Old daemon and wallet version 0.17.0.1
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
As an aside the home page still links the 17.0.0 version for 32bit (which yeah, blows up for me)
j_scheibel last edited by | Tip j_scheibel
getting it in the 17.0.1 64 bit version too. maybe something has haapened to my wallet hmm. time to do some digging
something has happened on this block - it always dies there even when i stop network activity and close and reopen (to advance how far along it is in loading the block chain). i’m going try redownloading the whole block chain unless someone has an idea
i moved the wallet over to a fresh install of the 64 bit version with no block chain. then let it go (stopping once to make sure if i had to start over i didnt have to go ALLL the way back to the beginning) it finished and everything is good.
i am curious though. as my wallet is fairly old as feathercoin goes. is there a way to get hd key generation enabled without making a new wallet and transferring my funds?
mhh, I’m using the 0.17.0/0.17.1 version of the client and my original wallet is from 2014.
I didn’t have the problems you faced and all upgrades worked well.
As far as I know you need a clean wallet to enable hd key generatation, but you can dump your private keys to the console, copy/paste the keys to a safe place, delete the wallet.dat file and start the client. It then have hd keys enabled and generate an hd key for you. As soon as that is done you can add your private keys from the console and rescan the blockchain to get your coins.