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

Masternode Status: POS_ERROR

Because it either failed responding on port 9999 or was acting incorrectly on IX locks when it was chosen to do so 6 or more times in a row
 
alright got also errors since a couple of days now i think:

015-06-08 19:48:01 MasternodePOS::mnse - MasternodeB ranking is too low
2015-06-08 19:48:02 MasternodePOS::mnse - MasternodeB ranking is too low
2015-06-08 19:48:05 MasternodePOS::mnse - MasternodeB ranking is too low
2015-06-08 19:48:06 MasternodePOS::mnse - MasternodeB ranking is too low
2015-06-08 19:48:07 MasternodePOS::mnse - MasternodeB ranking is too low
2015-06-08 19:48:08 MasternodePOS::mnse - MasternodeB ranking is too low
2015-06-08 19:48:10 MasternodePOS::mnse - MasternodeB ranking is too low
2015-06-08 19:48:12 CActiveMasternode::Dseep() - RelayMasternodeEntryPing vin = CTxIn(COutPoint(64493231c1843b9a0579fce24c07422acccde32166ed04724ac35164f37b9dff, 1), scriptSig=)
2015-06-08 19:48:13 CDarksendPool::UpdateState() - Can't set state to ERROR or SUCCESS as a Masternode.
2015-06-08 19:48:43 CDarksendPool::UpdateState() - Can't set state to ERROR or SUCCESS as a Masternode.
 
After rebooting two of my server instances in order to perform network updates on them, one of my instances shows
POS_ERROR when trying to masternode list grep IP it. The other had no problem after restarting ./dashd
The one with the POS_ERROR still has POS score 0 on dashninja.pl but i'm getting worried now.

I checked firewall and its still has port 9999 open, anything else i can do ?

edit : the advice was given to just delete the whole blockchain (let only wallet.dat & dash.conf stay in there) and then sync from bootstrap. That did the trick, it now shows ''ENABLED" in both PUTTY and in the masternodes status overview list (https://www.dashpay.io/binaries/masternodes.txt)
 
Last edited by a moderator:
Back
Top