Quote from: Kismar on August 28, 2018, 11:58:30 AM

Just had my masternode go down a few hours ago, running 1.1.4.6 built on Saturday afternoon. Restarted it with valgrind so far without issue, below is the end of the debug.log if it might be of help:

Code:

2018-08-28 06:08:07 CGovernanceManager::ProcessVote -- Old invalid vote , MN outpoint = 2bd839a7c42729200f4b9d753a68b111ae2d55ee60b89455beae332c47f6d7a3-1, governance object hash = a5f79b3e5e2b0cbb6764bcfc093aa3c68e4521e9d4e03c590319e33152249d25
2018-08
2018-08-28 06:49:22 mncache.dat dump finished 207ms
2018-08-28 06:49:22 Verifying mnpayments.dat format...
2018-08-28 06:49:24 Loaded info from mnpayments.dat 1492ms
2018-08-28 06:49:24 Votes: 68219, Blocks: 4752
2018-08-28 06:49:24 Writting info to mnpayments.dat...
2018-08-28 06:49:25 Written info to mnpayments.dat 1185ms
2018-08-28 06:49:25 Votes: 68019, Blocks: 4803
2018-08-28 06:49:25 mnpayments.dat dump finished 2682ms
2018-08-28 06:49:25 Verifying governance.dat format...
2018-08-28 06:49:27 Loaded info from governance.dat 1740ms
2018-08-28 06:49:27 Governance Objects: 498 (Proposals: 113, Triggers: 384, Watchdogs: 1/1, Other: 0; Seen: 5263), Votes: 0
2018-08-28 06:49:27 Writting info to governance.dat...
2018-08-28 06:49:28 Written info to governance.dat 1612ms
2018-08-28 06:49:28 Governance Objects: 645 (Proposals: 115, Triggers: 529, Watchdogs: 1/1, Other: 0; Seen: 5580), Votes: 10785
2018-08-28 06:49:28 governance.dat dump finished 3357ms
2018-08-28 06:49:28 Verifying netfulfilled.dat format...
2018-08-28 06:49:28 Loaded info from netfulfilled.dat 2ms
2018-08-28 06:49:28 Nodes with fulfilled requests: 10
2018-08-28 06:49:28 Writting info to netfulfilled.dat...
2018-08-28 06:49:28 Written info to netfulfilled.dat 0ms
2018-08-28 06:49:28 Nodes with fulfilled requests: 178
2018-08-28 06:49:28 netfulfilled.dat dump finished 39ms
2018-08-28 06:49:28 dumped database files ...
2018-08-28 06:49:29 Shutdown: done

Thanks Kismar, that was a good post.

2018-08-28 06:49:21
ERROR: Found chain with blocks marked invalid
2018-08-28 06:49:21 ERROR: AcceptBlockHeader: block is marked invalid
2018-08-28 06:49:21 ERROR: invalid header received 846ef0d0c305f54a821ec9061af34a4cca1319cc84654b2e2e4f777039d6a38f
2018-08-28 06:49:21 tor: Thread interrupt
2018-08-28 06:49:21 torcontrol thread exit
2018-08-28 06:49:21 Cleaning sockets...
2018-08-28 06:49:22 PrepareShutdown: Prepare Shutdown In progress...
2018-08-28 06:49:22 Shutdown - renaming thread ...
2018-08-28 06:49:22 runCommand error: system(./biblepayd -erasechain) returned 32512

So it is revealing. On my end I need to take a look at something - it appears we do sort of jump the gun in the "Found chain with blocks marked invalid". We supposedly attempt to replay the last 205 blocks when that happens, but on your node it appears we jumped down and tried to restart it with -erasechain (see last line in the log) and that command returned an error (error 32512).

So on your end, if you are starting biblepay from an absolute path, (like from a script) that would explain 32512. Ill take a look at this. If you want autorecover to work, you could modify your script to : unalias cd && cd ~/biblepay/src/qt && ./biblepayd when it starts and then it should recover when this happens. But this is just for the time being as we make this fullproof and resilient.