There is no correctly working bitcoind for Debian?

[epros]

I have Debian stable release (wheezy) and need to install Bitcoin daemon (bitcoind). There is no such a package in standard wheezy repository. I've tried the next approaches:

1. To compile from GitHub sources. But I failed: process, started by "make -f makefile.unix", after ten minutes and a lot of messages ends with error 1. I don't understand why. Perhaps, the lack of some header file?

2. To get bitcoind binary, compiled for linux. I've tried two sources: (a) I downloaded archive http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.8.5/bitcoin-0.8.5-linux.tar.gz/download and extracted bin/32/bitcoind from there. (b) I installed "bitcoind" package from Debian unstable release (sid) repository. In both cases I had the same result: Daemon starts and responds to JSON requests, but it doesn't work correctly. Below I'm describing symptoms:

- After several hours of loading blockchain, respond on "getblockcount"  no longer increments (stops on some random number, last time it was 205559).
- A bit later "getinfo" request returns error message: "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade".
- A bit later, after restarting the daemon, "getblockcount" starts from 0 (!!!). I already many times begun from scratch.
- And one more symptom: I don't understand when, but sometimes JSON connection to bitcoind doesn't establish (after tens of attempts). A few minutes later things come to norm.

Here is some cuttings from "debug.log":

Code:

received block 000000000000040768674335f20d3dff6e705e3eb30054cb91ce1163687ef301
SetBestChain: new best=000000000000040768674335f20d3dff6e705e3eb30054cb91ce1163687ef301  height=205559  log2_work=68.937464 tx=8410323  date=2012-10-29 12:55:35 progress=0.150214
ProcessBlock: ACCEPTED
received block 000000000000015c80d7b124c8c9c969954b358200ab05682b174c25fede45cf
ERROR: ProcessBlock() : already have block 188398 000000000000015c80d7b124c8c9c969954b358200ab05682b174c25fede45cf
Misbehaving: 88.125.47.132:8333 (0 -> 0)
received block 0000000000000089ecdc316eaf553e5bcd9591bbd46137862829c21a6ca96189
ERROR: ProcessBlock() : already have block 188399 0000000000000089ecdc316eaf553e5bcd9591bbd46137862829c21a6ca96189
Misbehaving: 88.125.47.132:8333 (0 -> 0)

(After 505559th block some errors occur. Incorrect blocks received from some peer?)

Code:

ProcessBlock: ACCEPTED
received block 00000000000001d2ea093ba25ce17fcfd6e98d090ffa9942dd32d943f617728f
InvalidChainFound: invalid block=00000000000001d2ea093ba25ce17fcfd6e98d090ffa9942dd32d943f617728f  height=205565  log2_work=61.018525  date=2012-10-29 13:20:32
InvalidChainFound:  current best=000000000000040768674335f20d3dff6e705e3eb30054cb91ce1163687ef301  height=205559  log2_work=60.968772  date=2012-10-29 12:55:35
ProcessBlock: ACCEPTED
received block 0000000000000006a6bf68dbc68f0a6ff10c6e408c794d77d4dd00d11210ac7c
InvalidChainFound: invalid block=0000000000000006a6bf68dbc68f0a6ff10c6e408c794d77d4dd00d11210ac7c  height=205566  log2_work=61.026653  date=2012-10-29 13:35:38
InvalidChainFound:  current best=000000000000040768674335f20d3dff6e705e3eb30054cb91ce1163687ef301  height=205559  log2_work=60.968772  date=2012-10-29 12:55:35
InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
ProcessBlock: ACCEPTED
Added 1 addresses from 85.24.169.132: 39 tried, 14390 new
stored orphan tx 9e42c3024049649daf7be471340b756a035800e08ca06314c50900207256ad42 (mapsz 139)
received block 00000000000003aa6a32a3e8372569554e1dfd71c05419193cd49611a1d273fa
InvalidChainFound: invalid block=00000000000003aa6a32a3e8372569554e1dfd71c05419193cd49611a1d273fa  height=205567  log2_work=61.034736  date=2012-10-29 14:04:42
InvalidChainFound:  current best=000000000000040768674335f20d3dff6e705e3eb30054cb91ce1163687ef301  height=205559  log2_work=60.968772  date=2012-10-29 12:55:35
InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.

