Topic: Armory 0.94.1 is out - page 8. (Read 12086 times)
Armory is failing to shutdown bitcoind somehow. Turn off auto management and deal with BitcoinQt manually instead.
I install new Armory win64 with core 0.12.1 and in generality it work.
But when I tried to close Armory - program froze and don't closed.
In log:
Then I wait more than 10 minutes, kill process and restart Armory.
But sometimes (in previous version) and now start with gray transactions (tab transaction active, but not unabled) and I can't browse transactions, but 14-15pcs visible (in disabled mode).
If I go to Dashboard tab I can't come back (button transaction gray and disabled).
Armory write that offline - loading database headers (long time - more than hour and nothing changed).
Image, that many time I see in Armory (from 19:16 to 20:17):
http://s019.radikal.ru/i615/1604/72/40f9591a435a.jpg
I shoutdown Armory and close OK.
Then I run Armory again - start and close without problem in few minutes. WTF?) Connection to internet stable all time:
I think may be this line do Armory offline and then don't come back: 2016-04-24 19:16 (INFO) -- ArmoryQt.py:5801 - Dashboard switched to auto-BadConnection (but blocks downloading!).
But when I tried to close Armory - program froze and don't closed.
In log:
Code:
2016-04-24 18:43 (INFO) -- ArmoryQt.py:6171 - Current block number: 408740
2016-04-24 18:44 (INFO) -- ArmoryQt.py:6685 - BDM is safe for clean shutdown
2016-04-24 18:44 (INFO) -- SDM.pyc:683 - Called stopBitcoind
2016-04-24 18:44 (ERROR) -- SDM.pyc:894 - generic error
Traceback (most recent call last):
File "SDM.pyc", line 857, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 97, in __call__
File "httplib.pyc", line 1074, in getresponse
File "httplib.pyc", line 415, in begin
File "httplib.pyc", line 379, in _read_status
BadStatusLine: ''
2016-04-24 18:44 (ERROR) -- ArmoryUtils.pyc:3168 - Error in pybkgdthread: ''
Traceback (most recent call last):
File "armoryengine\ArmoryUtils.pyc", line 3166, in run
File "armoryengine\ArmoryUtils.pyc", line 3103, in funcPartial
File "SDM.pyc", line 857, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 97, in __call__
File "httplib.pyc", line 1074, in getresponse
File "httplib.pyc", line 415, in begin
File "httplib.pyc", line 379, in _read_status
BadStatusLine: ''
2016-04-24 18:45 (ERROR) -- Networking.pyc:350 - ***Connection to Satoshi client LOST! Attempting to reconnect...
2016-04-24 18:45 (INFO) -- ArmoryQt.py:6727 - Attempting to close the main window!
2016-04-24 18:45 (WARNING) -- SDM.pyc:768 - Overriding not-available state. This should happen 0-5 times
Then I wait more than 10 minutes, kill process and restart Armory.
But sometimes (in previous version) and now start with gray transactions (tab transaction active, but not unabled) and I can't browse transactions, but 14-15pcs visible (in disabled mode).
If I go to Dashboard tab I can't come back (button transaction gray and disabled).
Armory write that offline - loading database headers (long time - more than hour and nothing changed).
Image, that many time I see in Armory (from 19:16 to 20:17):
http://s019.radikal.ru/i615/1604/72/40f9591a435a.jpg
I shoutdown Armory and close OK.
Code:
2016-04-24 19:08 (INFO) -- SDM.pyc:669 - PID of bitcoind: 12800
2016-04-24 19:08 (INFO) -- SDM.pyc:670 - PID of armory: 5136
2016-04-24 19:08 (INFO) -- ArmoryUtils.pyc:593 - Executing popen: ['.\\guardian.exe', '5136', '12800']
2016-04-24 19:08 (INFO) -- SDM.pyc:848 - Creating proxy in SDM: host=127.0.0.1, port=8332
2016-04-24 19:08 (INFO) -- ArmoryQt.py:1527 - setupUriRegistration
2016-04-24 19:08 (INFO) -- ArmoryQt.py:1645 - URL-register action: AskUser
2016-04-24 19:08 (INFO) -- ArmoryQt.py:664 - Usermode: Expert
2016-04-24 19:08 (INFO) -- ArmoryQt.py:1823 - Changing usermode:
2016-04-24 19:08 (INFO) -- ArmoryQt.py:1824 - From: Expert
2016-04-24 19:08 (INFO) -- ArmoryQt.py:1832 - To: Expert
2016-04-24 19:08 (INFO) -- ArmoryQt.py:5812 - Dashboard switched to auto-InitSync
2016-04-24 19:13 (INFO) -- ArmoryQt.py:2498 - loadBlockchainIfNecessary
2016-04-24 19:13 (INFO) -- ArmoryQt.py:2519 - Setting netmode: 1
2016-04-24 19:13 (INFO) -- ArmoryQt.py:5935 - Dashboard switched to "Scanning" mode
2016-04-24 19:13 (INFO) -- Networking.pyc:64 - Connection initiated. Start handshake
2016-04-24 19:13 (INFO) -- ArmoryQt.py:5935 - Dashboard switched to "Scanning" mode
2016-04-24 19:13 (INFO) -- Networking.pyc:155 - Received version message from peer:
2016-04-24 19:13 (INFO) -- Networking.pyc:156 - Version: 70012
2016-04-24 19:13 (INFO) -- Networking.pyc:157 - SubVersion: /Satoshi:0.12.1/
2016-04-24 19:13 (INFO) -- Networking.pyc:158 - TimeStamp: 1461514397
2016-04-24 19:13 (INFO) -- Networking.pyc:159 - StartHeight: 408740
2016-04-24 19:13 (INFO) -- Networking.pyc:341 - Handshake finished, connection open!
2016-04-24 19:16 (INFO) -- ArmoryQt.py:5801 - Dashboard switched to auto-BadConnection
2016-04-24 19:16 (INFO) -- ArmoryQt.py:3121 - Current block number: 408741
2016-04-24 19:17 (INFO) -- ArmoryQt.py:6163 - New Block! : 408742
2016-04-24 19:17 (INFO) -- ArmoryQt.py:6171 - Current block number: 408742
2016-04-24 19:43 (INFO) -- ArmoryQt.py:6163 - New Block! : 408743
2016-04-24 19:43 (INFO) -- ArmoryQt.py:6171 - Current block number: 408743
2016-04-24 19:52 (INFO) -- ArmoryQt.py:6163 - New Block! : 408744
2016-04-24 19:52 (INFO) -- ArmoryQt.py:6171 - Current block number: 408744
2016-04-24 20:07 (INFO) -- ArmoryQt.py:6163 - New Block! : 408745
2016-04-24 20:07 (INFO) -- ArmoryQt.py:6171 - Current block number: 408745
2016-04-24 20:08 (INFO) -- Networking.pyc:214 - Received new block. 000000000000000000234ba7945b1b431a420e48ba3190ac33f26cf3db6bf193
2016-04-24 20:08 (INFO) -- ArmoryQt.py:6163 - New Block! : 408746
2016-04-24 20:08 (INFO) -- ArmoryQt.py:6171 - Current block number: 408746
2016-04-24 20:10 (INFO) -- ArmoryQt.py:6163 - New Block! : 408747
2016-04-24 20:10 (INFO) -- ArmoryQt.py:6171 - Current block number: 408747
2016-04-24 20:17 (INFO) -- ArmoryQt.py:6685 - BDM is safe for clean shutdown
2016-04-24 20:17 (INFO) -- SDM.pyc:683 - Called stopBitcoind
2016-04-24 20:17 (ERROR) -- SDM.pyc:894 - generic error
Traceback (most recent call last):
File "SDM.pyc", line 857, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 97, in __call__
File "httplib.pyc", line 1074, in getresponse
File "httplib.pyc", line 415, in begin
File "httplib.pyc", line 379, in _read_status
BadStatusLine: ''
2016-04-24 20:17 (ERROR) -- ArmoryUtils.pyc:3168 - Error in pybkgdthread: ''
Traceback (most recent call last):
File "armoryengine\ArmoryUtils.pyc", line 3166, in run
File "armoryengine\ArmoryUtils.pyc", line 3103, in funcPartial
File "SDM.pyc", line 857, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 97, in __call__
File "httplib.pyc", line 1074, in getresponse
File "httplib.pyc", line 415, in begin
File "httplib.pyc", line 379, in _read_status
BadStatusLine: ''
2016-04-24 20:17 (ERROR) -- Networking.pyc:350 - ***Connection to Satoshi client LOST! Attempting to reconnect...
2016-04-24 20:17 (INFO) -- ArmoryQt.py:6727 - Attempting to close the main window!
Then I run Armory again - start and close without problem in few minutes. WTF?) Connection to internet stable all time:
Code:
2016-04-24 20:19 (INFO) -- SDM.pyc:669 - PID of bitcoind: 18284
2016-04-24 20:19 (INFO) -- SDM.pyc:670 - PID of armory: 20248
2016-04-24 20:19 (INFO) -- ArmoryUtils.pyc:593 - Executing popen: ['.\\guardian.exe', '20248', '18284']
2016-04-24 20:19 (INFO) -- SDM.pyc:848 - Creating proxy in SDM: host=127.0.0.1, port=8332
2016-04-24 20:19 (INFO) -- ArmoryQt.py:1527 - setupUriRegistration
2016-04-24 20:19 (INFO) -- ArmoryQt.py:1645 - URL-register action: AskUser
2016-04-24 20:19 (INFO) -- ArmoryQt.py:664 - Usermode: Expert
2016-04-24 20:19 (INFO) -- ArmoryQt.py:1823 - Changing usermode:
2016-04-24 20:19 (INFO) -- ArmoryQt.py:1824 - From: Expert
2016-04-24 20:19 (INFO) -- ArmoryQt.py:1832 - To: Expert
2016-04-24 20:19 (INFO) -- ArmoryQt.py:5812 - Dashboard switched to auto-InitSync
2016-04-24 20:27 (INFO) -- ArmoryQt.py:2498 - loadBlockchainIfNecessary
2016-04-24 20:27 (INFO) -- ArmoryQt.py:2519 - Setting netmode: 1
2016-04-24 20:27 (INFO) -- ArmoryQt.py:5935 - Dashboard switched to "Scanning" mode
2016-04-24 20:27 (INFO) -- Networking.pyc:64 - Connection initiated. Start handshake
2016-04-24 20:27 (INFO) -- ArmoryQt.py:5935 - Dashboard switched to "Scanning" mode
2016-04-24 20:27 (INFO) -- Networking.pyc:155 - Received version message from peer:
2016-04-24 20:27 (INFO) -- Networking.pyc:156 - Version: 70012
2016-04-24 20:27 (INFO) -- Networking.pyc:157 - SubVersion: /Satoshi:0.12.1/
2016-04-24 20:27 (INFO) -- Networking.pyc:158 - TimeStamp: 1461518847
2016-04-24 20:27 (INFO) -- Networking.pyc:159 - StartHeight: 408747
2016-04-24 20:27 (INFO) -- Networking.pyc:341 - Handshake finished, connection open!
2016-04-24 20:34 (INFO) -- ArmoryQt.py:3121 - Current block number: 408747
2016-04-24 20:35 (INFO) -- ArmoryQt.py:6163 - New Block! : 408748
2016-04-24 20:35 (INFO) -- ArmoryQt.py:6171 - Current block number: 408748
2016-04-24 20:40 (INFO) -- ArmoryQt.py:6685 - BDM is safe for clean shutdown
2016-04-24 20:40 (INFO) -- SDM.pyc:683 - Called stopBitcoind
2016-04-24 20:41 (INFO) -- ArmoryQt.py:6727 - Attempting to close the main window!
2016-04-24 20:41 (ERROR) -- Networking.pyc:350 - ***Connection to Satoshi client LOST! Attempting to reconnect...
@Newar
are you sure that Armory is using the correct directory for .armory? it's currently in /root/, which implies you installed 0.94 while logged in as the root user? Can you try rebuilding the 0.94 db? (delete .armory/databases) It's possible that whichever erroneous contents in your previous copy of the Bitcoin blockchain also made it's way into the Armory databases, and so the tx scanning stage for Armory is essentially detecting that mismatch.
are you sure that Armory is using the correct directory for .armory? it's currently in /root/, which implies you installed 0.94 while logged in as the root user? Can you try rebuilding the 0.94 db? (delete .armory/databases) It's possible that whichever erroneous contents in your previous copy of the Bitcoin blockchain also made it's way into the Armory databases, and so the tx scanning stage for Armory is essentially detecting that mismatch.
Quote
-INFO - 1461221902: (DatabaseBuilder.cpp:195) Found 378432 headers in db
As Carlton suspects, you are using a fresh copy of the blockchain over a preexisting DB. Delete that DB, let Armory start from scratch.
Thank you both. Fixed.
goatpig, would you like a free Silver Wallet for being cool enough to keep Armory going? -> http://silverwallets.com/
That's a kind offer but I'll pass. These things look nice though =)
I just upgraded 2 of my Armory instances and have had no issues so far. I just love seeing my used space cut in half with the new database setup.
goatpig, would you like a free Silver Wallet for being cool enough to keep Armory going? -> http://silverwallets.com/
goatpig, would you like a free Silver Wallet for being cool enough to keep Armory going? -> http://silverwallets.com/
Another daft question:
How do I get the Armory icon to show on the launcher? - that's using the standard Ubuntu Gnome GUI
At present the launcher shows a grey '?'. Otherwise everything working fine.
How do I get the Armory icon to show on the launcher? - that's using the standard Ubuntu Gnome GUI
At present the launcher shows a grey '?'. Otherwise everything working fine.
You can't use the same DB as 0.93 for 0.94. Point to another folder using the --dbdir command line argument
Thanks gp. I renamed the 93.1 db folder then created a new one with standard name. All purring along fine now. If all remains well, I'll delete the old one in a day or two and get back 60+Gb of space
You can't use the same DB as 0.93 for 0.94. Point to another folder using the --dbdir command line argument
I've been using Armory for a couple years now. I'm 'techie-light' so please bare with me & apologies if this has already been answered.
System: OS - Ubuntu 15.1 15Gb real memory 15Gb virtual memory
Initially I installed 0.94.1 on top of 0.93.1 using the Git clone + make + make install instructions.
That resulted in the Armory GUI showing a successful Wallet consistency check + successful Bitcoin Engine init; then the GUI turned grey and I got a program not responding message requiring a manual close which left Bitcoind running but no Armory process running. I then uninstalled Armory leaving the settings as was and re-installed.
Result: As above except that, instead of the GUI freezing, it simply disappears.
All looks fine in the log (to me anyway - ie no errors) until the last few lines as follows:
Any pointers much appreciated
System: OS - Ubuntu 15.1 15Gb real memory 15Gb virtual memory
Initially I installed 0.94.1 on top of 0.93.1 using the Git clone + make + make install instructions.
That resulted in the Armory GUI showing a successful Wallet consistency check + successful Bitcoin Engine init; then the GUI turned grey and I got a program not responding message requiring a manual close which left Bitcoind running but no Armory process running. I then uninstalled Armory leaving the settings as was and re-installed.
Result: As above except that, instead of the GUI freezing, it simply disappears.
All looks fine in the log (to me anyway - ie no errors) until the last few lines as follows:
Code:
2016-04-22 10:44 (INFO) -- ArmoryQt.py:5812 - Dashboard switched to auto-InitSync
2016-04-22 10:44 (INFO) -- ArmoryQt.py:2498 - loadBlockchainIfNecessary
2016-04-22 10:44 (ERROR) -- ArmoryQt.py:1336 - 4 attempts to load blockchain failed. Remove mempool.bin.
2016-04-22 10:44 (ERROR) -- ArmoryQt.py:1341 - File mempool.bin does not exist. Nothing deleted.
2016-04-22 10:44 (INFO) -- ArmoryQt.py:2519 - Setting netmode: 1
2016-04-22 10:44 (INFO) -- ArmoryQt.py:5935 - Dashboard switched to "Scanning" mode
2016-04-22 10:44 (INFO) -- Networking.py:64 - Connection initiated. Start handshake
2016-04-22 10:44 (INFO) -- ArmoryQt.py:5935 - Dashboard switched to "Scanning" mode
2016-04-22 10:44 (INFO) -- Networking.py:155 - Received version message from peer:
2016-04-22 10:44 (INFO) -- Networking.py:156 - Version: 70012
2016-04-22 10:44 (INFO) -- Networking.py:157 - SubVersion: /Satoshi:0.12.0/
2016-04-22 10:44 (INFO) -- Networking.py:158 - TimeStamp: 1461318297
2016-04-22 10:44 (INFO) -- Networking.py:159 - StartHeight: 408421
2016-04-22 10:44 (INFO) -- Networking.py:341 - Handshake finished, connection open!
Quote
-INFO - 1461221902: (DatabaseBuilder.cpp:195) Found 378432 headers in db
As Carlton suspects, you are using a fresh copy of the blockchain over a preexisting DB. Delete that DB, let Armory start from scratch.
@Newar
are you sure that Armory is using the correct directory for .armory? it's currently in /root/, which implies you installed 0.94 while logged in as the root user? Can you try rebuilding the 0.94 db? (delete .armory/databases) It's possible that whichever erroneous contents in your previous copy of the Bitcoin blockchain also made it's way into the Armory databases, and so the tx scanning stage for Armory is essentially detecting that mismatch.
are you sure that Armory is using the correct directory for .armory? it's currently in /root/, which implies you installed 0.94 while logged in as the root user? Can you try rebuilding the 0.94 db? (delete .armory/databases) It's possible that whichever erroneous contents in your previous copy of the Bitcoin blockchain also made it's way into the Armory databases, and so the tx scanning stage for Armory is essentially detecting that mismatch.
Should I bitcoind -reindex?
Yes. This is a deser error, that's unmistakably corrupted block data.
I have done the reindex, and - since the error persisted - removed the blocks, chainstate and database folders of bicoind. Now after everything is fresh I still get:
Code:
(WARNING) SDM.py:768 - Overriding not-available state. This should happen 0-5 times
(ERROR) ArmoryQt.py:1336 - 32 attempts to load blockchain failed. Remove mempool.bin.
(ERROR) ArmoryQt.py:1341 - File mempool.bin does not exist. Nothing deleted.
-INFO - 1461221735: (BlockUtils.cpp:924) blkfile dir: /home/eee/.bitcoin/blocks
-INFO - 1461221735: (BlockUtils.cpp:925) lmdb dir: /root/.armory/databases
-INFO - 1461221735: (lmdb_wrapper.cpp:387) Opening databases...
-INFO - 1461221736: (BlockUtils.cpp:1105) Executing: doInitialSyncOnLoad
-INFO - 1461221736: (DatabaseBuilder.cpp:162) Reading headers from db
-INFO - 1461221902: (DatabaseBuilder.cpp:195) Found 378432 headers in db
-INFO - 1461221905: (DatabaseBuilder.cpp:43) updating HEADERS db
-DEBUG - 1461221905: (Blockchain.cpp:213) Organizing chain
-INFO - 1461221906: (DatabaseBuilder.cpp:47) updated HEADERS db in 0.948083s
-INFO - 1461221906: (DatabaseBuilder.cpp:98) scanning new blocks from #0 to #377947
--ERROR -- ERROR ERROR - - 14612219091461221909: 1461221909(: BlockchainScanner.cpp(:: BlockchainScanner.cpp(:BlockchainScanner.cpp:276276276) ) ) unknown block deser error during scan at height #unknown block deser error during scan at height #1
-ERROR - unknown block deser error during scan at height #20
1461221909: (BlockchainScanner.cpp:276) unknown block deser error during scan at height #3
terminate called without an active exception
-ERROR - 1461221909: (BlockchainScanner.cpp:276) unknown block deser error during scan at height #0
Lubuntu Trusty, 16 GB RAM, 51 GB free HDD
Any more pointers?
Thanks!
It's currently tuned to run at around 1GB.
that's interesting b/c i had to increase it from 2GB to 4GB to get it to run again.
You also have to consider what the OS consumes.
It's currently tuned to run at around 1GB.
that's interesting b/c i had to increase it from 2GB to 4GB to get it to run again.
You also have to consider what the OS consumes.
It's currently tuned to run at around 1GB.
that's interesting b/c i had to increase it from 2GB to 4GB to get it to run again.
Should I bitcoind -reindex?
Yes. This is a deser error, that's unmistakably corrupted block data.
First off, thank you for keeping the project going. Very much appreciated!
I got 0.94.1 installed and get right off the bat:
Code:
(ERROR) ArmoryQt.py:1336 - 28 attempts to load blockchain failed. Remove mempool.bin.
(ERROR) ArmoryQt.py:1341 - File mempool.bin does not exist. Nothing deleted.
-INFO - 1460704730: (BlockUtils.cpp:924) blkfile dir: /home/eee/.bitcoin/blocks
-INFO - 1460704730: (BlockUtils.cpp:925) lmdb dir: /root/.armory/databases
-INFO - 1460704730: (lmdb_wrapper.cpp:387) Opening databases...
-INFO - 1460704731: (BlockUtils.cpp:1105) Executing: doInitialSyncOnLoad
-INFO - 1460704731: (DatabaseBuilder.cpp:162) Reading headers from db
-INFO - 1460705165: (DatabaseBuilder.cpp:195) Found 378432 headers in db
-INFO - 1460705168: (DatabaseBuilder.cpp:43) updating HEADERS db
-DEBUG - 1460705168: (Blockchain.cpp:213) Organizing chain
-INFO - 1460705169: (DatabaseBuilder.cpp:47) updated HEADERS db in 0.948337s
-INFO - 1460705169: (DatabaseBuilder.cpp:98) scanning new blocks from #0 to #377947
---ERROR ERROR - - ERROR - -146070517114607051711460705171: ERROR : - : 1460705171: (BlockchainScanner.cpp:276() (BlockchainScanner.cpp:BlockchainScanner.cppunknown block deser error during scan at height #276) unknown block deser error during scan at height #2
:276) unknown block deser error during scan at height #3
(BlockchainScanner.cpp:276) unknown block deser error during scan at height #0
1
terminate called without an active exception
Should I bitcoind -reindex?
Bitcoin Core (0.12) runs fine on its own though.
How is the latest Bitcoin Core doing with the latest Armory? Any major bugs?
Unless you are running a x86 OS or you have low RAM and disabled the swap (or actually managed to fill swap partition), you can't get a bad_alloc for running out of physical RAM. This is all virtual address space, the underlying actual RAM isn't all that relevant.
bad_alloc appears when the OS fails to allocate memory. This is more often the case when a bogus amount of memory is requested (say unserializing a random chunck of 9 bytes as a varInt and allocating that absurd number) than actually exhausting all RAM on the system.
If you suspect it is actually how much memory you have available on your system, you should try and reduce the RAM Armory uses instead of increasing yours:
https://github.com/goatpig/BitcoinArmory/blob/master/cppForSwig/BlockchainScanner.h#L96
Set this value to 2 to cut the memory use in half, then
make clean
make
It's currently tuned to run at around 1GB.
bad_alloc appears when the OS fails to allocate memory. This is more often the case when a bogus amount of memory is requested (say unserializing a random chunck of 9 bytes as a varInt and allocating that absurd number) than actually exhausting all RAM on the system.
If you suspect it is actually how much memory you have available on your system, you should try and reduce the RAM Armory uses instead of increasing yours:
https://github.com/goatpig/BitcoinArmory/blob/master/cppForSwig/BlockchainScanner.h#L96
Set this value to 2 to cut the memory use in half, then
make clean
make
It's currently tuned to run at around 1GB.
Jump to: