search

etotheipi / BitcoinArmory

Python-Based Bitcoin Software
Other
820 stars 617 forks source link

Scanning blockchain stopped at 230711 #59

Open meinsenf opened 11 years ago

meinsenf commented 11 years ago

Armory is not scanning the full block chain. So I do not have access to my full wallet value. Last blockchain block shown by Armory is 230711. Last blockchain block shown by bitcoind is 230937

I have restarted the program multiple times. Scanning always stops at the same block (230711).

No error is indicated by Armory itself.

Configuration Armory Version 0.87.2 beta Running on Ubuntu: uname -a shows "Linux 3.5.0-27-generic #46-Ubuntu SMP Mon Mar 25 19:58:17 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux" Bitcoind is running on same computer in version 0.8.1

bitcoind getinfo shows:

{ "version" : 80100, "protocolversion" : 70001, "walletversion" : 60000, "balance" : 0.00000000, "blocks" : 230937, "connections" : 24, "proxy" : "", "difficulty" : 7672999.92016414, "testnet" : false, "keypoololdest" : 1359399334, "keypoolsize" : 101, "paytxfee" : 0.00000000, "unlocked_until" : 0, "errors" : ""

}

feydreva commented 11 years ago

Seems I have the same issue, it stops reading the chain at block 201603 (now at 230992) any idea ?

etotheipi commented 11 years ago

My guess is that there's something wrong with the blockchain files. Armory is not able to read the whole blockchain, and even when it says it's finished scanning, it's way behind the network. You can see in the bottom right corner the number is off.

My only suggestion until I start maintaining my own blockchain files, is to redownload the blockchain. Remove everything in the Bitcoin datadir except "wallet.dat", then let it download again. If you have a fair amount of RAM, you can run Bitcoin (not Armory) with the -dbcache=1000 option to speed it up.

In fact, perhaps you can try out the new testing release I have:
https://bitcointalk.org/index.php?topic=156250.msg1655941

It's just about done... and it will do all that for you (run bitcoin in the background, specify dbcache, wait until it's synchronized).

meinsenf commented 11 years ago

etotheipi thanks for your support. I followed your recommendation to delete all but wallet.dat (and my bitcoin.conf). Then I restarted bitcoind and finally when bitcoind has reached the actual block in chain I started amory. Armory now works again. Thanks again.

Beside this here are some more details I detected: 1.) I have started armory from a terminal and this indeed produced some error output I did not see before (because I had no terminal). This output was:

Attempting to read blockchain from file: /home/bitcoin/.bitcoin/blocks/blk00012.dat /home/bitcoin/.bitcoin/blocks/blk00012.dat is 50,331,648 bytes _*ERROR: Block previously main branch, now orphan!?0381478c13b508622c847c42a3ad7eae20c6952ee81951ecb300000000000000 _ERROR: Block previously main branch, now orphan!?0381478c13b508622c847c42a3ad7eae20c6952ee81951ecb300000000000000 **ERROR: Block previously main branch, now orphan!?038f51739daa6aaa90a987ba7c839c23e472c636871e885a2802000000000000 ...

2.) Before deleting and restoring the bitcoin database I have had only few files .bitcoin/blocks/blkNNNNN.dat. blk00012.dat was the last one. The first blk files were bigger. Maybe the bitcoind version 8.0 created bigger files and then version 8.1 switch to smaller. Now after recreation of blockchain database I have quite a lot blkNNNNN.dat files. The last number is 54. Each (except the last) is 128MB in size.

I have made a copy of the old .bitcoin directory. If you are interested in the database files from there we may find a way to transfer them to you.

etotheipi commented 11 years ago

Was your #1 above before you you deleted and re-downloaded the block files? That's standard output for having a corrupted block in the blockfiles: it ends up with a bad block, it is rejected, and then all subsequent blocks look like orphans (because the path/chain to the genesis block is broken).

The #2 you posted is actually expected, too. Pre-0.8.0, Bitcoin-qt used to store blk*.dat files up to 2 GB. Then they changed it, and 0.8.0+ now limits the size to the 128 MB, but only for new files. If you have the old 2 GB files, it keeps them, and continues building off of them.

Glad to hear that it worked. I wonder if other people having problems also have the same as #2 : a mixture of 0.7 and 0.8 blockfiles (they should be identical formats, but it wouldn't surprise me if something was weird, there).

meinsenf commented 11 years ago

1.) was before delete and re-download!

feydreva commented 11 years ago

Hello, I ran you new alpha version and it worked well.. It downloaded the chain again, and everyhting is back. Thx