(A bit later bitcoind already doesn't accept correct blocks?)

Code:

Bitcoin version v0.8.5.0-gef14a26-beta ()
Using OpenSSL version OpenSSL 1.0.1e 11 Feb 2013
Startup time: 2013-11-26 14:25:35
Default data directory /.bitcoin
Using data directory /etc/.bitcoin/
Using at most 125 connections (8192 file descriptors available)
Using 2 threads for script verification
init message: Verifying wallet...
dbenv.open LogDir=/etc/.bitcoin/database ErrorFile=/etc/.bitcoin/db.log
Bound to [::]:8333
Bound to 0.0.0.0:8333
init message: Loading block index...
Opening LevelDB in /etc/.bitcoin/blocks/index
Opened LevelDB successfully
Opening LevelDB in /etc/.bitcoin/chainstate
Opened LevelDB successfully
LoadBlockIndexDB(): last block file = 0
LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=73, size=6372288, heights=0...205631, time=2009-01-03...2012-10-29)
LoadBlockIndexDB(): transaction index disabled
init message: Verifying blocks...
 block index             355ms
init message: Loading wallet...
nFileVersion = 80500
 wallet                 1511ms
SetBestChain: new best=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f  height=0  log2_work=32.000022  tx=1  date=2009-01-03 18:15:05 progress=0.000000

(This is after restart of the daemon. I see "height=0" here. Does it mean reset of "getblockcount"?)

Code:

received block 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048
Pre-allocating up to position 0x100000 in rev00000.dat
SetBestChain: new best=00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048  height=1  log2_work=33.000022  tx=2  date=2009-01-09 02:54:25 progress=0.000000
ProcessBlock: ACCEPTED
received block 000000006a625f06636b8bb6ac7b960a8d03705d1ace08b1a19da3fdcc99ddbd
SetBestChain: new best=000000006a625f06636b8bb6ac7b960a8d03705d1ace08b1a19da3fdcc99ddbd  height=2  log2_work=33.584985  tx=3  date=2009-01-09 02:55:44 progress=0.000000
ProcessBlock: ACCEPTED
received block 0000000082b5015589a3fdf2d4baff403e6f0be035a5d9742c1cae6295464449
SetBestChain: new best=0000000082b5015589a3fdf2d4baff403e6f0be035a5d9742c1cae6295464449  height=3  log2_work=34.000022  tx=4  date=2009-01-09 03:02:53 progress=0.000000

(This is a bit later. I see, that "height" now is counting from the beginning.)

Please help. I would choose alternative bitcoin client (multibit or electrum), but I need blockchain locally loaded (headers of last few thousands at least).

[1715212935]

1715212935

[1715212935]

1715212935

[escrow.ms]

Proper process
https://js.gg/installing-bitcoind-on-debian-wheezy-7/

Do it from scratch, Just use 0.8.5 Instead of 0.8.1 which is in article.

[epros]

Proper process
https://js.gg/installing-bitcoind-on-debian-wheezy-7/

Do it from scratch, Just use 0.8.5 Instead of 0.8.1 which is in article.

I did it all early (except little details). Now I tried to do exactly what is written. And I have some errors (and no results of compilation).

Here is two last output strings of "make -f makefile.unix":

Code:

/usr/include/boost/thread/xtime.hpp:88:1: error: expected declaration before ‘}’ token
make: *** [obj/alert.o] Error 1

[epros]

Ok, I found out that the reason of failed compilation was broken version of libboost1.49-dev package in stable release of Debian.
I renewed version of the library and have the bitcoind successfully compiled now. Hope that it works better than binaries I had before...

[epros]

No, the same misbehavior repeats in compiled version:

Code:

