Masternode FAILED with "NEW_START_REQUIRED"

Technologov

Member
Mar 5, 2017
160
36
88
38
Israel
New MN running Dash Core 12.1.3, and stopped while I was asleep. (running as a $5 VPS on Vulture)

1. Why this is happening ?
2. how can I solve it ? (prevent it from crashing, esp. when I'm asleep or on vacation)
3. Does it reset the queue ? (so my MN doesn't get paid)

I expected the Masternode to be easy. Like "Fire-and-Forget".
 
Last edited:

UdjinM6

Official Dash Dev
Dash Core Group
May 20, 2014
3,639
3,537
1,183
1. Make sure this VPS has enough RAM, could be that OS is killing it due to high resource usage
2. Setup monitoring script which would restart it in case of a crash (there are few threads about this here on forum)
3. Make sure to setup DDoS protection on your VPS (see recent DDoS attack notification in Official Announcements and some following posts/threads for instructions)
 

bitbybit

New Member
Mar 18, 2017
9
1
3
33
I'm near the end of setting up my 1st mn and ran into this New_Start_Required issue. Came across this post.
Here's what I did:
- restart VPS
- ran "./dash-cli mnsync status", it displays "
{
"AssetID": 999,
"AssetName": "MASTERNODE_SYNC_FINISHED",
"Attempt": 0,
"IsBlockchainSynced": true,
"IsMasternodeListSynced": true,
"IsWinnersListSynced": true,
"IsSynced": true,
"IsFailed": false
}
so I assume the sync is completely successful.
- ran "venv/bin/python bin/sentinel.py", it displays "Invalid Masternode Status, cannot continue."

Checked VM monitoring, CPU and RAM don't seem to be an issue. This is brand new server, DDoS attack is unlikely. Any other ideas?