Title: Debian 7 + bitcoind from source + libdb5.1 = nope [SOLVED] Post by: w00dy on November 30, 2013, 08:51:33 PM - i want to compile bitcoind on Debian 7.2 x64
- i can NOT install libdb4.x dev packages because it breaks other stuff on the box. - i don't care about the wallet. i just need to run bitcoind on this box - litecoind (latest) is running fine.... compiled on this box. the kernel: Code: Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.51-1 after a git clone i do a ./autogen.sh the ./configure breaks with Code: configure: error: Found Berkeley DB other than 4.8, required for portable wallets (--with-incompatible-bdb to ignore) ok... no problem... just "fix" it with "--with-incompatible-bdb". the ./configure runs through and i can do a "make". bitcoind builds successfully but if i try to run it i get Code: Error: Error initializing wallet database environment /home/bitcoin/.bitcoin! debug.log Code: 2013-11-30 20:14:35 Bitcoin version v0.8.2-827-gb78d1cd-beta (2013-11-29 22:04:18 -0800) even tho it says "init message: Verifying wallet..." - there is no wallet.dat. the only "fix" for this error i found via google is pretty much a "delete .bitcoin"... but it does not work here. no matter what i do, it fails always with "Error initializing wallet database environment" :-[ any1? Title: Re: Debian 7 + bitcoind from source + libdb5.1 = nope Post by: Adriano on November 30, 2013, 09:04:51 PM Are you running it with the user who owns /home/bitcoin/
Have any file/directory been created under /home/bitcoin/.bitcoin ? I would say it seems a permission issue. Adriano Title: Re: Debian 7 + bitcoind from source + libdb5.1 = nope Post by: w00dy on November 30, 2013, 09:20:18 PM Are you running it with the user who owns /home/bitcoin/ Have any file/directory been created under /home/bitcoin/.bitcoin ? I would say it seems a permission issue. Adriano i think permissions are fine. - there is a user "bitcoin" in group "bitcoin" also, the litecoin stuff to compare, entrys in my passwd Code: bitcoin:x:1005:1005::/home/bitcoin:/bin/bash and group Code: bitcoin:x:1005: /home Code: drwxr-xr-x 5 root root 4096 Nov 30 12:56 . - bitcoin/litecoin homes sit on / - data is a raid5 volume, woody's home is symlinked on it. /home/litecoin Code: drwxr-xr-x 3 litecoin litecoin 4096 Nov 30 13:38 . /home/bitcoin Code: drwxr-xr-x 3 bitcoin bitcoin 4096 Nov 30 21:21 . running bitcoind_broken or non-stripped bitcoind executable as root OR user bitcoin (su - bitcoin -> ./bitcoind) make no difference. Edit: .bitcoin is NOT created if i run as root .bitcoin IS created if i run as "bitcoin" Code: drwxr-xr-x 4 bitcoin bitcoin 4096 Nov 30 22:47 . Title: Re: Debian 7 + bitcoind from source + libdb5.1 = nope Post by: gmaxwell on December 01, 2013, 12:51:56 AM You cannot switch BDB versions on a wallet that wasn't cleanly shut down on the prior version, I'd guess thats whats happening here.
Title: Re: Debian 7 + bitcoind from source + libdb5.1 = nope Post by: Adriano on December 01, 2013, 01:03:41 AM You cannot switch BDB versions on a wallet that wasn't cleanly shut down on the prior version, I'd guess thats whats happening here. As I understood it is a brand new instalation where the wallet.dat isn't even present yet and had to be created. running bitcoind_broken or non-stripped bitcoind executable as root OR user bitcoin (su - bitcoin -> ./bitcoind) make no difference. Edit: .bitcoin is NOT created if i run as root .bitcoin IS created if i run as "bitcoin" .bitcoin is probably being created on /root/.bitcoin when you run it as root (unless you define datadir on the command line) Anyway, if it was created when you run it as bitcoin user then it is not permission problem indeed. Code: drwxr-xr-x 4 bitcoin bitcoin 4096 Nov 30 22:47 . If you remove the /home/bitcoind/.bitcoin/ and start bitcoind again, does it create again the same files as stated above? Adriano Title: Re: Debian 7 + bitcoind from source + libdb5.1 = nope Post by: Adriano on December 01, 2013, 01:29:02 AM I have just tried with https://github.com/bitcoin/bitcoin/archive/0.8.6.zip on my system and it worked ok on debian 7.2 with libdb5.1
Can you try downloading it directly instead of cloning and see if there is any differences ? Adriano Title: Re: Debian 7 + bitcoind from source + libdb5.1 = nope Post by: w00dy on December 01, 2013, 07:42:05 AM You cannot switch BDB versions on a wallet that wasn't cleanly shut down on the prior version, I'd guess thats whats happening here. As I understood it is a brand new instalation where the wallet.dat isn't even present yet and had to be created. Adriano is right here. running bitcoind_broken or non-stripped bitcoind executable as root OR user bitcoin (su - bitcoin -> ./bitcoind) make no difference. Edit: .bitcoin is NOT created if i run as root .bitcoin IS created if i run as "bitcoin" .bitcoin is probably being created on /root/.bitcoin when you run it as root (unless you define datadir on the command line) .bitcoin is found in /root but it's contens look exactly like the "bitcoin" user dir. Code: drwxr-xr-x 9 root root 4096 Nov 30 22:46 . ALL the database directorys are empty. Quote If you remove the /home/bitcoind/.bitcoin/ and start bitcoind again, does it create again the same files as stated above? Adriano Code: su - bitcoin you get this: Code: drwxr-xr-x 4 bitcoin bitcoin 4096 Dez 1 08:35 . Quote I have just tried with https://github.com/bitcoin/bitcoin/archive/0.8.6.zip on my system and it worked ok on debian 7.2 with libdb5.1 Can you try downloading it directly instead of cloning and see if there is any differences ? will do soon. Thx for your help! Title: Re: Debian 7 + bitcoind from source + libdb5.1 = nope [SOLVED] Post by: w00dy on December 01, 2013, 09:18:53 AM ooooookay... looks like the problem was somehow on my end.
this debian box got upgraded from squeeze to wheezy like 2 months ago. I'm not really sure what the solution was but i did this: - installed the upnp libs (before, i always compiled with USE_UPNP=0) - apt-get auto-remove'ed left-overs from Squeeze (lots of old boost libs got removed) - restarted :P now the git cloned source and the zip-DL source compile and work... 8) thx a lot! Title: Re: Debian 7 + bitcoind from source + libdb5.1 = nope [SOLVED] Post by: Adriano on December 01, 2013, 10:41:40 AM ooooookay... looks like the problem was somehow on my end. this debian box got upgraded from squeeze to wheezy like 2 months ago. I'm not really sure what the solution was but i did this: - installed the upnp libs (before, i always compiled with USE_UPNP=0) - apt-get auto-remove'ed left-overs from Squeeze (lots of old boost libs got removed) - restarted :P now the git cloned source and the zip-DL source compile and work... 8) thx a lot! That's great. Title: Re: Debian 7 + bitcoind from source + libdb5.1 = nope [SOLVED] Post by: Barmz on December 02, 2013, 11:28:53 PM Great job, I have the same problem w/ DBD5.1 + Debian 7 + Bitcoind source :)
I'll try again tomorrow Title: Re: Debian 7 + bitcoind from source + libdb5.1 = nope [SOLVED] Post by: nostromo429 on December 08, 2013, 06:36:08 PM I'm running into this problem with bitcoind and BerkeleyDB on Debian wheezy myself, now, in a brand-new installation from scratch.
Question: What does the Code: --with-incompatible-bdb I'm curious why BDB 4.8 is still being used, it seems to be near obsolescence even on known-glacial distros (CentOS and Debian stable). My problem is that IFF Code: --with-incompatible-bdb Options? Maybe I could build BDB 4.8 and shove it someplace really out-of-the-way like /opt? Thanks in advance! Title: Re: Debian 7 + bitcoind from source + libdb5.1 = nope [SOLVED] Post by: Adriano on December 09, 2013, 02:38:12 AM I'm running into this problem with bitcoind and BerkeleyDB on Debian wheezy myself, now, in a brand-new installation from scratch. Question: What does the Code: --with-incompatible-bdb I'm curious why BDB 4.8 is still being used, it seems to be near obsolescence even on known-glacial distros (CentOS and Debian stable). My problem is that IFF Code: --with-incompatible-bdb Options? Maybe I could build BDB 4.8 and shove it someplace really out-of-the-way like /opt? Thanks in advance! you can always export the privkeys and import them on the other instance if they're really incompatible. Anyways, if you are building both servers you probably will use the same version and then they will be compatible between them. Adriano |