Masternode goes to 'NEW_START_REQUIRED' status; becomes INACTIVE

Technologov

Member
Mar 5, 2017
160
36
88
38
Israel
This MN gets down:

https://www.dashninja.pl/mndetails.html?mnpubkey=Xx3ZyerDSnvKpBi3aK6jpHeqeporSMgCWj

Dash Core shows 'NEW_START_REQUIRED' status.
Dash Ninja shows : Status Inactive (0%)

But MN itself says everything is fine:

[email protected]:~/sentinel# venv/bin/python bin/sentinel.py
[email protected]:~/sentinel#

[email protected]:~/sentinel# ~/dashcore-0.12.1/bin/dash-cli mnsync status
{
"AssetID": 999,
"AssetName": "MASTERNODE_SYNC_FINISHED",
"Attempt": 0,
"IsBlockchainSynced": true,
"IsMasternodeListSynced": true,
"IsWinnersListSynced": true,
"IsSynced": true,
"IsFailed": false
}

[email protected]:~/sentinel# ~/dashcore-0.12.1/bin/dash-cli getblockcount
646769

Crontab is set to every 5 minutes:
[email protected]:~/sentinel# cat /etc/cron.d/sentinel
*/5 * * * * root cd ~/sentinel && venv/bin/python bin/sentinel.py 2>&1 >> ~/sentinel-cron.log


[email protected]:~/sentinel# ~/dashcore-0.12.1/bin/dash-cli --version
Dash Core RPC client version v0.12.1.4

EDIT: MN was manually restarted from control wallet.

Outcome:
We need more debugging tools for MasterNode debug.

Any ideas?
 
Last edited: