Topic: Armory hangs at Organizing Blockchain (Read 1631 times)
That is the big new feature goatpig is working on at the moment with v0.94...
To my surprise it seems to be working now.
Great.
Thanks everyone for the comments.
124GB for both BitcoinCore and Armory.
I hope some future version has a solution for this double blockchain-size.
Great.
Thanks everyone for the comments.
124GB for both BitcoinCore and Armory.
I hope some future version has a solution for this double blockchain-size.
Just started from scratch again.
First uninstalling Armory and BitcoinCore, including data-folders of Core and Armory.
installed BitcoinCore 0.12.0
installed Armory
started Armory
This is going to take a while again, downloading the blockchain
First uninstalling Armory and BitcoinCore, including data-folders of Core and Armory.
installed BitcoinCore 0.12.0
installed Armory
started Armory
This is going to take a while again, downloading the blockchain
The first time I tried Armory I already had a fully downloaded blockchain I copied from my Linux-box (Bitcoin Core 0.11.1).
I got an error in Armory: Bad Allocation
I then started from scratch.
First uninstalling Armory and BitcoinCore, including data-folders of Core and Armory.
I installed BitcoinCore 0.11.1
Waited untill the blockchain was fully loaded.
Then installed Armory.
And then I posted this topic.
The first blockchain I useds works flawless, including the rescan-option (after insterting a new private key).
Again a corrupted blockchain? Two times a corrupted blockchain with the latest one being fresh?
BitcoinCore works just fine.
I just uninstalled Armory again, also deleting the data-folder. This includes the Armory-database, right?
Started Armory.
No change in the folders except for the changes just after first starting Armory.
I also tried to start Core first and then Armory (after changing the necessary setting for that).
Still the same result
I got an error in Armory: Bad Allocation
I then started from scratch.
First uninstalling Armory and BitcoinCore, including data-folders of Core and Armory.
I installed BitcoinCore 0.11.1
Waited untill the blockchain was fully loaded.
Then installed Armory.
And then I posted this topic.
The first blockchain I useds works flawless, including the rescan-option (after insterting a new private key).
Again a corrupted blockchain? Two times a corrupted blockchain with the latest one being fresh?
BitcoinCore works just fine.
I just uninstalled Armory again, also deleting the data-folder. This includes the Armory-database, right?
Started Armory.
No change in the folders except for the changes just after first starting Armory.
I also tried to start Core first and then Armory (after changing the necessary setting for that).
Still the same result
Try rebuilding your Armory databases. If that doesn't work, delete the databases folder yourself.
IIRC, this was usually caused by blockchain corruption. I noticed that you're on Windows. It was (still is?) notoriously bad at handling Core's LevelDB database. You'd see blockchain corruption quite often. 0.11.2 and 0.12 supposedly fixed this. (I'm not on Windows and can't comment.) So, you may need to download the blockchain again now that you're on 0.12. goatpig can confirm whether or not what I said is accurate. 
Just gave it up and quitted Armory.
Uninstalled Bitcoin Core 0.11.1 64bit
Installed Bitcoin Core 0.12.0 64bit
Same result after starting Armory, but will wait for a while.
Does anybody have a clue on what is going on?
Uninstalled Bitcoin Core 0.11.1 64bit
Installed Bitcoin Core 0.12.0 64bit
Same result after starting Armory, but will wait for a while.
Does anybody have a clue on what is going on?
And just now, after 3 hours of running:
armorylog.txt :
2016-03-01 17:48 (ERROR) -- Networking.pyc:359 - ***Connection to Satoshi client LOST! Attempting to reconnect...
2016-03-01 17:48 (INFO) -- ArmoryQt.py:6010 - Dashboard switched to "Scanning" mode
2016-03-01 17:48 (INFO) -- ArmoryQt.py:2546 - Setting netmode: 1
2016-03-01 17:48 (INFO) -- Networking.pyc:65 - Connection initiated. Start handshake
2016-03-01 17:48 (INFO) -- ArmoryQt.py:6010 - Dashboard switched to "Scanning" mode
2016-03-01 17:48 (INFO) -- Networking.pyc:156 - Received version message from peer:
2016-03-01 17:48 (INFO) -- Networking.pyc:157 - Version: 70002
2016-03-01 17:48 (INFO) -- Networking.pyc:158 - SubVersion: /Satoshi:0.11.1/
2016-03-01 17:48 (INFO) -- Networking.pyc:159 - TimeStamp: 1456850902
2016-03-01 17:48 (INFO) -- Networking.pyc:160 - StartHeight: 400697
2016-03-01 17:48 (INFO) -- Networking.pyc:350 - Handshake finished, connection open!
and again:
2016-03-01 19:18 (ERROR) -- Networking.pyc:359 - ***Connection to Satoshi client LOST! Attempting to reconnect...
2016-03-01 19:18 (INFO) -- ArmoryQt.py:6010 - Dashboard switched to "Scanning" mode
2016-03-01 19:18 (INFO) -- ArmoryQt.py:2546 - Setting netmode: 1
2016-03-01 19:18 (INFO) -- Networking.pyc:65 - Connection initiated. Start handshake
2016-03-01 19:18 (INFO) -- ArmoryQt.py:6010 - Dashboard switched to "Scanning" mode
2016-03-01 19:18 (INFO) -- Networking.pyc:156 - Received version message from peer:
2016-03-01 19:18 (INFO) -- Networking.pyc:157 - Version: 70002
2016-03-01 19:18 (INFO) -- Networking.pyc:158 - SubVersion: /Satoshi:0.11.1/
2016-03-01 19:18 (INFO) -- Networking.pyc:159 - TimeStamp: 1456856318
2016-03-01 19:18 (INFO) -- Networking.pyc:160 - StartHeight: 400703
2016-03-01 19:18 (INFO) -- Networking.pyc:350 - Handshake finished, connection open!
and again:
2016-03-01 20:48 (ERROR) -- Networking.pyc:359 - ***Connection to Satoshi client LOST! Attempting to reconnect...
2016-03-01 20:48 (INFO) -- ArmoryQt.py:6010 - Dashboard switched to "Scanning" mode
2016-03-01 20:48 (INFO) -- ArmoryQt.py:2546 - Setting netmode: 1
2016-03-01 20:49 (INFO) -- Networking.pyc:65 - Connection initiated. Start handshake
2016-03-01 20:49 (INFO) -- ArmoryQt.py:6010 - Dashboard switched to "Scanning" mode
2016-03-01 20:49 (INFO) -- Networking.pyc:156 - Received version message from peer:
2016-03-01 20:49 (INFO) -- Networking.pyc:157 - Version: 70002
2016-03-01 20:49 (INFO) -- Networking.pyc:158 - SubVersion: /Satoshi:0.11.1/
2016-03-01 20:49 (INFO) -- Networking.pyc:159 - TimeStamp: 1456861768
2016-03-01 20:49 (INFO) -- Networking.pyc:160 - StartHeight: 400711
2016-03-01 20:49 (INFO) -- Networking.pyc:350 - Handshake finished, connection open!
Still no change in rest of the Armory-folders
This is what Armory looks like:
Is this still normal behaviour?
armorylog.txt :
2016-03-01 17:48 (ERROR) -- Networking.pyc:359 - ***Connection to Satoshi client LOST! Attempting to reconnect...
2016-03-01 17:48 (INFO) -- ArmoryQt.py:6010 - Dashboard switched to "Scanning" mode
2016-03-01 17:48 (INFO) -- ArmoryQt.py:2546 - Setting netmode: 1
2016-03-01 17:48 (INFO) -- Networking.pyc:65 - Connection initiated. Start handshake
2016-03-01 17:48 (INFO) -- ArmoryQt.py:6010 - Dashboard switched to "Scanning" mode
2016-03-01 17:48 (INFO) -- Networking.pyc:156 - Received version message from peer:
2016-03-01 17:48 (INFO) -- Networking.pyc:157 - Version: 70002
2016-03-01 17:48 (INFO) -- Networking.pyc:158 - SubVersion: /Satoshi:0.11.1/
2016-03-01 17:48 (INFO) -- Networking.pyc:159 - TimeStamp: 1456850902
2016-03-01 17:48 (INFO) -- Networking.pyc:160 - StartHeight: 400697
2016-03-01 17:48 (INFO) -- Networking.pyc:350 - Handshake finished, connection open!
and again:
2016-03-01 19:18 (ERROR) -- Networking.pyc:359 - ***Connection to Satoshi client LOST! Attempting to reconnect...
2016-03-01 19:18 (INFO) -- ArmoryQt.py:6010 - Dashboard switched to "Scanning" mode
2016-03-01 19:18 (INFO) -- ArmoryQt.py:2546 - Setting netmode: 1
2016-03-01 19:18 (INFO) -- Networking.pyc:65 - Connection initiated. Start handshake
2016-03-01 19:18 (INFO) -- ArmoryQt.py:6010 - Dashboard switched to "Scanning" mode
2016-03-01 19:18 (INFO) -- Networking.pyc:156 - Received version message from peer:
2016-03-01 19:18 (INFO) -- Networking.pyc:157 - Version: 70002
2016-03-01 19:18 (INFO) -- Networking.pyc:158 - SubVersion: /Satoshi:0.11.1/
2016-03-01 19:18 (INFO) -- Networking.pyc:159 - TimeStamp: 1456856318
2016-03-01 19:18 (INFO) -- Networking.pyc:160 - StartHeight: 400703
2016-03-01 19:18 (INFO) -- Networking.pyc:350 - Handshake finished, connection open!
and again:
2016-03-01 20:48 (ERROR) -- Networking.pyc:359 - ***Connection to Satoshi client LOST! Attempting to reconnect...
2016-03-01 20:48 (INFO) -- ArmoryQt.py:6010 - Dashboard switched to "Scanning" mode
2016-03-01 20:48 (INFO) -- ArmoryQt.py:2546 - Setting netmode: 1
2016-03-01 20:49 (INFO) -- Networking.pyc:65 - Connection initiated. Start handshake
2016-03-01 20:49 (INFO) -- ArmoryQt.py:6010 - Dashboard switched to "Scanning" mode
2016-03-01 20:49 (INFO) -- Networking.pyc:156 - Received version message from peer:
2016-03-01 20:49 (INFO) -- Networking.pyc:157 - Version: 70002
2016-03-01 20:49 (INFO) -- Networking.pyc:158 - SubVersion: /Satoshi:0.11.1/
2016-03-01 20:49 (INFO) -- Networking.pyc:159 - TimeStamp: 1456861768
2016-03-01 20:49 (INFO) -- Networking.pyc:160 - StartHeight: 400711
2016-03-01 20:49 (INFO) -- Networking.pyc:350 - Handshake finished, connection open!
Still no change in rest of the Armory-folders
This is what Armory looks like:
Is this still normal behaviour?
Intel Core i5 3340M 2,7 GHz
16GB memory
117GB free ssd-space (after BitcoinCore blockchain download)
Windows 7 64bit
Armory 0.93.3
Bitcoin Core 0.11.1 64bit
Blockchain was fully loaded before installing/starting Armory.
After starting Armory it seems to hang at Organizing Blockchain. Over an hour now.
The bar is moving and the wheel-icon is turning.
About 26% cpu-usage
BitcoinCore and Armory have been installed in default folders.
No wallets have been created by me.
Antivirus has been set not to scan the data-folders (username removed by me) :
C:\Users\XXXXXXXXX\AppData\Roaming\Armory
C:\Users\XXXXXXXXX\AppData\Roaming\Bitcoin
No change in any Armory-folders after an hour running Armory
Except for announce.file & armorylog.txt :
2016-03-01 15:47 (INFO) -- announcefetch.pyc:271 - Fetching: https://bitcoinarmory.com/announce.txt
2016-03-01 15:47 (ERROR) -- announcefetch.pyc:283 - Specified URL was inaccessible
2016-03-01 15:47 (ERROR) -- announcefetch.pyc:284 - Tried: https://bitcoinarmory.com/announce.txt
2016-03-01 15:47 (INFO) -- announcefetch.pyc:271 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt
Last lines before that :
2016-03-01 14:48 (INFO) -- Networking.pyc:156 - Received version message from peer:
2016-03-01 14:48 (INFO) -- Networking.pyc:157 - Version: 70002
2016-03-01 14:48 (INFO) -- Networking.pyc:158 - SubVersion: /Satoshi:0.11.1/
2016-03-01 14:48 (INFO) -- Networking.pyc:159 - TimeStamp: 1456840091
2016-03-01 14:48 (INFO) -- Networking.pyc:160 - StartHeight: 400682
2016-03-01 14:48 (INFO) -- Networking.pyc:350 - Handshake finished, connection open!
contents of armorycpplog.txt (username removed by me) :
Log file opened at 1456840062: C:\Users\XXXXXXXXX\AppData\Roaming\Armory\armorycpplog.txt
-INFO - 1456840092: (..\BlockUtils.cpp:918) blkfile dir: C:\Users\XXXXXXXXX\AppData\Roaming\Bitcoin\blocks
-INFO - 1456840092: (..\BlockUtils.cpp:919) lmdb dir: C:\Users\XXXXXXXXX\AppData\Roaming\Armory\databases
-INFO - 1456840092: (..\lmdb_wrapper.cpp:478) Opening databases...
-INFO - 1456840092: (..\BlockUtils.cpp:1250) Executing: doInitialSyncOnLoad
-INFO - 1456840092: (..\BlockUtils.cpp:1321) Total number of blk*.dat files: 458
-INFO - 1456840092: (..\BlockUtils.cpp:1322) Total blockchain bytes: 61,239,784,836
-INFO - 1456840092: (..\BlockUtils.cpp:1695) Reading headers from db
-WARN - 1456840092: (..\lmdb_wrapper.cpp:1478) No headers in DB yet!
-INFO - 1456840092: (..\BlockUtils.cpp:1721) Found 1 headers in db
-DEBUG - 1456840092: (..\Blockchain.cpp:211) Organizing chain w/ rebuild
-WARN - 1456840092: (..\BlockUtils.cpp:1351) --- Fetching SSH summaries for 0 registered addresses
-INFO - 1456840092: (..\BlockUtils.cpp:1364) Left off at file 0, offset 0
-INFO - 1456840092: (..\BlockUtils.cpp:1367) Reading headers and building chain...
-INFO - 1456840092: (..\BlockUtils.cpp:1368) Starting at block file 0 offset 0
-INFO - 1456840092: (..\BlockUtils.cpp:1370) Block height 0
-ERROR - 1456840092: (..\BlockUtils.cpp:639) Next block header found at offset 16777403
-DEBUG - 1456840096: (..\Blockchain.cpp:211) Organizing chain w/ rebuild
What is Armory doing?
Why do I not see any significant changes in the folders over time?
16GB memory
117GB free ssd-space (after BitcoinCore blockchain download)
Windows 7 64bit
Armory 0.93.3
Bitcoin Core 0.11.1 64bit
Blockchain was fully loaded before installing/starting Armory.
After starting Armory it seems to hang at Organizing Blockchain. Over an hour now.
The bar is moving and the wheel-icon is turning.
About 26% cpu-usage
BitcoinCore and Armory have been installed in default folders.
No wallets have been created by me.
Antivirus has been set not to scan the data-folders (username removed by me) :
C:\Users\XXXXXXXXX\AppData\Roaming\Armory
C:\Users\XXXXXXXXX\AppData\Roaming\Bitcoin
No change in any Armory-folders after an hour running Armory
Except for announce.file & armorylog.txt :
2016-03-01 15:47 (INFO) -- announcefetch.pyc:271 - Fetching: https://bitcoinarmory.com/announce.txt
2016-03-01 15:47 (ERROR) -- announcefetch.pyc:283 - Specified URL was inaccessible
2016-03-01 15:47 (ERROR) -- announcefetch.pyc:284 - Tried: https://bitcoinarmory.com/announce.txt
2016-03-01 15:47 (INFO) -- announcefetch.pyc:271 - Fetching: https://s3.amazonaws.com/bitcoinarmory-media/announce.txt
Last lines before that :
2016-03-01 14:48 (INFO) -- Networking.pyc:156 - Received version message from peer:
2016-03-01 14:48 (INFO) -- Networking.pyc:157 - Version: 70002
2016-03-01 14:48 (INFO) -- Networking.pyc:158 - SubVersion: /Satoshi:0.11.1/
2016-03-01 14:48 (INFO) -- Networking.pyc:159 - TimeStamp: 1456840091
2016-03-01 14:48 (INFO) -- Networking.pyc:160 - StartHeight: 400682
2016-03-01 14:48 (INFO) -- Networking.pyc:350 - Handshake finished, connection open!
contents of armorycpplog.txt (username removed by me) :
Log file opened at 1456840062: C:\Users\XXXXXXXXX\AppData\Roaming\Armory\armorycpplog.txt
-INFO - 1456840092: (..\BlockUtils.cpp:918) blkfile dir: C:\Users\XXXXXXXXX\AppData\Roaming\Bitcoin\blocks
-INFO - 1456840092: (..\BlockUtils.cpp:919) lmdb dir: C:\Users\XXXXXXXXX\AppData\Roaming\Armory\databases
-INFO - 1456840092: (..\lmdb_wrapper.cpp:478) Opening databases...
-INFO - 1456840092: (..\BlockUtils.cpp:1250) Executing: doInitialSyncOnLoad
-INFO - 1456840092: (..\BlockUtils.cpp:1321) Total number of blk*.dat files: 458
-INFO - 1456840092: (..\BlockUtils.cpp:1322) Total blockchain bytes: 61,239,784,836
-INFO - 1456840092: (..\BlockUtils.cpp:1695) Reading headers from db
-WARN - 1456840092: (..\lmdb_wrapper.cpp:1478) No headers in DB yet!
-INFO - 1456840092: (..\BlockUtils.cpp:1721) Found 1 headers in db
-DEBUG - 1456840092: (..\Blockchain.cpp:211) Organizing chain w/ rebuild
-WARN - 1456840092: (..\BlockUtils.cpp:1351) --- Fetching SSH summaries for 0 registered addresses
-INFO - 1456840092: (..\BlockUtils.cpp:1364) Left off at file 0, offset 0
-INFO - 1456840092: (..\BlockUtils.cpp:1367) Reading headers and building chain...
-INFO - 1456840092: (..\BlockUtils.cpp:1368) Starting at block file 0 offset 0
-INFO - 1456840092: (..\BlockUtils.cpp:1370) Block height 0
-ERROR - 1456840092: (..\BlockUtils.cpp:639) Next block header found at offset 16777403
-DEBUG - 1456840096: (..\Blockchain.cpp:211) Organizing chain w/ rebuild
What is Armory doing?
Why do I not see any significant changes in the folders over time?
Jump to: