Topic: Warning: Large valid fork found (Read 2193 times)
Ok, cool. I ran the 0.8.4rc2 reindex against my old "broken" blockchain, and it completed without errors.
This is the one that 0.8.2 decided was corrupt, and was unable to reindex.
If you'd like any information about library versions I am using in unstable, let me know.
Are you running debian's package or did you pull bitcoin from git?
It is git.
Quote
If you are building it yourself, type "git checkout v0.8.4rc2" and build that. I am _very_ interested in hearing from you about how things are working for you, as we believe there may be problems with a dependency in debian unstable, so please follow up.
Ok I have checked out 0.8.4rc2 which built fine, but reported a corrupt database at startup. So I am reindexing now.
I'll report back once it gets somewhere - tomorrow probably.
Are you running debian's package or did you pull bitcoin from git?
If it's debian's package then thats very alarming that they are shipping untested git snapshots.
If you are building it yourself, type "git checkout v0.8.4rc2" and build that. I am _very_ interested in hearing from you about how things are working for you, as we believe there may be problems with a dependency in debian unstable, so please follow up.
If it's debian's package then thats very alarming that they are shipping untested git snapshots.
If you are building it yourself, type "git checkout v0.8.4rc2" and build that. I am _very_ interested in hearing from you about how things are working for you, as we believe there may be problems with a dependency in debian unstable, so please follow up.
What version of bitcoin are you actually running, where did you get it from, what OS? and can you look for INVALID in your debug log and post the few lines before and after the first instance of that?
I am running bitcoind on Debian Wheezy/Unstable, and according to debug.log (though I thought I saw 0.8.4 in the git pull):
Bitcoin version v0.8.2-332-gf19eda1-beta
It doesn't say INVALID in debug.log anywhere - could something else cause the inconsitancy? Or can I git my way back to a better version of bitcoind?
The messages you're quoting existing only in bitcoin's git master, as you can see— it's a little prone to crying wolf and not ready for release yet.
What version of bitcoin are you actually running, where did you get it from, what OS? and can you look for INVALID in your debug log and post the few lines before and after the first instance of that?
What version of bitcoin are you actually running, where did you get it from, what OS? and can you look for INVALID in your debug log and post the few lines before and after the first instance of that?
Hello, I was getting a "Chain state database corruption likely" warning in my bitcoin logs, followed by a drop to safe mode. So I decided to clear the ~/.bitcoin folder, gill pull to the latest, and re-download the blockchain.
However, it is happening again:
Code:
CheckForkWarningConditions: Warning: Large valid fork found
forking the chain at height 209249 (00000000000004b59c50942a44245f83ab3ee96fad06a5e5a9f36fde8c514dcf)
lasting to height 234725 (00000000000001a0dacd1542c69c7060aec6714f370ee65ffd89c53b77e5336c).
Chain state database corruption likely.
forking the chain at height 209249 (00000000000004b59c50942a44245f83ab3ee96fad06a5e5a9f36fde8c514dcf)
lasting to height 234725 (00000000000001a0dacd1542c69c7060aec6714f370ee65ffd89c53b77e5336c).
Chain state database corruption likely.
There haven't been any outages during the download (it has only been running a few hours), the machine is fine.
Any ideas what might cause this, or can the warning be ignored?
I get this in getinfo:
Code:
"errors" : "Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues."
This is on bitcoind 0.8.4, the problems seemed to start on 0.8.3
Thanks,
Paul
Jump to: