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

MN will not start !

My MN will not start
this is an old MN but a fresh install done with dashman after reinstalling server
the local wallet reports MN started but then goes straight to watchdog expired
I have reinstalled sentinel and applied the latest sentinel patch
dashman is reporting wrong balance (should be 0 as was able to withdraw)

I cant think of anything else to do apart from reinstall again



dashman version 0.1.25 (37-g489dee6) - Fri Nov 10 09:26:25 EST 2017
gathering info, please wait... DONE!

hostname : 8888888
host uptime/load average : 1 days, 0.98 0.58 0.44
dashd bind ip address : 88888888888888888888888888888
dashd version : 0.12.2.0
dashd up-to-date : YES
dashd running : YES
dashd uptime : 0 days, 13 hours, 49 mins, 20 secs
dashd responding (rpc) : YES
dashd listening (ip) : YES
dashd connecting (peers) : YES
dashd port open : YES
dashd connection count : 12
dashd blocks synced : YES
last block (local dashd) : 768427
(chainz) : 768427
(dash.org) : 768427
(dashwhale) : 768426
(masternode.me) : 768426 - no forks detected
dashd current difficulty : 40227297.4349404
masternode started : NO
masternode visible (local) : NO
masternode visible (ninja) : YES
masternode address : 8888888888888888888888888888888888888888888
masternode funding txn : 888888888888888888888888888888888888888888
masternode queue/count : 0/0
masternode mnsync state : MASTERNODE_SYNC_FINISHED
1510275549
masternode network state :
masternode last payment : 1.80425 in 763775 on 11/01/2017 23:17:04 (8 days, 15 hours ago)
masternode balance : 1007.223721330
sentinel installed : YES
sentinel tests passed : YES
sentinel crontab enabled : YES
sentinel online : NO
Exiting.
 
It takes time to be 'ENABLED', maybe just wait a little longer.
try running commands below:
dash-cli masternode status
dash-cli mnsync status
OR
cd ~/.dashcore/sentinel/ && venv/bin/python bin/sentinel.py
check the results to get more detail.
 
dash-cli masternode status
{
"outpoint": "88888888888888888888888888888888888888",
"service": "888888888888:9999",
"status": "Not capable masternode: Masternode in NEW_START_REQUIRED state"
}
dash-cli mnsync status
{
"AssetID": 999,
"AssetName": "MASTERNODE_SYNC_FINISHED",
"AssetStartTime": 1510275549,
"Attempt": 0,
"IsBlockchainSynced": true,
"IsMasternodeListSynced": true,
"IsWinnersListSynced": true,
"IsSynced": true,
"IsFailed": false
}
cd ~/.dashcore/sentinel/ && venv/bin/python bin/sentinel.py
Invalid Masternode Status, cannot continue.
 
it's weird
it's like the local wallet "start" command just won't work

i'm going to recheck the .conf files

they are both correct

and local wallet shows correct balance
 
Last edited:
I fixed it

the crontab -e user name was wrong

I don't know how that happen i did'nt even make it
lol

balance is still not right though
 
Maybe you need a rescan on local wallet.
"Tools" => "Wallet Repair" => "Rescan blockchain files"
Check your balance again after the rescan.
 
I have got similar problem, its dashman returns "sentinel online : NO"

dash-cli masternode status returns:
"status": "Not capable masternode: Invalid protocol version"

cd ~/.dashcore/sentinel/ && venv/bin/python bin/sentinel.py
Invalid Masternode Status, cannot continue.
 
Back
Top