Can't remove Not capable masternode: Masternode in NEW_START_REQUIRED state

[europound]

really stuck with Not capable masternode: Masternode in NEW_START_REQUIRED state
removed caches,
changed ips
started from controller cold wallet

nothing helps
stuck in Not capable masternode: Masternode in NEW_START_REQUIRED state

what to do?

this happened after docker container crashed on a server

i did reindex, everything

 

[europound]

cd /sentinel && ./venv/bin/python bin/sentinel.py
Invalid Masternode Status, cannot continue.

 

[strophy]

What version of dashd are you using?

 

[europound]

latest,
i am just curious what could have caused this
any ideas?
how to shake off this pesky state?

 

[europound]

basically this is a bug
i am struggling with this bug for over two days, cannot shake off new state start error

this bug happens when too many dockers start lagging and completely freeze
and then server goes into limbo... not crash but limbo.... extremely slow ssh access, and docker response, takes hours

the only way is to fix this bug is to completely change everything, redo everything from scratch, everything must be new

new IP server
new mn genkey
new tmn xid
new config
etc

nothing must be linked to limbo state mn


please fix this weird bug

 

[europound]

it is as if entire mn network wants something from the past which you cannot give
nothing helps to bring back from limbo state,
reindex
removal of files
complete redo but with the same IP, genkey, txid

nothing helps

 

[europound]

solution is to start docker container from scratch, otherwise won't be able to shake off deep internal corruption that will pop up some days later

remove all related to mn
and start from scratch
seems to help