ProcessBlock: ACCEPTED
received block 0000000000038703a7ec5ef25ac27471d1db2b32e7b8d1414e078fcdc3f0abeb
SetBestChain: new best=0000000000038703a7ec5ef25ac27471d1db2b32e7b8d1414e078fcdc3f0abeb  height=101997  log2_work=54.761447  tx=3540  date=2011-01-10 20:34:35 progress=0.000063
ProcessBlock: ACCEPTED
received block 0000000000030c522a40397eaf099b1572d7368a31d0891f71c7222d7980dfa8
ERROR: ConnectBlock() : inputs missing/spent
InvalidChainFound: invalid block=0000000000030c522a40397eaf099b1572d7368a31d0891f71c7222d7980dfa8  height=101998  log2_work=54.764752  date=2011-01-10 20:37:04
InvalidChainFound:  current best=0000000000038703a7ec5ef25ac27471d1db2b32e7b8d1414e078fcdc3f0abeb  height=101997  log2_work=54.761447  date=2011-01-10 20:34:35
InvalidChainFound: invalid block=0000000000030c522a40397eaf099b1572d7368a31d0891f71c7222d7980dfa8  height=101998  log2_work=54.764752  date=2011-01-10 20:37:04
InvalidChainFound:  current best=0000000000038703a7ec5ef25ac27471d1db2b32e7b8d1414e078fcdc3f0abeb  height=101997  log2_work=54.761447  date=2011-01-10 20:34:35

But 0000000000030c522a40397eaf099b1572d7368a31d0891f71c7222d7980dfa8 is a VALID block height=101998!!!

And a bit later:

Code:

received block 0000000000038b80cf5db1173e96f2290cfda12c505b0fe1bd37d6975e164a8a
InvalidChainFound: invalid block=0000000000038b80cf5db1173e96f2290cfda12c505b0fe1bd37d6975e164a8a  height=101999  log2_work=54.76805  date=2011-01-10 20:39:08
InvalidChainFound:  current best=0000000000038703a7ec5ef25ac27471d1db2b32e7b8d1414e078fcdc3f0abeb  height=101997  log2_work=54.761447  date=2011-01-10 20:34:35
ProcessBlock: ACCEPTED
received block 00000000000335c47dd6ae953912d172a4d9839355f2083165043bb6f43c2f58
InvalidChainFound: invalid block=00000000000335c47dd6ae953912d172a4d9839355f2083165043bb6f43c2f58  height=102000  log2_work=54.77134  date=2011-01-10 20:39:40
InvalidChainFound:  current best=0000000000038703a7ec5ef25ac27471d1db2b32e7b8d1414e078fcdc3f0abeb  height=101997  log2_work=54.761447  date=2011-01-10 20:34:35
ProcessBlock: ACCEPTED
received block 0000000000035107dce8eb675c6fa9a08c7617c109b3553ad8f208dda24065a6
InvalidChainFound: invalid block=0000000000035107dce8eb675c6fa9a08c7617c109b3553ad8f208dda24065a6  height=102001  log2_work=54.774623  date=2011-01-10 20:41:59
InvalidChainFound:  current best=0000000000038703a7ec5ef25ac27471d1db2b32e7b8d1414e078fcdc3f0abeb  height=101997  log2_work=54.761447  date=2011-01-10 20:34:35
ProcessBlock: ACCEPTED

And so on.

What is wrong? Now I have doubts that such a product as "standard bitcoin client" exists...

[epros]

Wow, people with the same problem detected, look here.
Now I'm trying to restart with parameter -par=1 set.

[MidGe]

I have the same problem. What is more interesting is that it is happening at the same place than for you, that is on or about the 28/29th Sep 2012! AS I have said it happened whether loading from bootstrap.dat or from the network, suggesting some data error in the chain!

This very specific error has been reported a number of times already, as I am finding out searching these forums.  I have not been able to find a real solution to it yet.

[MidGe]

I have now tried the latest version (0.8.6), and I still have the same problem.

Is there any way I can contribute to resolving this issue?  It is one that does seem to occur in a number of cases (I found that out doing a Google search or a search on these forum). Is the debug log, or part of it useful?