I hope that someone can help me out here with setting up a MN again. I had no problems doing this in older versions but now i keep getting stuck at the same point. Please keep in mind that I am not good in linux but i have used this guide before to keep a MN going for years.

- I start WinSCP and i click on the folder icon with the wheel/star and make the .dashcore folder
- At this point the folder does not display in the right window unless i click on the show hidden folder in the lower right corner or i click CTRL - O and write /.dashcore
- I can copy the two files from the desktop to the folder no problems there
- Once i get back to putty, i can enter the .dashcore folder
- I go back to root and install Joe
- Back in the user folder I type joe .dashcore/dash.conf, get the screen that has nothing in it and paste the setup that i have in my notepad
- Once i hit CTRL - k - x i get the following ERROR OPENING FILE.

I have tried creating the folder in putty with mkdir .dashcore but even then it does not show up unless i un-hide hidden files in winSCP.

I am trying to restart my masternode with the update. when I run ./dashd on the vps with the update I am getting an : Error loading block database. I am asked if I want to rebuild the database but everything hangs when I type yes. I did some research online and it seemed people got this message with bitcoin when there drives where full.

I have a 15G instance of which 4.1G is available. I've read minimum requirements are 20GB however I should be able to run dashd at least for a little while longer until the drive fills up, so I am confused as to why I am getting this error.

I want to install sentinel and get my masternode up and running again but am stuck on this part. Any suggestions, please?

Dash Core TeamModerator

I am trying to restart my masternode with the update. when I run ./dashd on the vps with the update I am getting an : Error loading block database. I am asked if I want to rebuild the database but everything hangs when I type yes. I did some research online and it seemed people got this message with bitcoin when there drives where full.

I have a 15G instance of which 4.1G is available. I've read minimum requirements are 20GB however I should be able to run dashd at least for a little while longer until the drive fills up, so I am confused as to why I am getting this error.

I want to install sentinel and get my masternode up and running again but am stuck on this part. Any suggestions, please?

Dash Core TeamModerator

I tried to reindex and that didn't work either. So I just started a brand new instance. Now I am at the ./dash-cli mnsync status part. I am not getting a sync. How long should it take?

Click to expand...

A brand new instance would have to download and reprocess full blockchain first which is ~1.2-1.5 GB currently iirc. So the time depends on your bandwidth and cpu/ram.
Check current blocks via "dash-cli getblockcount" periodically and compare that to http://explorer.dash.org/ - this should give you some idea how far is your node from having full blockchain.

A brand new instance would have to download and reprocess full blockchain first which is ~1.2-1.5 GB currently iirc. So the time depends on your bandwidth and cpu/ram.
Check current blocks via "dash-cli getblockcount" periodically and compare that to http://explorer.dash.org/ - this should give you some idea how far is your node from having full blockchain.

Click to expand...

Thanks! It's synced now. The node got the current block faster than the other sync variables, namely "isWinnersListSynced" and "IsSynced" took longer for some reason.

My watchdog keeps expiring. Can someone confirm that my cronjob is configured correctly? I've made sure I am updated to latest version of sentinel, and I have also confirmed that my cronjob is pointing to the correct directory:

Hi all, thanks to this awesome guide I have successfully set up 3 masternodes that I have been operating for a couple of months now. My only issue is that it seems that about once a week or two, each of the nodes (hosted on vultur) 'crash' (meaning the dashd process stops for some reason), and I have to go through the manual process of restarting the dashd client and digging the wallets out of cold storage to get everything up and running again. There doesn't seem to be a pattern to them crashing, and since I'm not a linux expert I'm having a hard time diagnosing what the problem is here. It does not appear that the instance itself is going down, so something else is causing the dash core to exit.

My questions are:

1) what is the best way to diagnose how/why dashcore stopped functioning?
2) Are other masternode operators seeing this pattern, meaning is this just typical behavior?
3) is the base 768MB / 15GB vultur node enough horsepower for a masternode, or could it be running out of RAM? Storage seems to be fine @ 15GB.
4) Is there a way to restart these nodes without having to dig out your wallet from cold storage each time?
5) Are there external ways to 'crash' someone else's masternode? I've disabled root logins and used the guide's basic firewall setup, should I be doing more here security-wise?

Dash Core TeamModerator

Hi all, thanks to this awesome guide I have successfully set up 3 masternodes that I have been operating for a couple of months now. My only issue is that it seems that about once a week or two, each of the nodes (hosted on vultur) 'crash' (meaning the dashd process stops for some reason), and I have to go through the manual process of restarting the dashd client and digging the wallets out of cold storage to get everything up and running again. There doesn't seem to be a pattern to them crashing, and since I'm not a linux expert I'm having a hard time diagnosing what the problem is here. It does not appear that the instance itself is going down, so something else is causing the dash core to exit.

My questions are:

1) what is the best way to diagnose how/why dashcore stopped functioning?
2) Are other masternode operators seeing this pattern, meaning is this just typical behavior?
3) is the base 768MB / 15GB vultur node enough horsepower for a masternode, or could it be running out of RAM? Storage seems to be fine @ 15GB.
4) Is there a way to restart these nodes without having to dig out your wallet from cold storage each time?
5) Are there external ways to 'crash' someone else's masternode? I've disabled root logins and used the guide's basic firewall setup, should I be doing more here security-wise?

2) It depends, crashes can happen due to a) errors in code b) lack of resources
3) Could be that it's killed by OOM (system), consider adding/increasing swap file
4) If they were offline more than 3 hours - no, if less - they should recover by themselves
5) Could be a result of ddos attack if you don't have proper defense in place and/or enough resources to mitigate it

Thanks for this guide. I'm working my way through it step by step. I've run into a problem, when I attempt to login to my VULTR VPS using PuTTY or WinSCP I'm always met with "Access Denied." I am able to login via the console using the same login credentials. What have I missed?

i was able to make my own Masternode with succes, it has been running for 4 days, does any one have estimate when to expect earning..
Everything is running fine, i dont know if there is a certain period when earning are credited..

Hi, you mentioned the local wallet can be closed here on afterwards when successful, but does the masternode need to have its wallet unlocked at all times? I saw the encrypt part in the steps, but couldn't find the unlocking part.

Hi I used Tao's guide to setup Masternode on remote server. I was able to get "Masternode Sucessfully Started" on putty screen. But when I go and check the status of my MN on dashninja it says "Inactive" under status bar ? I still 1000 DASH vested, and my server CPU is running at 9% with like 3.5 gb space used ? Can someone help please ?

@NewDashUser, I am wondering that the message "Masternode successfully started" you see on the putty screen. Starting masternode should be done from your local Dash Core wallet, that controls the private key holding your 1000 Dash collateral (Step 7 of Tao's manual). So either you keep your Dash collateral on the remote server's wallet (which is not safe) or you have done this step on the wrong machine (remote instead of local).