Ubuntu install.

[matthewh3]

Hi whenever I try and run Bitcoin on my Ubuntu PC I get the error message -

EXCEPTION: 22DbRunRecoveryException       
DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery       
bitcoin in AppInit()

Then the error message -

EXCEPTION: 22DbRunRecoveryException       
DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery       
bitcoin in CMyApp::OnUnhandledException()

Can anyone please help?

[DiThi]

Did you run 0.5.0rc1 then tried to run 0.4? I think I got the same error message when tried that. I did a backup of ~/.bitcon before, however, in case this would happen (but didn't restored it as the wallet is empty). I'll edit my post about compiling bitcoin recommending to backup ~/.bitcoin

[Justin Bieber]

Try emptying ~/.bitcoin/ (except for wallet.dat). Let it redownload the blockchain, something probably got corrupted.

[matthewh3]

Try emptying ~/.bitcoin/ (except for wallet.dat). Let it redownload the blockchain, something probably got corrupted.

Yes that worked thanks 

[a2offrb]

Very usual problem on ubuntu if shutting down client while its downloading blocks.
Is there solution to not download blocks from start? Takes 24 h on my old notebook 

[Justin Bieber]

Very usual problem on ubuntu if shutting down client while its downloading blocks.
Is there solution to not download blocks from start? Takes 24 h on my old notebook 

If you don't download the blockchain, you practically can't use the client.

[kokjo]

your database is of a wrong version. be sure to use the 4.8 version of libdb++ in ubuntu, when you are compiling

[Akemashite Omedetou]

Very usual problem on ubuntu if shutting down client while its downloading blocks.
Is there solution to not download blocks from start? Takes 24 h on my old notebook 

One thing you could easily do is to copy the block chain from another client, if you have access to one. (for example on another computer, or from a friend, etc...)
In that case, just copy files blk0001.dat and blkindex.dat from that computers's bitoin data directory to your data directory, overwriting files if needed.
If you have files like blk0002.dat, blk0003.dat and so on, copy them too.

[hevosenliha]

I just had this crash when shutting down 0.4 on ubuntu 64 bit.
(first time I ran 0.4 version, kept it running for a couple of days...)
Seems to still work afterwards anyway.


************************
UNKNOWN EXCEPTION       
bitcoin in CMyApp::OnUnhandledException()       

Segmentation fault

[DeathAndTaxes]

Eventually the client needs to support downloading compressed "recent" copy of blockchain via a bitorrent type protocol.  The client can still verify every block back to the genesis block locally so there is no risk of fraud.

The blockchain will only get larger and larger.  By "recent" I mean the network could take a snapshot of the blockchain say ever 1000 blocks (roughly once a week) on the even 1000th block.  Compress the blockchain and offer it as a seed via private torrent.  Client could have a single function bittorrent client inside.  The current method of passing new blocks is fine but that method is not the best for downloading tens of thousands of blocks.

The ability for all clients to download larger compressed "chunks" of the blockchain in out of order allocation to maximize throughput should speed up new block downloads.  The error checking built into bittorrent protocol would reduce the issue of block corruption.  Many people like myself would gladly devote bandwith to provide highspeed continual seeds of the "block snapshot".

Once client has completed the torrent (w/ nice progress bar) it would need to verify each block from genesis block to ensure the blockchain is accurate and then begin to download new blocks beyond xxx000 which at most would be 999 more blocks.

  

[dancupid]

Run a second Ubuntu in a virtual machine just for bitcoin and keep lots of snapshots so you don't need to keep downloading the block-chain in full.

[btc_artist]

Eventually the client needs to support downloading compressed "recent" copy of blockchain via a bitorrent type protocol.  The client can still verify every block back to the genesis block locally so there is no risk of fraud.

The blockchain will only get larger and larger.  By "recent" I mean the network could take a snapshot of the client every say 1000 blocks (roughly week) on the even 1000.  Compress the blockchain and offer it as a seed via private bittorrent type protocol.  The ability for all clients to download larger compressed "chunks" of the blockchain in out of order allocation to maximize throughput should speed up new block downloads.  The error checking built into bittorrent protocol would reduce the issue of block corruption.  Many people like myself would gladly devote bandwith to provide highspeed continual seeds of the "block snapshot".

Once client has completed the torrent (w/ nice progress bar) it will verify each block from genesis block and then begin to download new blocks beyon xxx000 which at most would be 999 more blocks.

 

You should outline this suggestion somewhere (here or github) where the devs will see it and can evaluate the idea.