Masternode Status: POS_ERROR

[x958T7W92b]

Does anyone know why a masternode might be displaying a status of POS_ERROR?

 

[UdjinM6]

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

 

[defunctec]

I have the same error.

Is this a problem?

How do i fix?

Thanks

 

[UdjinM6]

I have the same error.

Is this a problem?

How do i fix?

Thanks

Yes, you will miss mn payment. Make sure it's up to date and port 9999 is open.

 

[defunctec]

Yes, you will miss mn payment. Make sure it's up to date and port 9999 is open.

Node is upto date. Reinstalled the lot and still no result.

How do i open port?

Thanks

 

[UdjinM6]

Node is upto date. Reinstalled the lot and still no result.

How do i open port?

Thanks

Can you send me debug.log pls? [email protected]

 

[fuzzyduck]

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:seep() - 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.

 

[fuzzyduck]

Guess ill wait a bit and see if my POS score goes back to 0.

Yes, if not or goes more down then there is problem.
Wait few hours and see.

 

[fuzzyduck]

It did.... Lol. problem solved.

 

[qwizzie]

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)