• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

Dash core server starts, synchs but then stops: Invalid Masternode status

Erik_dash

New member
After installing Dash wallet 0.12.1 my masternode worked fine for 3-4 days, then it got disabled. Now I upgraded my Vultr server: 2 Ghz, 2GB RAM, 40GB Disk, 1TB/month.
I also upgraded my wallet to 0.12.3, yesterday after 8 hours of trying I finally managed to enable my masternode and after less than 2 hours it was disabled again.

Today I cannot run the Dash core server: "dashd not synched with network" (ok, this is normal), then: "Invalid Masternode Status. Cannot continue", then after a restart of the Dash Core server it sais: " Cannot obtain a lock on data directory.... Dash Core is probably already running." I cannot run the sentinal either, it gives the same error message. Any ideas?
 
After installing Dash wallet 0.12.1 my masternode worked fine for 3-4 days, then it got disabled. Now I upgraded my Vultr server: 2 Ghz, 2GB RAM, 40GB Disk, 1TB/month.
I also upgraded my wallet to 0.12.3, yesterday after 8 hours of trying I finally managed to enable my masternode and after less than 2 hours it was disabled again.

Today I cannot run the Dash core server: "dashd not synched with network" (ok, this is normal), then: "Invalid Masternode Status. Cannot continue", then after a restart of the Dash Core server it sais: " Cannot obtain a lock on data directory.... Dash Core is probably already running." I cannot run the sentinal either, it gives the same error message. Any ideas?

Invalid Masternode Status most likely means it needs a start from your cold wallet. Try using command masternode start-alias MNLABEL passphrase
(MNLABEL = what you entered in your masternode.conf and passphrase is your wallets password)

"Dash Core server cannot obtain lock" most likely means dashd is running already and can therefore not restart .. you can do a ./dash-cli stop
to stop the server and then do another ./dashd to start it again to know its running for sure.

Personally i would first make sure remote server is fully synced by issuing command ./dash-cli mnsync status
if it has everything on yes there then you can do a cold wallet restart with command masternode start-alias MNLABEL passphrase

Check on https://www.dashninja.pl/masternodes.html to see if your masternode appears after half a hour

Use following cronjob to keep sentinel alive :

If sentinel is installed in folder .dashcore : (change below YOURUSERNAME into your own accountname)

* * * * * cd /home/YOURUSERNAME/.dashcore/sentinel && ./venv/bin/python bin/sentinel.py >/dev/null 2>&1

If sentinel is installed in home/yourusername : (change below YOURUSERNAME into your own accountname)

* * * * * cd /home/YOURUSERNAME/sentinel && ./venv/bin/python bin/sentinel.py >/dev/null 2>&1
 
Last edited:
Back
Top