This happened to me today (again). Latest OSX, bitcoin-qt 0.8.5. FileVault 2 enabled, but it doesn't sound like that matters.
Any update/progress?
Topic: "Error opening block database. Do you want to rebuild the block database now?" - page 2. (Read 48060 times)
October 18, 2013, 02:48:44 PM
September 24, 2013, 04:45:33 PM
this problem has gotten so bad with OSX that i've gone back to the Windows version.
September 24, 2013, 04:33:36 PM
I have just encountered this error since I downloaded Bitcoin-Qt version 0.8.5 for OSX running on Mountain Lion, having replaced version 0.8.4 which I downloaded just a few days ago, and am seeing this when I attempt to run it: "Error opening block database. Do you want to rebuild the block database now?". I did not see this error when I ran 0.8.4.
Should I click "Ok" and allow the rebuild of the block database to proceed? Or would it be wise to stick to 0.8.4 for the time being?
Should I click "Ok" and allow the rebuild of the block database to proceed? Or would it be wise to stick to 0.8.4 for the time being?
Same problem here.
September 17, 2013, 10:58:41 AM
I bit the bullet and decided to delete all the files and re-download the blockchain. Replaced wallet.dat with a backup and I'm good to go on 0.8.5.
But now I'm reluctant to shut down Bitcoin-Qt in case I encounter the error again.
But now I'm reluctant to shut down Bitcoin-Qt in case I encounter the error again.
so you dont know for sure if it worked. only one way to find out.
mine just finished re indexing. im looking for a new wallet if anyone has any recommendations. i would consider a cloud wallet or whatever they are called.
September 17, 2013, 01:18:26 AM
I bit the bullet and decided to delete all the files and re-download the blockchain. Replaced wallet.dat with a backup and I'm good to go on 0.8.5.
But now I'm reluctant to shut down Bitcoin-Qt in case I encounter the error again.
But now I'm reluctant to shut down Bitcoin-Qt in case I encounter the error again.
September 15, 2013, 08:59:00 AM
Not just MAC, it's happening on Linux also.
I am now on my 3rd reindex, and to make matters worse, have forgotten some of my wallet encryption passphrase. But that is a different post.
What is giving me cause for concern now is the fact there is a post on here which says 0.8.5 solves the problem, but now I am seeing
users of 0.8.5 with the same problem.
WTF is going on?
I am now on my 3rd reindex, and to make matters worse, have forgotten some of my wallet encryption passphrase. But that is a different post.
What is giving me cause for concern now is the fact there is a post on here which says 0.8.5 solves the problem, but now I am seeing
users of 0.8.5 with the same problem.
WTF is going on?
September 14, 2013, 05:38:58 PM
What you're describing doesn't make sense except coincidentally. 0.8.4 and 0.8.5 are nearly identical, save for turning off the check that was getting tripped up by the negative version transactions.
I wonder— is everyone having frequent problems on OSX running filevault?
I wonder— is everyone having frequent problems on OSX running filevault?
and this is a fresh install version of mac os 10.8.4 that is only 2 mo old.
I could use a osx fresh install
September 14, 2013, 04:34:55 PM
What you're describing doesn't make sense except coincidentally. 0.8.4 and 0.8.5 are nearly identical, save for turning off the check that was getting tripped up by the negative version transactions.
I wonder— is everyone having frequent problems on OSX running filevault?
I wonder— is everyone having frequent problems on OSX running filevault?
no. i have Filevault turned off specifically to try and avoid this problem but yet it occurred again in 0.8.5
and this is a fresh install version of mac os 10.8.4 that is only 2 mo old.
September 14, 2013, 04:26:23 PM
What you're describing doesn't make sense except coincidentally. 0.8.4 and 0.8.5 are nearly identical, save for turning off the check that was getting tripped up by the negative version transactions.
I wonder— is everyone having frequent problems on OSX running filevault?
I wonder— is everyone having frequent problems on OSX running filevault?
No, not filevault. However when I first set up the client on version 0.6.3 I moved the contents of the Bitcoin directory into an encrypted disc image and hard linked the contents back into the original location. This meant that every time I needed to run Bitcoin-Qt I had to open the disc image first.
Of course now that I have encountered this error and looked into the file structure again I realise that it has changed. Doh. Oh well, this has still worked faultlessly until now.
Since posting about the error I have restored all the files to the Bitcoin directory from a backup and also restored the 0.8.4 application. I ran it with the checklevel=2 commandline option. It is now stuck at the "Verifying blocks..." stage and has been for more than 30 hours. It seems to be creating and removing files ending in .sst in the "chainstate" directory (for example 068675.sst) continuously. This seems like a very long time, and a little concerning tbh. I'm starting to wonder if it might be better to simply delete the Bitcoin directory, re-download the blockchain, then copy the wallet.dat file back when it's finished
September 14, 2013, 03:45:19 PM
osx 10.6 says im running "bitcoin version v0.8.3- beta" with this same problem.. 
I guess I'll wait to download the blocks one last time and find a new wallet? It does not seem like much else could be done with in reason.
I guess I'll wait to download the blocks one last time and find a new wallet? It does not seem like much else could be done with in reason. 
September 14, 2013, 02:29:58 PM
What you're describing doesn't make sense except coincidentally. 0.8.4 and 0.8.5 are nearly identical, save for turning off the check that was getting tripped up by the negative version transactions.
I wonder— is everyone having frequent problems on OSX running filevault?
I wonder— is everyone having frequent problems on OSX running filevault?
September 14, 2013, 01:49:30 PM
I had the error with 0.8.4. I updated to 0.8.5. It worked. Upon restart, same error with 0.8.5. Also using OSX 10.8.5.
Same here.
https://github.com/bitcoin/bitcoin/issues/2770#issuecomment-24437169
September 14, 2013, 10:57:20 AM
I have just encountered this error since I downloaded Bitcoin-Qt version 0.8.5 for OSX running on Mountain Lion, having replaced version 0.8.4 which I downloaded just a few days ago, and am seeing this when I attempt to run it: "Error opening block database. Do you want to rebuild the block database now?". I did not see this error when I ran 0.8.4.
Should I click "Ok" and allow the rebuild of the block database to proceed? Or would it be wise to stick to 0.8.4 for the time being?
Should I click "Ok" and allow the rebuild of the block database to proceed? Or would it be wise to stick to 0.8.4 for the time being?
Same as Keewee:
I had the error with 0.8.4. I updated to 0.8.5. It worked. Upon restart, same error with 0.8.5. Also using OSX 10.8.5.
September 13, 2013, 06:38:17 AM
I have just encountered this error since I downloaded Bitcoin-Qt version 0.8.5 for OSX running on Mountain Lion, having replaced version 0.8.4 which I downloaded just a few days ago, and am seeing this when I attempt to run it: "Error opening block database. Do you want to rebuild the block database now?". I did not see this error when I ran 0.8.4.
Should I click "Ok" and allow the rebuild of the block database to proceed? Or would it be wise to stick to 0.8.4 for the time being?
Should I click "Ok" and allow the rebuild of the block database to proceed? Or would it be wise to stick to 0.8.4 for the time being?
September 13, 2013, 02:12:28 AM
And it looks like a known bug: https://bitcointalksearch.org/topic/all-bitcoind-bitcoin-qt-nodes-failing-to-come-up-workaround-inside-290922
Finally it's fixed! Was this the same bug this thread relates to?The last couple of posts here (the September ones) are almost certainly the issue linked above, however... which is fixed via the workaround there or in 0.8.5 that just came out.
September 13, 2013, 01:00:53 AM
And it looks like a known bug: https://bitcointalksearch.org/topic/all-bitcoind-bitcoin-qt-nodes-failing-to-come-up-workaround-inside-290922
Finally it's fixed! Was this the same bug this thread relates to? 
September 09, 2013, 09:13:31 AM
And it looks like a known bug: https://bitcointalksearch.org/topic/all-bitcoind-bitcoin-qt-nodes-failing-to-come-up-workaround-inside-290922
September 09, 2013, 09:11:36 AM
I have been fighting this same issue on 2 different servers for the last 12 hours or so. Not sure if it was introduced in the update to 0.8.4.
I've run with the -reindex flag, deleted the chainstore directory and let the system rebuild it and also removed the entire home directory and let it re-sync the entire blockchain. Every single time, it works fine until the process is restarted, and then it complains about a corrupted database:
Code:
2013-09-09 13:56:14 Bitcoin version v0.8.4.0-g839c7d1-beta ()
2013-09-09 13:56:14 Using OpenSSL version OpenSSL 1.0.1 14 Mar 2012
2013-09-09 13:56:14 Default data directory /var/lib/bitcoin/.bitcoin
2013-09-09 13:56:14 Using data directory /var/lib/bitcoin/.bitcoin
2013-09-09 13:56:14 Using at most 125 connections (1024 file descriptors available)
2013-09-09 13:56:14 Using 4 threads for script verification
2013-09-09 13:56:14 init message: Verifying wallet...
2013-09-09 13:56:14 dbenv.open LogDir=/var/lib/bitcoin/.bitcoin/database ErrorFile=/var/lib/bitcoin/.bitcoin/db.log
2013-09-09 13:56:14 Bound to [::]:8333
2013-09-09 13:56:14 Bound to 0.0.0.0:8333
2013-09-09 13:56:14 init message: Loading block index...
2013-09-09 13:56:14 Opening LevelDB in /var/lib/bitcoin/.bitcoin/blocks/index
2013-09-09 13:56:14 Opened LevelDB successfully
2013-09-09 13:56:14 Opening LevelDB in /var/lib/bitcoin/.bitcoin/chainstate
2013-09-09 13:56:14 Opened LevelDB successfully
2013-09-09 13:56:17 LoadBlockIndexDB(): last block file = 80
2013-09-09 13:56:17 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=200, size=24210772, heights=256747...256945, time=2013-09-08...2013-09-09)
2013-09-09 13:56:17 LoadBlockIndexDB(): transaction index enabled
2013-09-09 13:56:17 LoadBlockIndexDB(): hashBestChain=0000000000000021bc464889a73c170549c2b4fc877a1de31f3e11ef8f94a13c height=256945 date=2013-09-09 13:55:20
2013-09-09 13:56:17 init message: Verifying blocks...
2013-09-09 13:56:17 Verifying last 288 blocks at level 3
2013-09-09 13:56:20 ERROR: DisconnectBlock() : added transaction mismatch? database corrupted
2013-09-09 13:56:22 ERROR: VerifyDB() : *** coin database inconsistencies found (last 128 blocks, 16270 good transactions before that)
2013-09-09 13:56:22 : Corrupted block database detected.
Do you want to rebuild the block database now?
2013-09-09 13:56:22 Flush(false)
2013-09-09 13:56:22 DBFlush(false) ended 1ms
2013-09-09 13:56:22 StopNode()
2013-09-09 13:56:22 Flushed 0 addresses to peers.dat 4ms
2013-09-09 13:56:22 Committing 32881 changed transactions to coin database...
2013-09-09 13:56:22 Flush(true)
2013-09-09 13:56:22 DBFlush(true) ended 1ms
2013-09-09 13:56:26
2013-09-09 13:56:14 Using OpenSSL version OpenSSL 1.0.1 14 Mar 2012
2013-09-09 13:56:14 Default data directory /var/lib/bitcoin/.bitcoin
2013-09-09 13:56:14 Using data directory /var/lib/bitcoin/.bitcoin
2013-09-09 13:56:14 Using at most 125 connections (1024 file descriptors available)
2013-09-09 13:56:14 Using 4 threads for script verification
2013-09-09 13:56:14 init message: Verifying wallet...
2013-09-09 13:56:14 dbenv.open LogDir=/var/lib/bitcoin/.bitcoin/database ErrorFile=/var/lib/bitcoin/.bitcoin/db.log
2013-09-09 13:56:14 Bound to [::]:8333
2013-09-09 13:56:14 Bound to 0.0.0.0:8333
2013-09-09 13:56:14 init message: Loading block index...
2013-09-09 13:56:14 Opening LevelDB in /var/lib/bitcoin/.bitcoin/blocks/index
2013-09-09 13:56:14 Opened LevelDB successfully
2013-09-09 13:56:14 Opening LevelDB in /var/lib/bitcoin/.bitcoin/chainstate
2013-09-09 13:56:14 Opened LevelDB successfully
2013-09-09 13:56:17 LoadBlockIndexDB(): last block file = 80
2013-09-09 13:56:17 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=200, size=24210772, heights=256747...256945, time=2013-09-08...2013-09-09)
2013-09-09 13:56:17 LoadBlockIndexDB(): transaction index enabled
2013-09-09 13:56:17 LoadBlockIndexDB(): hashBestChain=0000000000000021bc464889a73c170549c2b4fc877a1de31f3e11ef8f94a13c height=256945 date=2013-09-09 13:55:20
2013-09-09 13:56:17 init message: Verifying blocks...
2013-09-09 13:56:17 Verifying last 288 blocks at level 3
2013-09-09 13:56:20 ERROR: DisconnectBlock() : added transaction mismatch? database corrupted
2013-09-09 13:56:22 ERROR: VerifyDB() : *** coin database inconsistencies found (last 128 blocks, 16270 good transactions before that)
2013-09-09 13:56:22 : Corrupted block database detected.
Do you want to rebuild the block database now?
2013-09-09 13:56:22 Flush(false)
2013-09-09 13:56:22 DBFlush(false) ended 1ms
2013-09-09 13:56:22 StopNode()
2013-09-09 13:56:22 Flushed 0 addresses to peers.dat 4ms
2013-09-09 13:56:22 Committing 32881 changed transactions to coin database...
2013-09-09 13:56:22 Flush(true)
2013-09-09 13:56:22 DBFlush(true) ended 1ms
2013-09-09 13:56:26
September 09, 2013, 08:44:09 AM
Ok, this is ridiculous!
1) Can't stop bitcoind with ./bitcoind stop; it replies "error: bla bla bla" (can't remember)..
2) Shuts down via jsonrpc and bitcoind process just sits there with 0% cpu though port is closed
3) Kills -9 process then this thread!?
So WTF now, delete database? I don't wan't to redownload whole blockchain after each "failed" restart of bitcoind?!?
Why is bitcoind asking a question you can't reply to?
EDIT: Currently reindexing, it's connectable, we'll see how that goes... funny thing bitcoind reports negative balance while indexing...
1) Can't stop bitcoind with ./bitcoind stop; it replies "error: bla bla bla" (can't remember)..
2) Shuts down via jsonrpc and bitcoind process just sits there with 0% cpu though port is closed
3) Kills -9 process then this thread!?
So WTF now, delete database? I don't wan't to redownload whole blockchain after each "failed" restart of bitcoind?!?
Why is bitcoind asking a question you can't reply to?
EDIT: Currently reindexing, it's connectable, we'll see how that goes... funny thing bitcoind reports negative balance while indexing...
August 10, 2013, 09:03:22 AM
You don't need to run Bitcoin-Qt. You can use Electrum or Multibit.
could i have my BTC transfer without finishing my blockchain in QT? I have a coin that was sent to me i have not received yet. could using Multibit or electrum intercept it? or should i wait?
also what one would people recommend? Electrum or Multibit?
Jump to: