after upgrade to 17 I see these in my logs:
2018-11-05T11:45:08Z ERROR: ContextualCheckBlockHeader : rejected by synchronized checkpoint
2018-11-05T11:45:08Z ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: e16099b791d181a6a74a84028e209c66f061e67c65f6e59d04b9a45faf4bb011, bad-version (code 17)
does anyone know what these mean? Should I be worried?
I think, your wallet has rejected a Block, that did not match the last ACP.
This can happen. If you observe this message frequently, we would need to investigate, what happens with your client.
After seeing these the daemon crashes without possibility to connect through CLI. I tried to -reindex. I also removed everything from .feathercoin/ except feathercoin.config and wallet.dat and sync again. I also saw warning about -rpcworkqueue so I raised that one by adding rpcworkqueue=128. But unfortunately it still dying on me. The version 16 was fine. I checked the memory consumption and disk space and it seems fine. Still not sure what’s going on so I will monitor further.
even worse… now I see:
ERROR: ReadBlockFromDisk: OpenBlockFile failed for CBlockDiskPos(nFile=-1, nPos=0)
I have plenty of disk space… re-indexing again with use-thinblocks=0 …
running on Linux 3.16.0-4-amd64 Debian 3.16.51-3 (2017-12-13) x86_64 GNU/Linux
Honnestly, I have no real idea, where the problem is.
I had a similar problem when testing 0.17 initial code, but can’t remember how I solved the problem.
did you install the binary from the github release, compiled the release code yourself or did you use the debian packet as described here?
Also what is your debian version , Debian 8.0 or Dabian 9.0?
You can get that with ‘cat /etc/issue’
I’m using PPA from you. On 3rd or 4th re-sync it seems fine actually. Not sure what was/is the root cause here. I would say the synchronization is pretty unstable process on my vps ssd environment. I still see ContextualCheckBlockHeader error from time to time but so far it seems fine. Will report back if I see something suspicious.
Thanks for the update and I’m glad that it finally works for you
Update: There should be a fix for your problem in the next release (0.17.1)
The new Version 0.17.0.1 is relased
cool stuff… thank you!! will try it out