unlinkable block about revpop-core HOT 6 CLOSED

Hi,

As far as we can tell, you are in the minority, so your node is not accepting blocks from the rest of the network, and it simply cannot bind these blocks.
The reasons for this may be higher up in the log, on the first block that was not accepted. Perhaps you can take a look and see if there’s more information?

Also, have a look at this previous issue and outcome, as it may provide some insight as well -- #52

Thanks!

from revpop-core.

does this help:
1395394ms th_a fork_database.cpp:64 push_block ] Pushing block to fork database that failed to link: 003f5d886885afbcd680ee312967cd47e0c186b8, 4152712
1395394ms th_a fork_database.cpp:65 push_block ] Head: 4152512, 003f5cc02488f9eb2dead4822c75dfff6da8029b

from revpop-core.

Actually we would have to take a look at the first block in the log that was declined. Generally though it appears that the blockchain is functioning as intended because you’re in the minority. In order to further assess if there’s a problem (though we suspect there probably isn’t) you’d have to provide information from the first block that was not accepted.
Alternatively you can also do a resync.
Thanks!

from revpop-core.

You know what, I started having this error a few times this week. I thought it was a one off and then I started seeing it a few more times. It seems that it's related to stopping the node and then restarting it. 3 times now after having stopped my node with CTRL+C and restarting it soon after, I've gotten this error and I have to delete my blockchain and resync. It seems like the longer I waited to restart my node after stopping it that the more possible it was that I'd get this error. I never had this issue pre v0.6.3 personally. I do see the "rewinding blockchain" console message when I CTRL+C and the program seems like it exits smoothly as always.

from revpop-core.

I left my node off for a few hours today to test its response (after being fully synced) and when I restarted it I got the error again.

from revpop-core.

While continual restarting is not typical when working with a node, the information has been noted and a study task has been added to the to-do list.
Thanks!

from revpop-core.