Topic: Rebuilding the Block Chain Issue (Read 1783 times)
I had issues the past day or two. I attempted restoring my 'bitcoin' folder back to a prior time from backup, which has worked in the past... but did not in this case, no matter how far back I went. Had to download the latest 0.8.5 client, then restore my bitcoin folder, then it launched up and worked (without having to download the entire blockchain again)
http://sourceforge.net/mailarchive/message.php?msg_id=31380906
Quote
Please return your seats and fasten your seat-belts.
All Bitcoin-qt / Bitcoind nodes will currently fail to come back up
after a restart, reporting
": *** coin database inconsistencies found"
and
"Do you want to rebuild the block database now?"
Reindexing _will not_ correct the problem. In Bitcoin-qt you should
say no to this reindex prompt as it will not help for this problem and
will only waste your time.
To workaround:
Please specify the command-line or configuration file argument
-checklevel=2 to Bitcoind or Bitcoin-qt.
The issue appears to have been introduced by 0.8.0 and is only a local
issue, beyond the annoyance restarting nodes it appears to be harmless
and carries no forking risk but will take a software update to fix
completely.
This problem will persist until no more than 288 blocks after 256818,
unless another trigger transaction is added to the blockchain (which
may well happen).
More information will be forthcoming once a patch is available.
All Bitcoin-qt / Bitcoind nodes will currently fail to come back up
after a restart, reporting
": *** coin database inconsistencies found"
and
"Do you want to rebuild the block database now?"
Reindexing _will not_ correct the problem. In Bitcoin-qt you should
say no to this reindex prompt as it will not help for this problem and
will only waste your time.
To workaround:
Please specify the command-line or configuration file argument
-checklevel=2 to Bitcoind or Bitcoin-qt.
The issue appears to have been introduced by 0.8.0 and is only a local
issue, beyond the annoyance restarting nodes it appears to be harmless
and carries no forking risk but will take a software update to fix
completely.
This problem will persist until no more than 288 blocks after 256818,
unless another trigger transaction is added to the blockchain (which
may well happen).
More information will be forthcoming once a patch is available.
This fix is not working for me. I'm sure I did it correctly. This sucks.
http://sourceforge.net/mailarchive/message.php?msg_id=31380906
Quote
Please return your seats and fasten your seat-belts.
All Bitcoin-qt / Bitcoind nodes will currently fail to come back up
after a restart, reporting
": *** coin database inconsistencies found"
and
"Do you want to rebuild the block database now?"
Reindexing _will not_ correct the problem. In Bitcoin-qt you should
say no to this reindex prompt as it will not help for this problem and
will only waste your time.
To workaround:
Please specify the command-line or configuration file argument
-checklevel=2 to Bitcoind or Bitcoin-qt.
The issue appears to have been introduced by 0.8.0 and is only a local
issue, beyond the annoyance restarting nodes it appears to be harmless
and carries no forking risk but will take a software update to fix
completely.
This problem will persist until no more than 288 blocks after 256818,
unless another trigger transaction is added to the blockchain (which
may well happen).
More information will be forthcoming once a patch is available.
All Bitcoin-qt / Bitcoind nodes will currently fail to come back up
after a restart, reporting
": *** coin database inconsistencies found"
and
"Do you want to rebuild the block database now?"
Reindexing _will not_ correct the problem. In Bitcoin-qt you should
say no to this reindex prompt as it will not help for this problem and
will only waste your time.
To workaround:
Please specify the command-line or configuration file argument
-checklevel=2 to Bitcoind or Bitcoin-qt.
The issue appears to have been introduced by 0.8.0 and is only a local
issue, beyond the annoyance restarting nodes it appears to be harmless
and carries no forking risk but will take a software update to fix
completely.
This problem will persist until no more than 288 blocks after 256818,
unless another trigger transaction is added to the blockchain (which
may well happen).
More information will be forthcoming once a patch is available.
hi
same issue here... since 2 days bitcoin-qt tells me to rebuild the blockchain. the client makes it and after some time the client was in sync.
now i make the update but the same error on startup, but with the new client no syncing anymore
in the debug console this is what i get on get info:
same issue here... since 2 days bitcoin-qt tells me to rebuild the blockchain. the client makes it and after some time the client was in sync.
now i make the update but the same error on startup, but with the new client no syncing anymore
in the debug console this is what i get on get info:
Code:
{
"version" : 80500,
"protocolversion" : 70001,
"walletversion" : 60000,
"balance" : ******,
"blocks" : 0,
"timeoffset" : 0,
"connections" : 17,
"proxy" : "",
"difficulty" : 1.00000000,
"testnet" : false,
"keypoololdest" : 1378389433,
"keypoolsize" : 100,
"paytxfee" : 0.00000000,
"unlocked_until" : 0,
"errors" : "Warnung: Angezeigte Transaktionen sind evtl. nicht korrekt! Sie oder die anderen Knoten müssen unter Umständen (den Client) aktualisieren."
}
"version" : 80500,
"protocolversion" : 70001,
"walletversion" : 60000,
"balance" : ******,
"blocks" : 0,
"timeoffset" : 0,
"connections" : 17,
"proxy" : "",
"difficulty" : 1.00000000,
"testnet" : false,
"keypoololdest" : 1378389433,
"keypoolsize" : 100,
"paytxfee" : 0.00000000,
"unlocked_until" : 0,
"errors" : "Warnung: Angezeigte Transaktionen sind evtl. nicht korrekt! Sie oder die anderen Knoten müssen unter Umständen (den Client) aktualisieren."
}
I keep getting the message that I need to rebuild the block chain when I start my wallet. It happened twice today, and I have not even restarted the pc. It's done it 4-5 times in the past week now. I downloaded the latest version hoping that would fix it. Guess not. Anyone have any ideas? Also, anyone know if this takes a lot of bandwidth? I'm usually pretty close to my monthly download limit already.
Jump to: