Topic: Armory 0.96 is out - page 12. (Read 13833 times)
Show me dbLog.txt
I upgraded from Armory 0.95.1 with Bitcoin Core 0.13.2 to Armory 0.96.0 for Ubuntu/Debian 64-bit with GCC 5.3. because I had two unconfirmed transactions (2 weeks old), which I wanted to clear.
Now, the new version of Armory doesn't finish Scanning Transaction History (1 second left)....I started Bitcoin Core with "bitcoin-qt --disablewallet" manually (this was the only possibility to get it working with Armory 95.1, therefore I just continued to do the same with the new version)
In
armorylog.txt:
2017-05-10 12:32 (INFO) -- ArmoryQt.py:558 - Usermode: Expert
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1681 - Changing usermode:
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1682 - From: Expert
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1690 - To: Expert
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1814 - startBitcoindIfNecessary
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1850 - setSatoshiPaths
2017-05-10 12:32 (WARNING) -- SDM.py:396 - Spawning DB with command:ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/home/andi/.bitcoin/
blocks" --datadir="/home/andi/.armory/" --dbdir="/home/andi/.armory/databases"
2017-05-10 12:32 (INFO) -- ArmoryUtils.py:665 - Executing popen: ['ArmoryDB', '--db-type="DB_FULL"', '--cookie', '--satoshi-datadir="/home/andi/.
bitcoin/blocks"', '--datadir="/home/andi/.armory/"', '--dbdir="/home/andi/.armory/databases"']
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1882 - loadBlockchainIfNecessary
2017-05-10 12:32 (ERROR) -- ArmoryQt.py:1188 - 3 attempts to load blockchain failed. Remove mempool.bin.
2017-05-10 12:32 (ERROR) -- ArmoryQt.py:1193 - File mempool.bin does not exist. Nothing deleted.
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-10 12:32 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
...1000x
2017-05-10 12:56 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
-----------------------------------------------
Help would be very much appreciated! Should I upgrade to Bitcoin Core 0.14.1 to solve my problem?
Now, the new version of Armory doesn't finish Scanning Transaction History (1 second left)....I started Bitcoin Core with "bitcoin-qt --disablewallet" manually (this was the only possibility to get it working with Armory 95.1, therefore I just continued to do the same with the new version)
In
armorylog.txt:
2017-05-10 12:32 (INFO) -- ArmoryQt.py:558 - Usermode: Expert
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1681 - Changing usermode:
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1682 - From: Expert
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1690 - To: Expert
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1814 - startBitcoindIfNecessary
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1850 - setSatoshiPaths
2017-05-10 12:32 (WARNING) -- SDM.py:396 - Spawning DB with command:ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/home/andi/.bitcoin/
blocks" --datadir="/home/andi/.armory/" --dbdir="/home/andi/.armory/databases"
2017-05-10 12:32 (INFO) -- ArmoryUtils.py:665 - Executing popen: ['ArmoryDB', '--db-type="DB_FULL"', '--cookie', '--satoshi-datadir="/home/andi/.
bitcoin/blocks"', '--datadir="/home/andi/.armory/"', '--dbdir="/home/andi/.armory/databases"']
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1882 - loadBlockchainIfNecessary
2017-05-10 12:32 (ERROR) -- ArmoryQt.py:1188 - 3 attempts to load blockchain failed. Remove mempool.bin.
2017-05-10 12:32 (ERROR) -- ArmoryQt.py:1193 - File mempool.bin does not exist. Nothing deleted.
2017-05-10 12:32 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-10 12:32 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
...1000x
2017-05-10 12:56 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
-----------------------------------------------
Help would be very much appreciated! Should I upgrade to Bitcoin Core 0.14.1 to solve my problem?
Mine's working great. I sent a transaction and the comment says chained zc. Does that mean anything?
Means your tx is spending an unconfirmed txout.
Mine's working great. I sent a transaction and the comment says chained zc. Does that mean anything?
Armory crashed every time after scanning.
Emptied %appdata%\Armory\databases , causing Armory to rebuild the database solved this problem.
btw: Amazing that this is the only piece of software that manages to fully use my 16 GB RAM while rebuilding the database. No problem for me.
Emptied %appdata%\Armory\databases , causing Armory to rebuild the database solved this problem.
btw: Amazing that this is the only piece of software that manages to fully use my 16 GB RAM while rebuilding the database. No problem for me.
mmaped RAM, not allocated.
Wallet properties: Used addresses:
Addresses not visible. Unsure after which this happens.
Solved after restarting Armory.
Addresses not visible. Unsure after which this happens.
Solved after restarting Armory.
What do you do to get to that?
Quote
Address Book: changed Comment, but it does not stick.
Or on the other hand: The comment for an address changed in the wallet does not display in the addressbook.
Or on the other hand: The comment for an address changed in the wallet does not display in the addressbook.
Comments are broken in address book for the moment.
Quote
After doing one transaction, and restarting Armory:
Does not fully start.
Solved by restarting BitcoinCore before starting Armory.
dblog.txt:
successful start and shutdown after previous mentioned problem:
Does not fully start.
Solved by restarting BitcoinCore before starting Armory.
dblog.txt:
Code:
Log file opened at 1494367860: C:\Users\jeff\AppData\Roaming\Armory\dbLog.txt
-INFO - 1494367860: (..\main.cpp:23) Running on 4 threads
-INFO - 1494367860: (..\main.cpp:24) Ram usage level: 4
-INFO - 1494367860: (..\BlockUtils.cpp:907) blkfile dir: C:\Users\jeff\AppData\Roaming\Bitcoin\blocks
-INFO - 1494367860: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\jeff\AppData\Roaming\Armory\databases
-INFO - 1494367860: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1494367860: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO - 1494367862: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO - 1494367863: (..\DatabaseBuilder.cpp:169) Reading headers from db
-WARN - 1494367865: (..\BDM_supportClasses.cpp:1891) running 0 zc parser threads
-WARN - 1494367865: (..\BDM_supportClasses.cpp:1891) running 5 zc parser threads
-WARN - 1494367865: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-INFO - 1494367866: (..\DatabaseBuilder.cpp:208) Found 465669 headers in db
-INFO - 1494367868: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1494367868: (..\DatabaseBuilder.cpp:477) Found next block after skipping 508317bytes
-INFO - 1494367869: (..\DatabaseBuilder.cpp:268) parsed block file #862
-DEBUG - 1494367869: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1494367869: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.491s
-INFO - 1494367869: (..\DatabaseBuilder.cpp:106) scanning new blocks from #465668 to #465667
-INFO - 1494367869: (..\BlockchainScanner.cpp:52) no history to scan
-INFO - 1494367869: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO - 1494367869: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.009s
-INFO - 1494367869: (..\DatabaseBuilder.cpp:160) init db in 6.281s
-INFO - 1494367869: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-WARN - 1494367875: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN - 1494367875: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN - 1494367875: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads
-WARN - 1494367875: (..\BDM_supportClasses.cpp:1891) running 35 zc parser threads
-INFO - 1494367860: (..\main.cpp:23) Running on 4 threads
-INFO - 1494367860: (..\main.cpp:24) Ram usage level: 4
-INFO - 1494367860: (..\BlockUtils.cpp:907) blkfile dir: C:\Users\jeff\AppData\Roaming\Bitcoin\blocks
-INFO - 1494367860: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\jeff\AppData\Roaming\Armory\databases
-INFO - 1494367860: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1494367860: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO - 1494367862: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO - 1494367863: (..\DatabaseBuilder.cpp:169) Reading headers from db
-WARN - 1494367865: (..\BDM_supportClasses.cpp:1891) running 0 zc parser threads
-WARN - 1494367865: (..\BDM_supportClasses.cpp:1891) running 5 zc parser threads
-WARN - 1494367865: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-INFO - 1494367866: (..\DatabaseBuilder.cpp:208) Found 465669 headers in db
-INFO - 1494367868: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1494367868: (..\DatabaseBuilder.cpp:477) Found next block after skipping 508317bytes
-INFO - 1494367869: (..\DatabaseBuilder.cpp:268) parsed block file #862
-DEBUG - 1494367869: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1494367869: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.491s
-INFO - 1494367869: (..\DatabaseBuilder.cpp:106) scanning new blocks from #465668 to #465667
-INFO - 1494367869: (..\BlockchainScanner.cpp:52) no history to scan
-INFO - 1494367869: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO - 1494367869: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.009s
-INFO - 1494367869: (..\DatabaseBuilder.cpp:160) init db in 6.281s
-INFO - 1494367869: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-WARN - 1494367875: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN - 1494367875: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN - 1494367875: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads
-WARN - 1494367875: (..\BDM_supportClasses.cpp:1891) running 35 zc parser threads
successful start and shutdown after previous mentioned problem:
Code:
Log file opened at 1494368069: C:\Users\jeff\AppData\Roaming\Armory\dbLog.txt
-INFO - 1494368069: (..\main.cpp:23) Running on 4 threads
-INFO - 1494368069: (..\main.cpp:24) Ram usage level: 4
-INFO - 1494368069: (..\BlockUtils.cpp:907) blkfile dir: C:\Users\jeff\AppData\Roaming\Bitcoin\blocks
-INFO - 1494368069: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\jeff\AppData\Roaming\Armory\databases
-INFO - 1494368069: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1494368070: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO - 1494368071: (..\BDM_Server.cpp:996) registered bdv: eb311f97a355b2f2dd5a
-INFO - 1494368072: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO - 1494368073: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 1494368076: (..\DatabaseBuilder.cpp:208) Found 465669 headers in db
-INFO - 1494368079: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1494368079: (..\DatabaseBuilder.cpp:477) Found next block after skipping 508317bytes
-INFO - 1494368079: (..\DatabaseBuilder.cpp:268) parsed block file #862
-DEBUG - 1494368079: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1494368079: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.726s
-INFO - 1494368079: (..\DatabaseBuilder.cpp:106) scanning new blocks from #465668 to #465667
-INFO - 1494368079: (..\BlockchainScanner.cpp:52) no history to scan
-INFO - 1494368079: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO - 1494368079: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.015s
-INFO - 1494368079: (..\DatabaseBuilder.cpp:160) init db in 7.121s
-INFO - 1494368079: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-WARN - 1494368102: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-WARN - 1494368102: (..\BDM_supportClasses.cpp:1891) running 15 zc parser threads
-WARN - 1494368102: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN - 1494368102: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN - 1494368109: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads
-WARN - 1494368109: (..\BDM_supportClasses.cpp:1891) running 35 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 40 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 45 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 50 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 55 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 60 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 65 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 70 zc parser threads
-INFO - 1494368200: (..\BDM_Server.cpp:1025) unregistered bdv: eb311f97a355b2f2dd5a
-INFO - 1494368200: (..\BDM_Server.cpp:936) proceeding to shutdown
-ERROR - 1494368200: (..\BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: POLLNVAL in readFromSocketThread
-INFO - 1494368200: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node
-ERROR - 1494368202: (..\BDM_mainthread.cpp:286) caught exception in main thread: terminate
-INFO - 1494368069: (..\main.cpp:23) Running on 4 threads
-INFO - 1494368069: (..\main.cpp:24) Ram usage level: 4
-INFO - 1494368069: (..\BlockUtils.cpp:907) blkfile dir: C:\Users\jeff\AppData\Roaming\Bitcoin\blocks
-INFO - 1494368069: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\jeff\AppData\Roaming\Armory\databases
-INFO - 1494368069: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1494368070: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO - 1494368071: (..\BDM_Server.cpp:996) registered bdv: eb311f97a355b2f2dd5a
-INFO - 1494368072: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO - 1494368073: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 1494368076: (..\DatabaseBuilder.cpp:208) Found 465669 headers in db
-INFO - 1494368079: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1494368079: (..\DatabaseBuilder.cpp:477) Found next block after skipping 508317bytes
-INFO - 1494368079: (..\DatabaseBuilder.cpp:268) parsed block file #862
-DEBUG - 1494368079: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1494368079: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.726s
-INFO - 1494368079: (..\DatabaseBuilder.cpp:106) scanning new blocks from #465668 to #465667
-INFO - 1494368079: (..\BlockchainScanner.cpp:52) no history to scan
-INFO - 1494368079: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO - 1494368079: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.015s
-INFO - 1494368079: (..\DatabaseBuilder.cpp:160) init db in 7.121s
-INFO - 1494368079: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-WARN - 1494368102: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-WARN - 1494368102: (..\BDM_supportClasses.cpp:1891) running 15 zc parser threads
-WARN - 1494368102: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN - 1494368102: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN - 1494368109: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads
-WARN - 1494368109: (..\BDM_supportClasses.cpp:1891) running 35 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 40 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 45 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 50 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 55 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 60 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 65 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 70 zc parser threads
-INFO - 1494368200: (..\BDM_Server.cpp:1025) unregistered bdv: eb311f97a355b2f2dd5a
-INFO - 1494368200: (..\BDM_Server.cpp:936) proceeding to shutdown
-ERROR - 1494368200: (..\BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: POLLNVAL in readFromSocketThread
-INFO - 1494368200: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node
-ERROR - 1494368202: (..\BDM_mainthread.cpp:286) caught exception in main thread: terminate
Will look into it.
I just upgraded Bitcoin Core and Armory. Here are the notes I made of my first experiences after the upgrade.
Windows 7 64bit
Updated Bitcoin Core from 0.14.0 to 0.14.1
Updated Armory from 0.95.1 to 0.96
Armory crashed every time after scanning.
Emptied %appdata%\Armory\databases , causing Armory to rebuild the database solved this problem.
btw: Amazing that this is the only piece of software that manages to fully use my 16 GB RAM while rebuilding the database. No problem for me.
Errormesage from tray-icon after starting Armory about the connection being lost to BitcoinCore while that is not really so.
I am running BitcoinCore continuously in the background, regardless of Armory running or not.
The CMD-window is still always visible.
Problem: Saving/Backing up a wallet unencrypted to a file does not work. "Save to File"
I want to use it to backup the private keys to another encrypted medium. CTRL-C and -V would work, but that is annoying after a while.
Compressed keys:
MultiBit Classis private keys are not accepted at Private Key Import: No valid private key data was entered.
https://bitcointalksearch.org/topic/m.14100768
Wallet properties: Used addresses:
Addresses not visible. Unsure after which this happens.
Solved after restarting Armory.
Address Book: changed Comment, but it does not stick.
Or on the other hand: The comment for an address changed in the wallet does not display in the addressbook.
After doing one transaction, and restarting Armory:
Does not fully start.
Solved by restarting BitcoinCore before starting Armory.
dblog.txt:
successful start and shutdown after previous mentioned problem:
Windows 7 64bit
Updated Bitcoin Core from 0.14.0 to 0.14.1
Updated Armory from 0.95.1 to 0.96
Armory crashed every time after scanning.
Emptied %appdata%\Armory\databases , causing Armory to rebuild the database solved this problem.
btw: Amazing that this is the only piece of software that manages to fully use my 16 GB RAM while rebuilding the database. No problem for me.
Errormesage from tray-icon after starting Armory about the connection being lost to BitcoinCore while that is not really so.
I am running BitcoinCore continuously in the background, regardless of Armory running or not.
The CMD-window is still always visible.
Problem: Saving/Backing up a wallet unencrypted to a file does not work. "Save to File"
I want to use it to backup the private keys to another encrypted medium. CTRL-C and -V would work, but that is annoying after a while.
Compressed keys:
MultiBit Classis private keys are not accepted at Private Key Import: No valid private key data was entered.
https://bitcointalksearch.org/topic/m.14100768
Wallet properties: Used addresses:
Addresses not visible. Unsure after which this happens.
Solved after restarting Armory.
Address Book: changed Comment, but it does not stick.
Or on the other hand: The comment for an address changed in the wallet does not display in the addressbook.
After doing one transaction, and restarting Armory:
Does not fully start.
Solved by restarting BitcoinCore before starting Armory.
dblog.txt:
Code:
Log file opened at 1494367860: C:\Users\jeff\AppData\Roaming\Armory\dbLog.txt
-INFO - 1494367860: (..\main.cpp:23) Running on 4 threads
-INFO - 1494367860: (..\main.cpp:24) Ram usage level: 4
-INFO - 1494367860: (..\BlockUtils.cpp:907) blkfile dir: C:\Users\jeff\AppData\Roaming\Bitcoin\blocks
-INFO - 1494367860: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\jeff\AppData\Roaming\Armory\databases
-INFO - 1494367860: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1494367860: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO - 1494367862: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO - 1494367863: (..\DatabaseBuilder.cpp:169) Reading headers from db
-WARN - 1494367865: (..\BDM_supportClasses.cpp:1891) running 0 zc parser threads
-WARN - 1494367865: (..\BDM_supportClasses.cpp:1891) running 5 zc parser threads
-WARN - 1494367865: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-INFO - 1494367866: (..\DatabaseBuilder.cpp:208) Found 465669 headers in db
-INFO - 1494367868: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1494367868: (..\DatabaseBuilder.cpp:477) Found next block after skipping 508317bytes
-INFO - 1494367869: (..\DatabaseBuilder.cpp:268) parsed block file #862
-DEBUG - 1494367869: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1494367869: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.491s
-INFO - 1494367869: (..\DatabaseBuilder.cpp:106) scanning new blocks from #465668 to #465667
-INFO - 1494367869: (..\BlockchainScanner.cpp:52) no history to scan
-INFO - 1494367869: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO - 1494367869: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.009s
-INFO - 1494367869: (..\DatabaseBuilder.cpp:160) init db in 6.281s
-INFO - 1494367869: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-WARN - 1494367875: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN - 1494367875: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN - 1494367875: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads
-WARN - 1494367875: (..\BDM_supportClasses.cpp:1891) running 35 zc parser threads
-INFO - 1494367860: (..\main.cpp:23) Running on 4 threads
-INFO - 1494367860: (..\main.cpp:24) Ram usage level: 4
-INFO - 1494367860: (..\BlockUtils.cpp:907) blkfile dir: C:\Users\jeff\AppData\Roaming\Bitcoin\blocks
-INFO - 1494367860: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\jeff\AppData\Roaming\Armory\databases
-INFO - 1494367860: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1494367860: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO - 1494367862: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO - 1494367863: (..\DatabaseBuilder.cpp:169) Reading headers from db
-WARN - 1494367865: (..\BDM_supportClasses.cpp:1891) running 0 zc parser threads
-WARN - 1494367865: (..\BDM_supportClasses.cpp:1891) running 5 zc parser threads
-WARN - 1494367865: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-INFO - 1494367866: (..\DatabaseBuilder.cpp:208) Found 465669 headers in db
-INFO - 1494367868: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1494367868: (..\DatabaseBuilder.cpp:477) Found next block after skipping 508317bytes
-INFO - 1494367869: (..\DatabaseBuilder.cpp:268) parsed block file #862
-DEBUG - 1494367869: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1494367869: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.491s
-INFO - 1494367869: (..\DatabaseBuilder.cpp:106) scanning new blocks from #465668 to #465667
-INFO - 1494367869: (..\BlockchainScanner.cpp:52) no history to scan
-INFO - 1494367869: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO - 1494367869: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.009s
-INFO - 1494367869: (..\DatabaseBuilder.cpp:160) init db in 6.281s
-INFO - 1494367869: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-WARN - 1494367875: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN - 1494367875: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN - 1494367875: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads
-WARN - 1494367875: (..\BDM_supportClasses.cpp:1891) running 35 zc parser threads
successful start and shutdown after previous mentioned problem:
Code:
Log file opened at 1494368069: C:\Users\jeff\AppData\Roaming\Armory\dbLog.txt
-INFO - 1494368069: (..\main.cpp:23) Running on 4 threads
-INFO - 1494368069: (..\main.cpp:24) Ram usage level: 4
-INFO - 1494368069: (..\BlockUtils.cpp:907) blkfile dir: C:\Users\jeff\AppData\Roaming\Bitcoin\blocks
-INFO - 1494368069: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\jeff\AppData\Roaming\Armory\databases
-INFO - 1494368069: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1494368070: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO - 1494368071: (..\BDM_Server.cpp:996) registered bdv: eb311f97a355b2f2dd5a
-INFO - 1494368072: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO - 1494368073: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 1494368076: (..\DatabaseBuilder.cpp:208) Found 465669 headers in db
-INFO - 1494368079: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1494368079: (..\DatabaseBuilder.cpp:477) Found next block after skipping 508317bytes
-INFO - 1494368079: (..\DatabaseBuilder.cpp:268) parsed block file #862
-DEBUG - 1494368079: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1494368079: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.726s
-INFO - 1494368079: (..\DatabaseBuilder.cpp:106) scanning new blocks from #465668 to #465667
-INFO - 1494368079: (..\BlockchainScanner.cpp:52) no history to scan
-INFO - 1494368079: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO - 1494368079: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.015s
-INFO - 1494368079: (..\DatabaseBuilder.cpp:160) init db in 7.121s
-INFO - 1494368079: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-WARN - 1494368102: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-WARN - 1494368102: (..\BDM_supportClasses.cpp:1891) running 15 zc parser threads
-WARN - 1494368102: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN - 1494368102: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN - 1494368109: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads
-WARN - 1494368109: (..\BDM_supportClasses.cpp:1891) running 35 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 40 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 45 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 50 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 55 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 60 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 65 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 70 zc parser threads
-INFO - 1494368200: (..\BDM_Server.cpp:1025) unregistered bdv: eb311f97a355b2f2dd5a
-INFO - 1494368200: (..\BDM_Server.cpp:936) proceeding to shutdown
-ERROR - 1494368200: (..\BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: POLLNVAL in readFromSocketThread
-INFO - 1494368200: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node
-ERROR - 1494368202: (..\BDM_mainthread.cpp:286) caught exception in main thread: terminate
-INFO - 1494368069: (..\main.cpp:23) Running on 4 threads
-INFO - 1494368069: (..\main.cpp:24) Ram usage level: 4
-INFO - 1494368069: (..\BlockUtils.cpp:907) blkfile dir: C:\Users\jeff\AppData\Roaming\Bitcoin\blocks
-INFO - 1494368069: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\jeff\AppData\Roaming\Armory\databases
-INFO - 1494368069: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1494368070: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO - 1494368071: (..\BDM_Server.cpp:996) registered bdv: eb311f97a355b2f2dd5a
-INFO - 1494368072: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO - 1494368073: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 1494368076: (..\DatabaseBuilder.cpp:208) Found 465669 headers in db
-INFO - 1494368079: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1494368079: (..\DatabaseBuilder.cpp:477) Found next block after skipping 508317bytes
-INFO - 1494368079: (..\DatabaseBuilder.cpp:268) parsed block file #862
-DEBUG - 1494368079: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1494368079: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.726s
-INFO - 1494368079: (..\DatabaseBuilder.cpp:106) scanning new blocks from #465668 to #465667
-INFO - 1494368079: (..\BlockchainScanner.cpp:52) no history to scan
-INFO - 1494368079: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO - 1494368079: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.015s
-INFO - 1494368079: (..\DatabaseBuilder.cpp:160) init db in 7.121s
-INFO - 1494368079: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-WARN - 1494368102: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-WARN - 1494368102: (..\BDM_supportClasses.cpp:1891) running 15 zc parser threads
-WARN - 1494368102: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN - 1494368102: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN - 1494368109: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads
-WARN - 1494368109: (..\BDM_supportClasses.cpp:1891) running 35 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 40 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 45 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 50 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 55 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 60 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 65 zc parser threads
-WARN - 1494368110: (..\BDM_supportClasses.cpp:1891) running 70 zc parser threads
-INFO - 1494368200: (..\BDM_Server.cpp:1025) unregistered bdv: eb311f97a355b2f2dd5a
-INFO - 1494368200: (..\BDM_Server.cpp:936) proceeding to shutdown
-ERROR - 1494368200: (..\BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: POLLNVAL in readFromSocketThread
-INFO - 1494368200: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node
-ERROR - 1494368202: (..\BDM_mainthread.cpp:286) caught exception in main thread: terminate
dbLog.txt too
logs
Log file opened at 1494352327: /home/debian/.armory/armorycpplog.txt
-INFO - 1494353307: (SocketObject.cpp:520) POLLIN recv return 0
Log file opened at 1494353394: /home/debian/.armory/armorycpplog.txt
-ERROR - 1494354120: (SocketObject.cpp:416) poll() error in readAndWrite: 4
logs
i keep getting stuck at Scanning Transaction History @1sec.
Debian VM with Core bitcoind 0.14.1
Debian VM with Core bitcoind 0.14.1
Hi Goatpig et al, thanks for all your hard work with this release.
I believe I'm experiencing the same problem as neosatus.
ArmoryQT.exe crashes after ArmoryDB.exe reports "unregistered bdv: etc..."
Hmm. I'm not sure what is wrong here. Try running Bitcoin Core manually then start Armory.I believe I'm experiencing the same problem as neosatus.
ArmoryQT.exe crashes after ArmoryDB.exe reports "unregistered bdv: etc..."
Can you use pruning in the new version of armory?
No.
Can you use pruning in the new version of armory?
Sure thing, thanks for the reply:
Cheers.
Code:
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1138 - C++ block utilities loaded successfully
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1255 -
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1256 -
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1257 -
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1258 - ************************************************************
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1259 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe --datadir=C:\Bitcoin DBs\Armory DB
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1260 - ************************************************************
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1261 - Loading Armory Engine:
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1262 - Armory Version : 0.96
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1263 - Armory Build: : a3d01aa722
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1264 - PyBtcWallet Version : 1.35
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1265 - Detected Operating system: Windows
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1266 - OS Variant : 7-6.1.7601-SP1-Multiprocessor Free
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1267 - User home-directory : C:\Users\xxx\AppData\Roaming
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1268 - Satoshi BTC directory : C:\Users\xxx\AppData\Roaming\Bitcoin\
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1269 - Armory home dir : C:\Bitcoin DBs\Armory DB
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1270 - Detected System Specs :
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1271 - Total Available RAM : 4.00 GB
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1272 - CPU ID string : Intel64 Family 6 Model 23 Stepping 10, GenuineIntel
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1273 - Number of CPU cores : 2 cores
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1274 - System is 64-bit : True
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1275 - Preferred Encoding : cp1252
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1276 - Machine Arch : amd64
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1277 - Available HDD (ARM) : 1104 GB
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1278 - Available HDD (BTC) : 1104 GB
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1279 -
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1280 - Network Name: Main Network
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1281 - Satoshi Port: 8333
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1282 - Do wlt check: True
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1283 - Named options/arguments to armoryengine.py:
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - thread_count : -1
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - rescan : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - ignoreAllZC : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - rescanBalance : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - disableModules : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - port : None
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - interport : 8223
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - coverageOutputDir: None
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - forceWalletCheck: False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - regtest : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - rebuild : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - nettimeout : 2
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - datadir : C:\Bitcoin DBs\Armory DB
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - clearMempool : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - offline : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - armoryDBDir : DEFAULT
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - armorydb_port : 9001
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - satoshiPort : DEFAULT
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - useTorSettings : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - netlog : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - keypool : 100
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - coverageInclude : None
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - forceOnline : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - redownload : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - rpcBindAddr : 127.0.0.1
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - armorydb_ip : 127.0.0.1
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - multisigFile : DEFAULT
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - ram_usage : -1
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - mtdebug : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - logDisable : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - settingsPath : C:\Bitcoin DBs\Armory DB\ArmorySettings.txt
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - language : en
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - db_type : DB_FULL
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - doDebug : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - enableDetSign : True
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - disableConfPermis: False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - testnet : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - rpcport : DEFAULT
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - satoshiHome : DEFAULT
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - satoshiRpcport : DEFAULT
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - logFile : C:\Bitcoin DBs\Armory DB\ArmoryQt.exe.log.txt
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - verbosity : None
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1286 - Other arguments:
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1289 - ************************************************************
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1692 - C++ block utilities loaded successfully
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:3590 - Using settings file: C:\Bitcoin DBs\Armory DB\ArmorySettings.txt
2017-05-09 13:19 (ERROR) -- ArmoryUtils.pyc:3747 - Unsupported language specified. Defaulting to English (en)
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:3750 - Using Language: en
2017-05-09 13:19 (INFO) -- BDM.pyc:368 - Using the asynchronous/multi-threaded BlockDataManager.
2017-05-09 13:19 (INFO) -- BDM.pyc:369 - Blockchain operations will happen in the background.
2017-05-09 13:19 (INFO) -- BDM.pyc:370 - Devs: check TheBDM.getState() before asking for data.
2017-05-09 13:19 (INFO) -- BDM.pyc:371 - Registering addresses during rescans will queue them for
2017-05-09 13:19 (INFO) -- BDM.pyc:372 - inclusion after the current scan is completed.
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:3590 - Using settings file: C:\Bitcoin DBs\Armory DB\ArmorySettings.txt
2017-05-09 13:19 (INFO) -- ArmoryQt.py:2042 - loadWalletsAndSettings
2017-05-09 13:19 (INFO) -- ArmoryQt.py:2102 - Loading wallets...
2017-05-09 13:19 (INFO) -- ArmoryQt.py:2167 - Number of wallets read in: 1
2017-05-09 13:19 (INFO) -- ArmoryQt.py:2172 - Wallet (xxx): "Primary Wallet " (Encrypted)
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1747 - acquiring process mutex...
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1385 - setupUriRegistration
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1453 - Armory already registered for current user. Done!
2017-05-09 13:19 (INFO) -- ArmoryQt.py:558 - Usermode: Advanced
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1681 - Changing usermode:
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1682 - From: Advanced
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1690 - To: Advanced
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1814 - startBitcoindIfNecessary
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1850 - setSatoshiPaths
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1868 - Setting satoshi datadir = C:\Bitcoin DBs\Bitcoin Core
2017-05-09 13:19 (INFO) -- SDM.pyc:251 - Found Bitcoin Core link on desktop: C:\Program Files (x86)\Armory
2017-05-09 13:19 (INFO) -- SDM.pyc:169 - Found bitcoind in the following places:
2017-05-09 13:19 (INFO) -- SDM.pyc:171 - C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-09 13:19 (INFO) -- SDM.pyc:171 - C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-09 13:19 (INFO) -- SDM.pyc:173 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-09 13:19 (INFO) -- SDM.pyc:337 - Called startBitcoind
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: [u'C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=C:\\Bitcoin DBs\\Bitcoin Core']
2017-05-09 13:19 (INFO) -- SDM.pyc:443 - PID of bitcoind: 3152
2017-05-09 13:19 (INFO) -- SDM.pyc:444 - PID of armory: 4488
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: ['.\\guardian.exe', '4488', '3152']
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1850 - setSatoshiPaths
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1868 - Setting satoshi datadir = C:\Bitcoin DBs\Bitcoin Core
2017-05-09 13:19 (WARNING) -- SDM.pyc:396 - Spawning DB with command:./ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="C:\Bitcoin DBs\Bitcoin Core\blocks" --datadir="C:\Bitcoin DBs\Armory DB" --dbdir="C:\Bitcoin DBs\Armory DB\databases"
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', u'--satoshi-datadir="C:\\Bitcoin DBs\\Bitcoin Core\\blocks"', u'--datadir="C:\\Bitcoin DBs\\Armory DB"', u'--dbdir="C:\\Bitcoin DBs\\Armory DB\\databases"']
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1882 - loadBlockchainIfNecessary
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (WARNING) -- ArmoryQt.py:4057 - Called updateSyncProgress while not sync'ing
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1255 -
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1256 -
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1257 -
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1258 - ************************************************************
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1259 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe --datadir=C:\Bitcoin DBs\Armory DB
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1260 - ************************************************************
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1261 - Loading Armory Engine:
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1262 - Armory Version : 0.96
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1263 - Armory Build: : a3d01aa722
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1264 - PyBtcWallet Version : 1.35
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1265 - Detected Operating system: Windows
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1266 - OS Variant : 7-6.1.7601-SP1-Multiprocessor Free
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1267 - User home-directory : C:\Users\xxx\AppData\Roaming
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1268 - Satoshi BTC directory : C:\Users\xxx\AppData\Roaming\Bitcoin\
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1269 - Armory home dir : C:\Bitcoin DBs\Armory DB
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1270 - Detected System Specs :
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1271 - Total Available RAM : 4.00 GB
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1272 - CPU ID string : Intel64 Family 6 Model 23 Stepping 10, GenuineIntel
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1273 - Number of CPU cores : 2 cores
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1274 - System is 64-bit : True
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1275 - Preferred Encoding : cp1252
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1276 - Machine Arch : amd64
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1277 - Available HDD (ARM) : 1104 GB
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1278 - Available HDD (BTC) : 1104 GB
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1279 -
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1280 - Network Name: Main Network
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1281 - Satoshi Port: 8333
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1282 - Do wlt check: True
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1283 - Named options/arguments to armoryengine.py:
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - thread_count : -1
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - rescan : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - ignoreAllZC : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - rescanBalance : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - disableModules : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - port : None
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - interport : 8223
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - coverageOutputDir: None
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - forceWalletCheck: False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - regtest : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - rebuild : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - nettimeout : 2
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - datadir : C:\Bitcoin DBs\Armory DB
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - clearMempool : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - offline : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - armoryDBDir : DEFAULT
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - armorydb_port : 9001
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - satoshiPort : DEFAULT
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - useTorSettings : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - netlog : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - keypool : 100
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - coverageInclude : None
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - forceOnline : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - redownload : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - rpcBindAddr : 127.0.0.1
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - armorydb_ip : 127.0.0.1
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - multisigFile : DEFAULT
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - ram_usage : -1
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - mtdebug : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - logDisable : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - settingsPath : C:\Bitcoin DBs\Armory DB\ArmorySettings.txt
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - language : en
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - db_type : DB_FULL
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - doDebug : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - enableDetSign : True
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - disableConfPermis: False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - testnet : False
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - rpcport : DEFAULT
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - satoshiHome : DEFAULT
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - satoshiRpcport : DEFAULT
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - logFile : C:\Bitcoin DBs\Armory DB\ArmoryQt.exe.log.txt
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1285 - verbosity : None
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1286 - Other arguments:
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1289 - ************************************************************
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:1692 - C++ block utilities loaded successfully
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:3590 - Using settings file: C:\Bitcoin DBs\Armory DB\ArmorySettings.txt
2017-05-09 13:19 (ERROR) -- ArmoryUtils.pyc:3747 - Unsupported language specified. Defaulting to English (en)
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:3750 - Using Language: en
2017-05-09 13:19 (INFO) -- BDM.pyc:368 - Using the asynchronous/multi-threaded BlockDataManager.
2017-05-09 13:19 (INFO) -- BDM.pyc:369 - Blockchain operations will happen in the background.
2017-05-09 13:19 (INFO) -- BDM.pyc:370 - Devs: check TheBDM.getState() before asking for data.
2017-05-09 13:19 (INFO) -- BDM.pyc:371 - Registering addresses during rescans will queue them for
2017-05-09 13:19 (INFO) -- BDM.pyc:372 - inclusion after the current scan is completed.
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:3590 - Using settings file: C:\Bitcoin DBs\Armory DB\ArmorySettings.txt
2017-05-09 13:19 (INFO) -- ArmoryQt.py:2042 - loadWalletsAndSettings
2017-05-09 13:19 (INFO) -- ArmoryQt.py:2102 - Loading wallets...
2017-05-09 13:19 (INFO) -- ArmoryQt.py:2167 - Number of wallets read in: 1
2017-05-09 13:19 (INFO) -- ArmoryQt.py:2172 - Wallet (xxx): "Primary Wallet " (Encrypted)
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1747 - acquiring process mutex...
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1385 - setupUriRegistration
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1453 - Armory already registered for current user. Done!
2017-05-09 13:19 (INFO) -- ArmoryQt.py:558 - Usermode: Advanced
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1681 - Changing usermode:
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1682 - From: Advanced
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1690 - To: Advanced
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1814 - startBitcoindIfNecessary
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1850 - setSatoshiPaths
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1868 - Setting satoshi datadir = C:\Bitcoin DBs\Bitcoin Core
2017-05-09 13:19 (INFO) -- SDM.pyc:251 - Found Bitcoin Core link on desktop: C:\Program Files (x86)\Armory
2017-05-09 13:19 (INFO) -- SDM.pyc:169 - Found bitcoind in the following places:
2017-05-09 13:19 (INFO) -- SDM.pyc:171 - C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-09 13:19 (INFO) -- SDM.pyc:171 - C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-09 13:19 (INFO) -- SDM.pyc:173 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-05-09 13:19 (INFO) -- SDM.pyc:337 - Called startBitcoind
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: [u'C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=C:\\Bitcoin DBs\\Bitcoin Core']
2017-05-09 13:19 (INFO) -- SDM.pyc:443 - PID of bitcoind: 3152
2017-05-09 13:19 (INFO) -- SDM.pyc:444 - PID of armory: 4488
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: ['.\\guardian.exe', '4488', '3152']
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1850 - setSatoshiPaths
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1868 - Setting satoshi datadir = C:\Bitcoin DBs\Bitcoin Core
2017-05-09 13:19 (WARNING) -- SDM.pyc:396 - Spawning DB with command:./ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="C:\Bitcoin DBs\Bitcoin Core\blocks" --datadir="C:\Bitcoin DBs\Armory DB" --dbdir="C:\Bitcoin DBs\Armory DB\databases"
2017-05-09 13:19 (INFO) -- ArmoryUtils.pyc:665 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', u'--satoshi-datadir="C:\\Bitcoin DBs\\Bitcoin Core\\blocks"', u'--datadir="C:\\Bitcoin DBs\\Armory DB"', u'--dbdir="C:\\Bitcoin DBs\\Armory DB\\databases"']
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1882 - loadBlockchainIfNecessary
2017-05-09 13:19 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (WARNING) -- ArmoryQt.py:4057 - Called updateSyncProgress while not sync'ing
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2017-05-09 13:19 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
Cheers.
Can you also post the armorylog.txt?
Hi Goatpig et al, thanks for all your hard work with this release.
I believe I'm experiencing the same problem as neosatus.
ArmoryQT.exe crashes after ArmoryDB.exe reports "unregistered bdv: etc..."
I have updated both Armory and Core (14.1).
Here's the dbLog for the latest crash, ArmoryDB.exe appears to continue to run.
armorylog has this entry at the time of the crash:
(WARNING) -- ArmoryQt.py:4057 - Called updateSyncProgress while not sync'ing
Thanks for any assistance.
Cheers.
I believe I'm experiencing the same problem as neosatus.
ArmoryQT.exe crashes after ArmoryDB.exe reports "unregistered bdv: etc..."
I have updated both Armory and Core (14.1).
Here's the dbLog for the latest crash, ArmoryDB.exe appears to continue to run.
Code:
Log file opened at 1494297575: C:\Bitcoin DBs\Armory DB/dbLog.txt
-INFO - 1494297575: (..\main.cpp:23) Running on 2 threads
-INFO - 1494297575: (..\main.cpp:24) Ram usage level: 4
-INFO - 1494297575: (..\BlockUtils.cpp:907) blkfile dir: C:\Bitcoin DBs\Bitcoin Core\blocks
-INFO - 1494297575: (..\BlockUtils.cpp:908) lmdb dir: C:\Bitcoin DBs\Armory DB\databases
-INFO - 1494297575: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1494297576: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO - 1494297577: (..\BDM_Server.cpp:996) registered bdv: 7471bf47422af7fc355a
-INFO - 1494297593: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 1494297596: (..\DatabaseBuilder.cpp:208) Found 465842 headers in db
-INFO - 1494297601: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1494297602: (..\DatabaseBuilder.cpp:477) Found next block after skipping 508411bytes
-INFO - 1494297602: (..\DatabaseBuilder.cpp:268) parsed block file #863
-DEBUG - 1494297602: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1494297602: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.968s
-INFO - 1494297602: (..\DatabaseBuilder.cpp:106) scanning new blocks from #465454 to #465453
-INFO - 1494297602: (..\BlockchainScanner.cpp:52) no history to scan
-INFO - 1494297602: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO - 1494297602: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.019s
-INFO - 1494297602: (..\DatabaseBuilder.cpp:160) init db in 26.789s
-INFO - 1494297602: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-INFO - 1494297604: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-WARN - 1494297636: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-WARN - 1494297641: (..\BDM_supportClasses.cpp:1891) running 15 zc parser threads
-WARN - 1494297641: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN - 1494297641: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN - 1494297641: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads
-WARN - 1494297685: (..\BDM_supportClasses.cpp:1891) running 35 zc parser threads
-WARN - 1494297687: (..\BDM_supportClasses.cpp:1891) running 40 zc parser threads
-WARN - 1494297715: (..\BDM_supportClasses.cpp:1891) running 45 zc parser threads
-WARN - 1494297715: (..\BDM_supportClasses.cpp:1891) running 50 zc parser threads
-ERROR - 1494298924: (..\BitcoinP2P.cpp:1037) caught StopBlockingLoop in processDataStackThread
-INFO - 1494298924: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node
-INFO - 1494298926: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-WARN - 1494298991: (..\BDM_supportClasses.cpp:1891) running 55 zc parser threads
-WARN - 1494298991: (..\BDM_supportClasses.cpp:1891) running 60 zc parser threads
-WARN - 1494298991: (..\BDM_supportClasses.cpp:1891) running 65 zc parser threads
-WARN - 1494298991: (..\BDM_supportClasses.cpp:1891) running 70 zc parser threads
-INFO - 1494299046: (..\BDM_Server.cpp:1025) unregistered bdv: 7471bf47422af7fc355a
-WARN - 1494299176: (..\BDM_supportClasses.cpp:1891) running 75 zc parser threads
-WARN - 1494299176: (..\BDM_supportClasses.cpp:1891) running 80 zc parser threads
-WARN - 1494299176: (..\BDM_supportClasses.cpp:1891) running 85 zc parser threads
-WARN - 1494299176: (..\BDM_supportClasses.cpp:1891) running 90 zc parser threads
-WARN - 1494299176: (..\BDM_supportClasses.cpp:1891) running 95 zc parser threads
-WARN - 1494299176: (..\BDM_supportClasses.cpp:1891) running 100 zc parser threads
-WARN - 1494299176: (..\BDM_supportClasses.cpp:1891) running 105 zc parser threads
-WARN - 1494299263: (..\BDM_supportClasses.cpp:1891) running 110 zc parser threads
-WARN - 1494299263: (..\BDM_supportClasses.cpp:1891) running 115 zc parser threads
-WARN - 1494299263: (..\BDM_supportClasses.cpp:1891) running 120 zc parser threads
-WARN - 1494299263: (..\BDM_supportClasses.cpp:1891) running 125 zc parser threads
-WARN - 1494299263: (..\BDM_supportClasses.cpp:1891) running 130 zc parser threads
-WARN - 1494299263: (..\BDM_supportClasses.cpp:1891) running 135 zc parser threads
-WARN - 1494299263: (..\BDM_supportClasses.cpp:1891) running 140 zc parser threads
-INFO - 1494297575: (..\main.cpp:23) Running on 2 threads
-INFO - 1494297575: (..\main.cpp:24) Ram usage level: 4
-INFO - 1494297575: (..\BlockUtils.cpp:907) blkfile dir: C:\Bitcoin DBs\Bitcoin Core\blocks
-INFO - 1494297575: (..\BlockUtils.cpp:908) lmdb dir: C:\Bitcoin DBs\Armory DB\databases
-INFO - 1494297575: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1494297576: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO - 1494297577: (..\BDM_Server.cpp:996) registered bdv: 7471bf47422af7fc355a
-INFO - 1494297593: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 1494297596: (..\DatabaseBuilder.cpp:208) Found 465842 headers in db
-INFO - 1494297601: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1494297602: (..\DatabaseBuilder.cpp:477) Found next block after skipping 508411bytes
-INFO - 1494297602: (..\DatabaseBuilder.cpp:268) parsed block file #863
-DEBUG - 1494297602: (..\Blockchain.cpp:242) Organizing chain
-INFO - 1494297602: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 0.968s
-INFO - 1494297602: (..\DatabaseBuilder.cpp:106) scanning new blocks from #465454 to #465453
-INFO - 1494297602: (..\BlockchainScanner.cpp:52) no history to scan
-INFO - 1494297602: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO - 1494297602: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.019s
-INFO - 1494297602: (..\DatabaseBuilder.cpp:160) init db in 26.789s
-INFO - 1494297602: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-INFO - 1494297604: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-WARN - 1494297636: (..\BDM_supportClasses.cpp:1891) running 10 zc parser threads
-WARN - 1494297641: (..\BDM_supportClasses.cpp:1891) running 15 zc parser threads
-WARN - 1494297641: (..\BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN - 1494297641: (..\BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN - 1494297641: (..\BDM_supportClasses.cpp:1891) running 30 zc parser threads
-WARN - 1494297685: (..\BDM_supportClasses.cpp:1891) running 35 zc parser threads
-WARN - 1494297687: (..\BDM_supportClasses.cpp:1891) running 40 zc parser threads
-WARN - 1494297715: (..\BDM_supportClasses.cpp:1891) running 45 zc parser threads
-WARN - 1494297715: (..\BDM_supportClasses.cpp:1891) running 50 zc parser threads
-ERROR - 1494298924: (..\BitcoinP2P.cpp:1037) caught StopBlockingLoop in processDataStackThread
-INFO - 1494298924: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node
-INFO - 1494298926: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-WARN - 1494298991: (..\BDM_supportClasses.cpp:1891) running 55 zc parser threads
-WARN - 1494298991: (..\BDM_supportClasses.cpp:1891) running 60 zc parser threads
-WARN - 1494298991: (..\BDM_supportClasses.cpp:1891) running 65 zc parser threads
-WARN - 1494298991: (..\BDM_supportClasses.cpp:1891) running 70 zc parser threads
-INFO - 1494299046: (..\BDM_Server.cpp:1025) unregistered bdv: 7471bf47422af7fc355a
-WARN - 1494299176: (..\BDM_supportClasses.cpp:1891) running 75 zc parser threads
-WARN - 1494299176: (..\BDM_supportClasses.cpp:1891) running 80 zc parser threads
-WARN - 1494299176: (..\BDM_supportClasses.cpp:1891) running 85 zc parser threads
-WARN - 1494299176: (..\BDM_supportClasses.cpp:1891) running 90 zc parser threads
-WARN - 1494299176: (..\BDM_supportClasses.cpp:1891) running 95 zc parser threads
-WARN - 1494299176: (..\BDM_supportClasses.cpp:1891) running 100 zc parser threads
-WARN - 1494299176: (..\BDM_supportClasses.cpp:1891) running 105 zc parser threads
-WARN - 1494299263: (..\BDM_supportClasses.cpp:1891) running 110 zc parser threads
-WARN - 1494299263: (..\BDM_supportClasses.cpp:1891) running 115 zc parser threads
-WARN - 1494299263: (..\BDM_supportClasses.cpp:1891) running 120 zc parser threads
-WARN - 1494299263: (..\BDM_supportClasses.cpp:1891) running 125 zc parser threads
-WARN - 1494299263: (..\BDM_supportClasses.cpp:1891) running 130 zc parser threads
-WARN - 1494299263: (..\BDM_supportClasses.cpp:1891) running 135 zc parser threads
-WARN - 1494299263: (..\BDM_supportClasses.cpp:1891) running 140 zc parser threads
armorylog has this entry at the time of the crash:
(WARNING) -- ArmoryQt.py:4057 - Called updateSyncProgress while not sync'ing
Thanks for any assistance.
Cheers.
I would have to see a full log file, both armorylog and dbLog
What CPU are you using? The 5.4 version is built with a lot of x86 instructions that may not be available on your hardware.
Im using Intel Core i7 CPU 920.
Can you tell me what do you think the issue might be when the new version of armory is preventing wallets from being opened that were created with 95.1 like i described above? Is it a bug?
What CPU are you using? The 5.4 version is built with a lot of x86 instructions that may not be available on your hardware.
I also noticed something weird (which i dont know if this might be the cause): between the two gcc armory versions, the 4.7 one was the one that ive been trying to get to work with the wallet files (which means it opens up).
However when checking why armory_0.96-gcc5.4_amd64.deb wasnt opening at all. Everytime i tried opening it, i saw in syslog this error line:
traps: python2[29095] trap invalid opcode ip:7f5a01402ec0 sp:7ffeddbf0808 error:0 in _CppBlockUtils.so[7f5a00f4d000+6a9000]
And when i do gcc -v in terminal to see my version of gcc, it prints that i have the latest 5.4:
gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
However when checking why armory_0.96-gcc5.4_amd64.deb wasnt opening at all. Everytime i tried opening it, i saw in syslog this error line:
traps: python2[29095] trap invalid opcode ip:7f5a01402ec0 sp:7ffeddbf0808 error:0 in _CppBlockUtils.so[7f5a00f4d000+6a9000]
And when i do gcc -v in terminal to see my version of gcc, it prints that i have the latest 5.4:
gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
when i tried to import the wallet above, like i said previously i notice 2 extra files in the folder that are auto created as the crash happens:
armory_XXXX_wallet.lmdb-lock
armory_XXXX_wallet.lmdb
armory_XXXX_wallet.lmdb-lock
armory_XXXX_wallet.lmdb
These are watching only copies of the python wallet for the new code to run off of. You can delete these all you want, but 0.96 will recreate them on the fly if they are missing. Earlier versions don't use these files.
Ok, well i created a test wallet in 95.1 and upgraded to 96.0, i open armory with test wallet files inside folder already and it will create these watch only wallets but as soon as the GUI begins to start up, it crashes.
I especially tried this with offline armory, to import digital backup or even from paper backup and as soon as i import, it crashes, i open offline armory again and the wallet didnt import, yet its still in the folder.
I checked the armorylog.txt file and it says this before the crash:
2017-05-08 17:17 (INFO) -- ArmoryQt.py:2102 - Loading wallets...
2017-05-08 17:17 (INFO) -- ArmoryQt.py:2167 - Number of wallets read in: 1
2017-05-08 17:17 (INFO) -- ArmoryQt.py:2172 - Wallet (35Qpf31Yj): "Test " (Encrypted)
2017-05-08 17:17 (INFO) -- ArmoryQt.py:2177 - Loading Multisig Lockboxes
crashes just after that.
Im not sure why this is happening even with brand new wallets. The other thing is that i tried doing a test backup on both wallets and it crashes the gui on that too.
Jump to: