bitcoind does not coexist with bitcoin

[Shevek]

Hi! This is my first "newbie" message!

I've installed bitcoind from Debian repositories. It works ok.

But, if I stop bitcoind and launch bitcoin from sourceforge, a lot of complaint messages about database corruption appear and the program stops.

Aren't they both compatible!!??

[1715366310]

1715366310

[koin]

Hi! This is my first "newbie" message!

I've installed bitcoind from Debian repositories. It works ok.

But, if I stop bitcoind and launch bitcoin from sourceforge, a lot of complaint messages about database corruption appear and the program stops.

Aren't they both compatible!!??

you can get bitcoind from soureforge as well.   does that version work ok too?

[Shevek]

you can get bitcoind from soureforge as well.   does that version work ok too?

The downloaded bitcoind (0.3.22) from sourceforge gives:

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

terminate called after throwing an instance of 'DbRunRecoveryException'
  what():  DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery

Of course, I previously stopped the Debian daemon.

I know both shares the directory ~.bitcoin but I supposed that the inside data structure is the same.

Thanks for your tip.

[dr.bitcoin]

Doesn't this sound like a corrupt database? Did your machine crash at any point when playing with bitcoind and bitcoin?

[Shevek]

Doesn't this sound like a corrupt database? Did your machine crash at any point when playing with bitcoind and bitcoin?

No, there is no crash. BTW bitcoin and bitcoind from sourceforge are mutually compatible. But bitcoind from Debian repositories gives the reported problem with both.

I've found a trick to share de same directory. It's not fair play but it works.

After stopping either bitcoin or bitcoind (from SF), delete the file ~.bitcoin/database/log.0000000??, and also eventually ~.bitcoin/bitcoin.pid. Then launching bitcoind from Debian packet yield no problem. Before re-run the programs of SF, the same file deletion should be done.

I'm not sure why, but it solves the problem...