|
Title: Armory does not appear to be scanning chain Post by: steamboat on April 03, 2013, 04:15:39 PM To start, computer specs:
AMD b55 quad core 3.8 ghz 16g ram Win 7 64 pro I'm using qt .8.1 and armory .87.2. I was originally running qt .7 on a different computer. I installed qt .8.1 on this computer, xferred the data files and rescanned. Qt is now showing my correct wallet balance, as well as being up to date (green check mark in bottom right). I then installed Armory and opened in online mode, and it has been showing "offline while scanning the blockchain" for hours, with "Connected (0 blocks)" showing in the bottom right corner. I have restarted Armory, restarted the computer, run in administrator mode, and nothing seems to work. Has anyone else experienced this issue, or been able to successfully pair Armory with qt v .8.1? Title: Re: Armory does not appear to be scanning chain Post by: etotheipi on April 03, 2013, 04:16:47 PM To start, computer specs: AMD b55 quad core 3.8 ghz 16g ram Win 7 64 pro I'm using qt .8.1 and armory .87.2. I was originally running qt .7 on a different computer. I installed qt .8.1 on this computer, xferred the data files and rescanned. Qt is now showing my correct wallet balance, as well as being up to date (green check mark in bottom right). I then installed Armory and opened in online mode, and it has been showing "offline while scanning the blockchain" for hours, with "Connected (0 blocks)" showing in the bottom right corner. I have restarted Armory, restarted the computer, run in administrator mode, and nothing seems to work. Has anyone else experienced this issue, or been able to successfully pair Armory with qt v .8.1? It's definitely supposed to work. I'm using it right now, in both Windows and Linux. Can you please export a log file (from the File menu) and email it or PM it to me? Title: Re: Armory does not appear to be scanning chain Post by: steamboat on April 03, 2013, 04:35:39 PM Sent. Thank you for the fast response.
Title: Re: Armory does not appear to be scanning chain Post by: etotheipi on April 03, 2013, 04:43:35 PM Sent. Thank you for the fast response. Are you using any non-standard settings for bitcoin-qt? A bitcoin.conf file? It looks like Armory is having a tough time communicating with it... Title: Re: Armory does not appear to be scanning chain Post by: steamboat on April 03, 2013, 04:44:46 PM I have not changed any settings. Just copy/pasted the old directory into the new and ran qt with -rescan. I messaged you what may be causing the problem, though I do not know how to fix it.
Title: Re: Armory does not appear to be scanning chain Post by: etotheipi on April 03, 2013, 04:45:53 PM I have not changed any settings. Just copy/pasted the old directory into the new and ran qt with -rescan. I messaged you what may be causing the problem, though I do not know how to fix it. Try removing the blk*.dat in the base directory. Leave the blocks/ directory alone. Only delete blk*.dat and blkindex.dat in the base. Title: Re: Armory does not appear to be scanning chain Post by: steamboat on April 03, 2013, 04:54:28 PM Okay, shut down Armory, then QT. Deleted blk*.dat files from the base roaming directory. Restarted QT, all is well. Restarted Armory, got a hang for a few seconds, then appears to be continuing with the same. Log update shows:
2013-04-03 12:49 (INFO) -- ArmoryQt.py:3593 - Attempting to close the main window! 2013-04-03 12:49 (INFO) -- ArmoryQt.py:3675 - Resetting BlockDataMgr, freeing memory 2013-04-03 12:51 (INFO) -- armoryengine.pyc:562 - 2013-04-03 12:51 (INFO) -- armoryengine.pyc:563 - 2013-04-03 12:51 (INFO) -- armoryengine.pyc:564 - 2013-04-03 12:51 (INFO) -- armoryengine.pyc:565 - ************************************************************ 2013-04-03 12:51 (INFO) -- armoryengine.pyc:566 - Invoked: C:\Program Files (x86)\Armory\Armory Bitcoin Client\Armory.exe 2013-04-03 12:51 (INFO) -- armoryengine.pyc:567 - ************************************************************ 2013-04-03 12:51 (INFO) -- armoryengine.pyc:568 - Loading Armory Engine: 2013-04-03 12:51 (INFO) -- armoryengine.pyc:569 - Armory Version : 0.87.2 2013-04-03 12:51 (INFO) -- armoryengine.pyc:570 - PyBtcWallet Version : 1.35 2013-04-03 12:51 (INFO) -- armoryengine.pyc:571 - Detected Operating system: Windows 2013-04-03 12:51 (INFO) -- armoryengine.pyc:572 - User home-directory : C:\Users\*\AppData\Roaming 2013-04-03 12:51 (INFO) -- armoryengine.pyc:573 - Satoshi BTC directory : C:\Users\*\AppData\Roaming\Bitcoin\ 2013-04-03 12:51 (INFO) -- armoryengine.pyc:574 - Armory home dir : C:\Users\*\AppData\Roaming\Armory\ 2013-04-03 12:51 (INFO) -- armoryengine.pyc:575 - 2013-04-03 12:51 (INFO) -- armoryengine.pyc:576 - Network Name: Main Network 2013-04-03 12:51 (INFO) -- armoryengine.pyc:577 - Satoshi Port: 8333 2013-04-03 12:51 (INFO) -- armoryengine.pyc:578 - Named options/arguments to armoryengine.py: 2013-04-03 12:51 (INFO) -- armoryengine.pyc:580 - logFile : C:\Users\*\AppData\Roaming\Armory\Armory.exe.log.txt 2013-04-03 12:51 (INFO) -- armoryengine.pyc:580 - skipVerCheck : False 2013-04-03 12:51 (INFO) -- armoryengine.pyc:580 - satoshiPort : DEFAULT 2013-04-03 12:51 (INFO) -- armoryengine.pyc:580 - settingsPath : C:\Users\*\AppData\Roaming\Armory\ArmorySettings.txt 2013-04-03 12:51 (INFO) -- armoryengine.pyc:580 - nettimeout : 2 2013-04-03 12:51 (INFO) -- armoryengine.pyc:580 - doDebug : False 2013-04-03 12:51 (INFO) -- armoryengine.pyc:580 - testnet : False 2013-04-03 12:51 (INFO) -- armoryengine.pyc:580 - netlog : False 2013-04-03 12:51 (INFO) -- armoryengine.pyc:580 - keypool : 100 2013-04-03 12:51 (INFO) -- armoryengine.pyc:580 - datadir : DEFAULT 2013-04-03 12:51 (INFO) -- armoryengine.pyc:580 - rpcport : DEFAULT 2013-04-03 12:51 (INFO) -- armoryengine.pyc:580 - satoshiHome : DEFAULT 2013-04-03 12:51 (INFO) -- armoryengine.pyc:580 - forceOnline : False 2013-04-03 12:51 (INFO) -- armoryengine.pyc:580 - logDisable : False 2013-04-03 12:51 (INFO) -- armoryengine.pyc:580 - offline : False 2013-04-03 12:51 (INFO) -- armoryengine.pyc:580 - mtdebug : False 2013-04-03 12:51 (INFO) -- armoryengine.pyc:580 - interport : 8223 2013-04-03 12:51 (INFO) -- armoryengine.pyc:581 - Other arguments: 2013-04-03 12:51 (INFO) -- armoryengine.pyc:584 - ************************************************************ 2013-04-03 12:51 (INFO) -- armoryengine.pyc:736 - C++ block utilities loaded successfully 2013-04-03 12:51 (INFO) -- armoryengine.pyc:11517 - Using the asynchronous/multi-threaded BlockDataManager. 2013-04-03 12:51 (INFO) -- armoryengine.pyc:11518 - Blockchain operations will happen in the background. 2013-04-03 12:51 (INFO) -- armoryengine.pyc:11519 - Devs: check TheBDM.getBDMState() before asking for data. 2013-04-03 12:51 (INFO) -- armoryengine.pyc:11520 - Registering addresses during rescans will queue them for 2013-04-03 12:51 (INFO) -- armoryengine.pyc:11521 - including after the current scan is completed. 2013-04-03 12:51 (INFO) -- armoryengine.pyc:9724 - Using settings file: C:\Users\*\AppData\Roaming\Armory\ArmorySettings.txt 2013-04-03 12:51 (INFO) -- ArmoryQt.py:1417 - Loading wallets... 2013-04-03 12:51 (INFO) -- ArmoryQt.py:1465 - Number of wallets read in: 1 2013-04-03 12:51 (INFO) -- ArmoryQt.py:1470 - Wallet (********): "primary " (Encrypted) 2013-04-03 12:51 (INFO) -- ArmoryQt.py:1104 - Setting up networking... 2013-04-03 12:51 (INFO) -- ArmoryQt.py:1152 - Internet connection is Available: True 2013-04-03 12:51 (INFO) -- ArmoryQt.py:1153 - Bitcoin-Qt/bitcoind is Available: True 2013-04-03 12:51 (ERROR) -- ArmoryQt.py:651 - 3 attempts to load blockchain failed. Remove mempool.bin. 2013-04-03 12:51 (INFO) -- armoryengine.pyc:11462 - Reset Requested 2013-04-03 12:51 (INFO) -- armoryengine.pyc:11466 - Go online requested 2013-04-03 12:51 (INFO) -- ArmoryQt.py:3202 - Dashboard switched to "Scanning" mode 2013-04-03 12:51 (INFO) -- ArmoryQt.py:548 - Usermode: Advanced 2013-04-03 12:51 (INFO) -- ArmoryQt.py:966 - Changing usermode: 2013-04-03 12:51 (INFO) -- ArmoryQt.py:967 - From: Advanced 2013-04-03 12:51 (INFO) -- ArmoryQt.py:975 - To: Advanced 2013-04-03 12:51 (INFO) -- armoryengine.pyc:9391 - Connection initiated. Start handshake 2013-04-03 12:51 (INFO) -- ArmoryQt.py:3202 - Dashboard switched to "Scanning" mode 2013-04-03 12:51 (INFO) -- ArmoryQt.py:1084 - You are running the latest version! 2013-04-03 12:51 (INFO) -- armoryengine.pyc:9631 - Handshake finished, connection open! Appears to be hanging at loading the blockchain Title: Re: Armory does not appear to be scanning chain Post by: steamboat on April 03, 2013, 04:56:03 PM Do I need to change
2013-04-03 12:51 (INFO) -- armoryengine.pyc:573 - Satoshi BTC directory : C:\Users\*\AppData\Roaming\Bitcoin\ to 2013-04-03 12:51 (INFO) -- armoryengine.pyc:573 - Satoshi BTC directory : C:\Users\*\AppData\Roaming\Bitcoin\blocks\ ? Title: Re: Armory does not appear to be scanning chain Post by: etotheipi on April 03, 2013, 04:59:09 PM Do I need to change 2013-04-03 12:51 (INFO) -- armoryengine.pyc:573 - Satoshi BTC directory : C:\Users\*\AppData\Roaming\Bitcoin\ to 2013-04-03 12:51 (INFO) -- armoryengine.pyc:573 - Satoshi BTC directory : C:\Users\*\AppData\Roaming\Bitcoin\blocks\ ? No, that's fine. It will look in both the main directory and the blocks directory for those blk files. It will pick the ones with the latest timestamps. Though, the latest version has more debugging output. Can you try it? http://dl.dropbox.com/u/1139081/ArmoryTestingReleases/armory_0.87.9-testing_win64.msi It might help me figure it out. Title: Re: Armory does not appear to be scanning chain Post by: steamboat on April 03, 2013, 05:04:56 PM Sure. Do I need to uninstall the previous version or run the install over top of it?
Title: Re: Armory does not appear to be scanning chain Post by: etotheipi on April 03, 2013, 05:08:01 PM Sure. Do I need to uninstall the previous version or run the install over top of it? Nope. You can always install over the previous version. All wallets and settings will remain untouched. Title: Re: Armory does not appear to be scanning chain Post by: steamboat on April 03, 2013, 05:20:48 PM Whelp. Installed and now it won't load. Crashes immediately.
Problem Event Name: APPCRASH Application Name: Armory.exe Application Version: 0.0.0.0 Application Timestamp: 4918017b Fault Module Name: MSVCR90.dll Fault Module Version: 9.0.30729.4940 Fault Module Timestamp: 4ca2e32e Exception Code: c0000005 Exception Offset: 000000000001eb58 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional Information 1: 95d1 Additional Information 2: 95d1766db898ef8ee32e62bf8315c3fc Additional Information 3: eb9a Additional Information 4: eb9a4ba802ad3af552861bced4313be9 Title: Re: Armory does not appear to be scanning chain Post by: etotheipi on April 03, 2013, 05:35:21 PM Whelp. Installed and now it won't load. Crashes immediately. Problem Event Name: APPCRASH Application Name: Armory.exe Application Version: 0.0.0.0 Application Timestamp: 4918017b Fault Module Name: MSVCR90.dll Fault Module Version: 9.0.30729.4940 Fault Module Timestamp: 4ca2e32e Exception Code: c0000005 Exception Offset: 000000000001eb58 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional Information 1: 95d1 Additional Information 2: 95d1766db898ef8ee32e62bf8315c3fc Additional Information 3: eb9a Additional Information 4: eb9a4ba802ad3af552861bced4313be9 GAH! Can you try repairing the installation? Or completely remove c:\program files (x86)\Armory ? Then reinstall it? I assume you're in Win7-64? Title: Re: Armory does not appear to be scanning chain Post by: steamboat on April 03, 2013, 05:40:27 PM I am indeed. I'll try to repair, and if that doesn't work I'll wipe and do a fresh install. I haven't put any coinage on there yet so I don't care about any of the data.
Title: Re: Armory does not appear to be scanning chain Post by: steamboat on April 03, 2013, 05:53:37 PM Okay, progress!
Repair didn't work. Uninstalled old and installed the latest and it is 100% synchronized with network, and Scanning tx history, currently @ 11%. Log file looks like this 2013-04-03 13:13 (INFO) -- ArmoryQt.py:3593 - Attempting to close the main window! 2013-04-03 13:13 (INFO) -- ArmoryQt.py:3675 - Resetting BlockDataMgr, freeing memory 2013-04-03 13:46 (INFO) -- armoryengine.pyc:761 - 2013-04-03 13:46 (INFO) -- armoryengine.pyc:762 - 2013-04-03 13:46 (INFO) -- armoryengine.pyc:763 - 2013-04-03 13:46 (INFO) -- armoryengine.pyc:764 - ************************************************************ 2013-04-03 13:46 (INFO) -- armoryengine.pyc:765 - Invoked: C:\Program Files (x86)\Armory\Armory Bitcoin Client\Armory.exe 2013-04-03 13:46 (INFO) -- armoryengine.pyc:766 - ************************************************************ 2013-04-03 13:46 (INFO) -- armoryengine.pyc:767 - Loading Armory Engine: 2013-04-03 13:46 (INFO) -- armoryengine.pyc:768 - Armory Version : 0.87.92 2013-04-03 13:46 (INFO) -- armoryengine.pyc:769 - PyBtcWallet Version : 1.35 2013-04-03 13:46 (INFO) -- armoryengine.pyc:770 - Detected Operating system: Windows 2013-04-03 13:46 (INFO) -- armoryengine.pyc:771 - OS Variant : 7-6.1.7600--Multiprocessor Free 2013-04-03 13:46 (INFO) -- armoryengine.pyc:772 - User home-directory : C:\Users\*\AppData\Roaming 2013-04-03 13:46 (INFO) -- armoryengine.pyc:773 - Satoshi BTC directory : C:\Users\*\AppData\Roaming\Bitcoin\ 2013-04-03 13:46 (INFO) -- armoryengine.pyc:774 - First blk*.dat file : C:\Users\*\AppData\Roaming\Bitcoin\blocks\blk00000.dat 2013-04-03 13:46 (INFO) -- armoryengine.pyc:775 - Armory home dir : C:\Users\*\AppData\Roaming\Armory\ 2013-04-03 13:46 (INFO) -- armoryengine.pyc:776 - Detected System Specs : 2013-04-03 13:46 (INFO) -- armoryengine.pyc:777 - Total Available RAM : 16381.24 GB 2013-04-03 13:46 (INFO) -- armoryengine.pyc:778 - CPU ID string : AMD64 Family 16 Model 4 Stepping 3, AuthenticAMD 2013-04-03 13:46 (INFO) -- armoryengine.pyc:779 - Number of CPU cores : 3 cores 2013-04-03 13:46 (INFO) -- armoryengine.pyc:780 - System is 64-bit : True 2013-04-03 13:46 (INFO) -- armoryengine.pyc:781 - 2013-04-03 13:46 (INFO) -- armoryengine.pyc:782 - Network Name: Main Network 2013-04-03 13:46 (INFO) -- armoryengine.pyc:783 - Satoshi Port: 8333 2013-04-03 13:46 (INFO) -- armoryengine.pyc:784 - Named options/arguments to armoryengine.py: 2013-04-03 13:46 (INFO) -- armoryengine.pyc:786 - bitcoindPath : DEFAULT 2013-04-03 13:46 (INFO) -- armoryengine.pyc:786 - skipVerCheck : False 2013-04-03 13:46 (INFO) -- armoryengine.pyc:786 - satoshiPort : DEFAULT 2013-04-03 13:46 (INFO) -- armoryengine.pyc:786 - settingsPath : C:\Users\*\AppData\Roaming\Armory\ArmorySettings.txt 2013-04-03 13:46 (INFO) -- armoryengine.pyc:786 - logFile : C:\Users\*\AppData\Roaming\Armory\Armory.exe.log.txt 2013-04-03 13:46 (INFO) -- armoryengine.pyc:786 - nettimeout : 2 2013-04-03 13:46 (INFO) -- armoryengine.pyc:786 - doDebug : False 2013-04-03 13:46 (INFO) -- armoryengine.pyc:786 - datadir : DEFAULT 2013-04-03 13:46 (INFO) -- armoryengine.pyc:786 - netlog : False 2013-04-03 13:46 (INFO) -- armoryengine.pyc:786 - keypool : 100 2013-04-03 13:46 (INFO) -- armoryengine.pyc:786 - testnet : False 2013-04-03 13:46 (INFO) -- armoryengine.pyc:786 - rpcport : DEFAULT 2013-04-03 13:46 (INFO) -- armoryengine.pyc:786 - satoshiHome : DEFAULT 2013-04-03 13:46 (INFO) -- armoryengine.pyc:786 - forceOnline : False 2013-04-03 13:46 (INFO) -- armoryengine.pyc:786 - logDisable : False 2013-04-03 13:46 (INFO) -- armoryengine.pyc:786 - offline : False 2013-04-03 13:46 (INFO) -- armoryengine.pyc:786 - mtdebug : False 2013-04-03 13:46 (INFO) -- armoryengine.pyc:786 - interport : 8223 2013-04-03 13:46 (INFO) -- armoryengine.pyc:787 - Other arguments: 2013-04-03 13:46 (INFO) -- armoryengine.pyc:790 - ************************************************************ 2013-04-03 13:46 (INFO) -- armoryengine.pyc:952 - C++ block utilities loaded successfully 2013-04-03 13:46 (INFO) -- armoryengine.pyc:12677 - Using the asynchronous/multi-threaded BlockDataManager. 2013-04-03 13:46 (INFO) -- armoryengine.pyc:12678 - Blockchain operations will happen in the background. 2013-04-03 13:46 (INFO) -- armoryengine.pyc:12679 - Devs: check TheBDM.getBDMState() before asking for data. 2013-04-03 13:46 (INFO) -- armoryengine.pyc:12680 - Registering addresses during rescans will queue them for 2013-04-03 13:46 (INFO) -- armoryengine.pyc:12681 - inclusion after the current scan is completed. 2013-04-03 13:46 (INFO) -- armoryengine.pyc:10845 - Using settings file: C:\Users\*\AppData\Roaming\Armory\ArmorySettings.txt 2013-04-03 13:46 (INFO) -- ArmoryQt.py:1413 - loadWalletsAndSettings 2013-04-03 13:46 (INFO) -- ArmoryQt.py:1460 - Loading wallets... 2013-04-03 13:46 (INFO) -- ArmoryQt.py:1508 - Number of wallets read in: 1 2013-04-03 13:46 (INFO) -- ArmoryQt.py:1513 - Wallet (*****): "primary " (Encrypted) 2013-04-03 13:46 (INFO) -- ArmoryQt.py:1104 - Setting up networking... 2013-04-03 13:46 (INFO) -- ArmoryQt.py:1150 - Internet connection is Available: True 2013-04-03 13:46 (INFO) -- ArmoryQt.py:1151 - Bitcoin-Qt/bitcoind is Available: 8333 2013-04-03 13:46 (INFO) -- ArmoryQt.py:1158 - startBitcoindIfNecessary 2013-04-03 13:46 (WARNING) -- ArmoryQt.py:1168 - Tried to start bitcoind, but satoshi already running 2013-04-03 13:46 (INFO) -- ArmoryQt.py:3931 - Dashboard switched to auto-butSatoshiRunning 2013-04-03 13:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:Auto, State:OfflineBitcoindRunning 2013-04-03 13:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo 2013-04-03 13:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Offline" 2013-04-03 13:46 (INFO) -- ArmoryQt.py:530 - Usermode: Advanced 2013-04-03 13:46 (INFO) -- ArmoryQt.py:951 - Changing usermode: 2013-04-03 13:46 (INFO) -- ArmoryQt.py:952 - From: Advanced 2013-04-03 13:46 (INFO) -- ArmoryQt.py:960 - To: Advanced 2013-04-03 13:47 (INFO) -- armoryengine.pyc:10246 - Signature on signed data block is GOOD! 2013-04-03 13:47 (INFO) -- ArmoryQt.py:1087 - You are running the latest version! 2013-04-03 13:47 (INFO) -- ArmoryQt.py:1158 - startBitcoindIfNecessary 2013-04-03 13:47 (INFO) -- ArmoryQt.py:1188 - setSatoshiPaths 2013-04-03 13:47 (INFO) -- armoryengine.pyc:10331 - Found bitcoind in the following places: 2013-04-03 13:47 (INFO) -- armoryengine.pyc:10333 - C:\Program Files (x86)\Bitcoin\daemon\bitcoind.exe 2013-04-03 13:47 (INFO) -- armoryengine.pyc:10335 - Using: C:\Program Files (x86)\Bitcoin\daemon\bitcoind.exe 2013-04-03 13:47 (INFO) -- armoryengine.pyc:10461 - No bitcoin.conf available. Creating it... 2013-04-03 13:47 (INFO) -- armoryengine.pyc:10482 - icacls C:\Users\*\AppData\Roaming\Bitcoin\bitcoin.conf /inheritance:r /grant:r SNM:F 2013-04-03 13:47 (INFO) -- armoryengine.pyc:602 - Executing popen: icacls C:\Users\*\AppData\Roaming\Bitcoin\bitcoin.conf /inheritance:r /grant:r SNM:F 2013-04-03 13:47 (INFO) -- armoryengine.pyc:10484 - icacls returned: processed file: C:\Users\*\AppData\Roaming\Bitcoin\bitcoin.conf Successfully processed 1 files; Failed processing 0 files 2013-04-03 13:47 (INFO) -- armoryengine.pyc:10520 - Called startBitcoind 2013-04-03 13:47 (INFO) -- armoryengine.pyc:602 - Executing popen: ['C:\\Program Files (x86)\\Bitcoin\\daemon\\bitcoind.exe', '-datadir=C:\\Users\\*\\AppData\\Roaming\\Bitcoin\\'] 2013-04-03 13:47 (INFO) -- armoryengine.pyc:10541 - PID of bitcoind: 4696 2013-04-03 13:47 (INFO) -- armoryengine.pyc:10542 - PID of armory: 6448 2013-04-03 13:47 (INFO) -- armoryengine.pyc:602 - Executing popen: ['C:\\Program Files (x86)\\Armory\\Armory Bitcoin Client\\guardian.exe', '6448', '4696'] 2013-04-03 13:47 (INFO) -- armoryengine.pyc:10700 - Creating proxy in SDM: host=127.0.0.1, port=8332 2013-04-03 13:47 (INFO) -- ArmoryQt.py:4018 - Dashboard switched to auto-InitSync 2013-04-03 13:47 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:Auto, State:InitializingLongTime 2013-04-03 13:47 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:Auto, State:NewUserInfo 2013-04-03 13:47 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Offline" 2013-04-03 13:48 (INFO) -- ArmoryQt.py:4018 - Dashboard switched to auto-InitSync 2013-04-03 13:48 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:Auto, State:InitializingDoneSoon 2013-04-03 13:48 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Offline" 2013-04-03 13:48 (INFO) -- ArmoryQt.py:4242 - Starting load blockchain 2013-04-03 13:48 (INFO) -- ArmoryQt.py:1208 - loadBlockchainIfNecessary 2013-04-03 13:48 (ERROR) -- ArmoryQt.py:633 - 4 attempts to load blockchain failed. Remove mempool.bin. 2013-04-03 13:48 (ERROR) -- ArmoryQt.py:638 - File mempool.bin does not exist. Nothing deleted. 2013-04-03 13:48 (INFO) -- ArmoryQt.py:1254 - Setting netmode: 1 2013-04-03 13:48 (INFO) -- armoryengine.pyc:12618 - Reset Requested 2013-04-03 13:48 (INFO) -- armoryengine.pyc:12622 - Go online requested 2013-04-03 13:48 (INFO) -- armoryengine.pyc:9874 - Connection initiated. Start handshake 2013-04-03 13:48 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-03 13:48 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanWithWallets 2013-04-03 13:48 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-03 13:48 (INFO) -- armoryengine.pyc:9963 - Received version message from peer: 2013-04-03 13:48 (INFO) -- armoryengine.pyc:9964 - Version: 70001 2013-04-03 13:48 (INFO) -- armoryengine.pyc:9965 - SubVersion: /Satoshi:0.8.1/ 2013-04-03 13:48 (INFO) -- armoryengine.pyc:9966 - TimeStamp: 1365011300 2013-04-03 13:48 (INFO) -- armoryengine.pyc:9967 - StartHeight: 229519 2013-04-03 13:48 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open! 2013-04-03 13:50 (INFO) -- armoryengine.pyc:9998 - New block broadcast received Title: Re: Armory does not appear to be scanning chain Post by: drrussellshane on April 03, 2013, 07:09:29 PM Forgive me, I am new to Armory.
I have bitcoin-qt running and Armory is still saying "disconnected". I have restarted both and bitcoin-qt is updated with a green check, but Armory is still disconnected. Any ideas? Title: Re: Armory does not appear to be scanning chain Post by: etotheipi on April 03, 2013, 08:50:18 PM Forgive me, I am new to Armory. I have bitcoin-qt running and Armory is still saying "disconnected". I have restarted both and bitcoin-qt is updated with a green check, but Armory is still disconnected. Any ideas? The dashboard should tell you why it's disconnected. Are you using 0.87.2? Can you try the latest testing version (https://bitcointalk.org/index.php?topic=56424.msg1723770#msg1723770) and send me a log file if it still doesn't work? Title: Re: Armory does not appear to be scanning chain Post by: Deth on April 04, 2013, 10:26:27 PM Hi etotheipi! Strange thing just did happen. I tried to sent 1 btc from wallet and apply coin control functions. I could send it only with third try, Armory said that "Blockchain is not accepting transcation blah-blah" or something similar. After 3 tries, this window poped up again, but transaction finally get to the blockchain and it was visible in transactions filed of Armory. After ~30 min I opened Armory again (it was minimized): that transaction disappeared and balance show previous numbers like 1 btc was never sent. Restarting didn`t work...how can I do rescan in Armory so it will see this transaction? I use Arch Linux + bitcoind 0.8.1 + Tor + Armory 0.8.7.2-beta.
P.S. What is mempool.bin file? Deleting it changes nothing. Title: Re: Armory does not appear to be scanning chain Post by: etotheipi on April 04, 2013, 11:18:40 PM Hi etotheipi! Strange thing just did happen. I tried to sent 1 btc from wallet and apply coin control functions. I could send it only with third try, Armory said that "Blockchain is not accepting transcation blah-blah" or something similar. After 3 tries, this window poped up again, but transaction finally get to the blockchain and it was visible in transactions filed of Armory. After ~30 min I opened Armory again (it was minimized): that transaction disappeared and balance show previous numbers like 1 btc was never sent. Restarting didn`t work...how can I do rescan in Armory so it will see this transaction? I use Arch Linux + bitcoind 0.8.1 + Tor + Armory 0.8.7.2-beta. P.S. What is mempool.bin file? Deleting it changes nothing. Can you find the transaction on Blockchain.info or blockexplorer? Make sure it wasn't a double-spend. Transactions don't usually disappear from the ledger, unless a block came in with a conflicting transaction. Next, when it's online, can you see that the block-count in the bottom-right corner is the latest? Make sure the number matches the latest block on the network (latest seen on blockchain.info). If it's behind, that's why it's missing ... Armory doesn't have access to all the blocks for some reason... mempool just holds zero-confirmation transactions. If you delete it when there's a zero-confirmation transaction in your ledger, it will disappear on the next load. Title: Re: Armory does not appear to be scanning chain Post by: Deth on April 04, 2013, 11:36:40 PM Damn! Blockchain wasn`t completely downloaded :) I need some sleep. Sorry for bothering with dumb questions and thank you :)
Title: Re: Armory does not appear to be scanning chain Post by: etotheipi on April 04, 2013, 11:38:28 PM Damn! Blockchain wasn`t completely downloaded :) I need some sleep. Sorry for bothering with dumb questions and thank you :) No worries! The new version will actually avoid that... Armory won't go online until that download is complete. Help me test it! https://bitcointalk.org/index.php?topic=56424.msg1723770#msg1723770 Title: Re: Armory does not appear to be scanning chain Post by: Deth on April 04, 2013, 11:52:25 PM I`d like to, but I`m a little bit paranoid :) Can you sign package somehow, since git checkout from github is not done even with ssl. Maybe I`m wrong, I am not really good at compiling and programming stuff.
Title: Re: Armory does not appear to be scanning chain Post by: etotheipi on April 05, 2013, 01:35:04 AM I`d like to, but I`m a little bit paranoid :) Can you sign package somehow, since git checkout from github is not done even with ssl. Maybe I`m wrong, I am not really good at compiling and programming stuff. You bring up an interesting point. I have been "inconvenienced" by having to go to the offline computer for signing. But there's no reason I can't sign the intermediate commits with my personal, less-secure key that is on my online computer, and switch to the offline key for major releases... hmmm Let me see what I can do... Title: Re: Armory does not appear to be scanning chain Post by: etotheipi on April 05, 2013, 01:49:27 AM Do the following:
Code: git checkout managesatoshi That should spit out the log and show you the signature. My personal GPG key is 0xFB596985 (http://keyserver.ubuntu.com/pks/lookup?op=vindex&search=alan+reiner). Title: Re: Armory does not appear to be scanning chain Post by: Deth on April 05, 2013, 01:57:26 AM Hm...strange thing is happening-2. I start Armory, after scanning, it shows Connected (228672 blocks) at the bottom right corner. While 'bitcoind getinfo' telling '"blocks" : 229725'. WTF? :-\
Ok, I`ll try git thing it a bit later. Title: Re: Armory does not appear to be scanning chain Post by: etotheipi on April 05, 2013, 02:00:28 AM Hm...strange thing is happening-2. I start Armory, after scanning, it shows Connected (228672 blocks) at the bottom right corner. While 'bitcoind getinfo' telling '"blocks" : 229725'. WTF? :-\ Ok, I`ll try git thing it a bit later. That usually means Armory couldn't access the correct/updated block files. Frequently happens if you change your bitcoind --datadir=X, but don't start Armory with the --satoshi-datadir=X. Then Armory is talking to the current bitcoind, but using the old blockfiles. Title: Re: Armory does not appear to be scanning chain Post by: steamboat on April 05, 2013, 02:01:13 AM Update:
So after installing and running. Armory sync's 100% with the network, but scanning transaction history gets stuck at 99%. The bottom says Connected (0 blocks), and the logs is a bunch of stuff like this: 2013-04-04 20:16 (INFO) -- armoryengine.pyc:9963 - Received version message from peer: 2013-04-04 20:16 (INFO) -- armoryengine.pyc:9964 - Version: 70001 2013-04-04 20:16 (INFO) -- armoryengine.pyc:9965 - SubVersion: /Satoshi:0.8.1/ 2013-04-04 20:16 (INFO) -- armoryengine.pyc:9966 - TimeStamp: 1365121007 2013-04-04 20:16 (INFO) -- armoryengine.pyc:9967 - StartHeight: 229717 2013-04-04 20:16 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open! 2013-04-04 20:20 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 20:20 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 20:20 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 20:23 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 20:23 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 20:23 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 20:23 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:23 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:23 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:23 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:23 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:23 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:23 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 20:23 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 20:23 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 20:26 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 20:26 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 20:26 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 20:26 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:26 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:26 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:26 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:26 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:26 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:37 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:37 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:37 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:37 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:37 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:37 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:44 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:44 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:44 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:44 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:44 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:44 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:46 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:46 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:46 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:46 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:46 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:46 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:56 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:56 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:56 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:56 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:56 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:56 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:57 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:57 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:57 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:57 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:57 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 20:57 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 21:02 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:02 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:02 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 21:02 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:02 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:02 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 21:16 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 21:16 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 21:16 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 21:16 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 21:16 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 21:16 (INFO) -- armoryengine.pyc:9998 - New block broadcast received 2013-04-04 21:17 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:17 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:17 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 21:22 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:22 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:22 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 21:26 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:26 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:26 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 21:30 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:30 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:30 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 21:42 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:42 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:42 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 21:46 (ERROR) -- armoryengine.pyc:10134 - ***Connection to Satoshi client LOST! Attempting to reconnect... 2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 21:46 (INFO) -- ArmoryQt.py:1254 - Setting netmode: 1 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9874 - Connection initiated. Start handshake 2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9963 - Received version message from peer: 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9964 - Version: 70001 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9965 - SubVersion: /Satoshi:0.8.1/ 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9966 - TimeStamp: 1365126375 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9967 - StartHeight: 229725 2013-04-04 21:46 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open! 2013-04-04 21:46 (ERROR) -- armoryengine.pyc:10134 - ***Connection to Satoshi client LOST! Attempting to reconnect... 2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 21:46 (INFO) -- ArmoryQt.py:1254 - Setting netmode: 1 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9874 - Connection initiated. Start handshake 2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9874 - Connection initiated. Start handshake 2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9963 - Received version message from peer: 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9964 - Version: 70001 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9965 - SubVersion: /Satoshi:0.8.1/ 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9966 - TimeStamp: 1365126377 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9967 - StartHeight: 229725 2013-04-04 21:46 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open! 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9963 - Received version message from peer: 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9964 - Version: 70001 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9965 - SubVersion: /Satoshi:0.8.1/ 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9966 - TimeStamp: 1365126377 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9967 - StartHeight: 229725 2013-04-04 21:46 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open! 2013-04-04 21:46 (ERROR) -- armoryengine.pyc:10134 - ***Connection to Satoshi client LOST! Attempting to reconnect... 2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 21:46 (INFO) -- ArmoryQt.py:1254 - Setting netmode: 1 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9874 - Connection initiated. Start handshake 2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9963 - Received version message from peer: 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9964 - Version: 70001 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9965 - SubVersion: /Satoshi:0.8.1/ 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9966 - TimeStamp: 1365126378 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9967 - StartHeight: 229725 2013-04-04 21:46 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open! 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9874 - Connection initiated. Start handshake 2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9963 - Received version message from peer: 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9964 - Version: 70001 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9965 - SubVersion: /Satoshi:0.8.1/ 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9966 - TimeStamp: 1365126380 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9967 - StartHeight: 229725 2013-04-04 21:46 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open! 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9874 - Connection initiated. Start handshake 2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9963 - Received version message from peer: 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9964 - Version: 70001 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9965 - SubVersion: /Satoshi:0.8.1/ 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9966 - TimeStamp: 1365126385 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9967 - StartHeight: 229725 2013-04-04 21:46 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open! 2013-04-04 21:46 (ERROR) -- armoryengine.pyc:10134 - ***Connection to Satoshi client LOST! Attempting to reconnect... 2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 21:46 (INFO) -- ArmoryQt.py:1254 - Setting netmode: 1 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9874 - Connection initiated. Start handshake 2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 21:46 (ERROR) -- armoryengine.pyc:10134 - ***Connection to Satoshi client LOST! Attempting to reconnect... 2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9963 - Received version message from peer: 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9964 - Version: 70001 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9965 - SubVersion: /Satoshi:0.8.1/ 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9966 - TimeStamp: 1365126387 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9967 - StartHeight: 229725 2013-04-04 21:46 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open! 2013-04-04 21:46 (INFO) -- ArmoryQt.py:1254 - Setting netmode: 1 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9874 - Connection initiated. Start handshake 2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9963 - Received version message from peer: 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9964 - Version: 70001 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9965 - SubVersion: /Satoshi:0.8.1/ 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9966 - TimeStamp: 1365126387 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9967 - StartHeight: 229725 2013-04-04 21:46 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open! 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9874 - Connection initiated. Start handshake 2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9963 - Received version message from peer: 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9964 - Version: 70001 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9965 - SubVersion: /Satoshi:0.8.1/ 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9966 - TimeStamp: 1365126388 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9967 - StartHeight: 229725 2013-04-04 21:46 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open! 2013-04-04 21:46 (ERROR) -- armoryengine.pyc:10134 - ***Connection to Satoshi client LOST! Attempting to reconnect... 2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 21:46 (INFO) -- ArmoryQt.py:1254 - Setting netmode: 1 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9874 - Connection initiated. Start handshake 2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9963 - Received version message from peer: 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9964 - Version: 70001 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9965 - SubVersion: /Satoshi:0.8.1/ 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9966 - TimeStamp: 1365126408 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9967 - StartHeight: 229725 2013-04-04 21:46 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open! 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9874 - Connection initiated. Start handshake 2013-04-04 21:46 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:46 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9963 - Received version message from peer: 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9964 - Version: 70001 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9965 - SubVersion: /Satoshi:0.8.1/ 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9966 - TimeStamp: 1365126409 2013-04-04 21:46 (INFO) -- armoryengine.pyc:9967 - StartHeight: 229725 2013-04-04 21:46 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open! 2013-04-04 21:47 (INFO) -- armoryengine.pyc:9874 - Connection initiated. Start handshake 2013-04-04 21:47 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:47 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:47 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 21:47 (INFO) -- armoryengine.pyc:9963 - Received version message from peer: 2013-04-04 21:47 (INFO) -- armoryengine.pyc:9964 - Version: 70001 2013-04-04 21:47 (INFO) -- armoryengine.pyc:9965 - SubVersion: /Satoshi:0.8.1/ 2013-04-04 21:47 (INFO) -- armoryengine.pyc:9966 - TimeStamp: 1365126477 2013-04-04 21:47 (INFO) -- armoryengine.pyc:9967 - StartHeight: 229725 2013-04-04 21:47 (INFO) -- armoryengine.pyc:10124 - Handshake finished, connection open! 2013-04-04 21:51 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:51 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:51 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" 2013-04-04 21:51 (INFO) -- ArmoryQt.py:4126 - Dashboard switched to "Scanning" mode 2013-04-04 21:51 (INFO) -- ArmoryQt.py:3506 - Switching Armory state text to Mgmt:User, State:ScanNoWallets 2013-04-04 21:51 (INFO) -- ArmoryQt.py:3448 - Switching Armory functional mode to "Scanning" Title: Re: Armory does not appear to be scanning chain Post by: etotheipi on April 05, 2013, 02:07:45 AM @steamboat
Can you PM me the full log file? I can't see the context I need from that snippet. It's obviously abnormal behavior, but I need more info. Title: Re: Armory does not appear to be scanning chain Post by: Deth on April 05, 2013, 03:52:30 AM Hm...strange thing is happening-2. I start Armory, after scanning, it shows Connected (228672 blocks) at the bottom right corner. While 'bitcoind getinfo' telling '"blocks" : 229725'. WTF? :-\ Ok, I`ll try git thing it a bit later. That usually means Armory couldn't access the correct/updated block files. Frequently happens if you change your bitcoind --datadir=X, but don't start Armory with the --satoshi-datadir=X. Then Armory is talking to the current bitcoind, but using the old blockfiles. Code: 2013-04-05 07:45 (ERROR) -- armoryengine.py:9641 - ***Connection to Satoshi client LOST! Attempting to reconnect... Title: Re: Armory does not appear to be scanning chain Post by: etotheipi on April 05, 2013, 04:33:56 AM Somehow Armory isn't reading past Block 229672. Can you do something for me. When you start Armory and it starts scanning, you'll see a bunch of lines like this: Code: Opening file 44: /home/alan/.bitcoin/blocks/blk00043.dat On my system, the last one is blk00052.dat. Can you check which is the last one listed there, and then check your /home/user/.bitcoin/blocks directory and make sure you have the same number. It's almost like it's not seeing the last blockfile... Title: Re: Armory does not appear to be scanning chain Post by: Deth on April 05, 2013, 04:49:55 AM Yes, my`n too. But here what I have then
Code: .../bitcoin/blocks/blk00051.dat is 134,217,728 bytes Title: Re: Armory does not appear to be scanning chain Post by: etotheipi on April 05, 2013, 04:27:00 PM Yes, my`n too. But here what I have then Code: .../bitcoin/blocks/blk00051.dat is 134,217,728 bytes It looks to me like a corrupted blockchain file. Most likely, block 229673 in your blockfiles is corrupt, and thus Armory doesn't see any blocks beyond that, because they all trace back to an orphan block. I don't know if you can just delete blk00052.dat and restart bitcoind and it will figure out what happened...? If you don't mind redownloading the blockchain, you may have nothing to lose... (just delete everything in the .bitcoin directory except wallet.dat and let bitcoind redownload everything. Armory will work after that, I promise :) Title: Re: Armory does not appear to be scanning chain Post by: Deth on April 05, 2013, 09:22:02 PM Quote I don't know if you can just delete blk00052.dat and restart bitcoind and it will figure out what happened...? I did that already when I said I reindex database. Now I deleted blk00052.dat and blk00051.dat, started bitcoin-qt, it told me to rebuild database, which I did. Bitcoin-qt now shows that it is completely synced...Armory thinks that it is only 228672 blocks :-\I`ll dig more, please give ideas if you have such, I really don`t want to redownload all blockchain... Title: Re: Armory does not appear to be scanning chain Post by: Deth on April 06, 2013, 02:11:21 PM Ok, I deleted all files except for blk00003.dat-blk00050.dat and compiled Armory from managesatoshi branch and after reindex, Armory now sees all transactions. But settings can`t be accessed. See here
https://bitcointalk.org/index.php?topic=56424.msg1756505#msg1756505 Title: Re: Armory does not appear to be scanning chain Post by: Spekulatius on April 06, 2013, 04:05:10 PM I have similar issues as OP:
My system: Win 7 64bit 3 GB RAM (2,87 GB usable) Intel Pentium Dual CPU T3400 @ 2.16 GHz and 2.17 GHz Bitcoin v0.8.0-beta (Satoshi Client) Armory 0.87.2-beta Other: I store the blockchain files of my Satoshi Client in a non-standard directory using the "-datadir=D:\Programme\Bitcoin\Blockchain" command in the bitcoin-qt.exe shortcut. This way the "Target"-field in the shortcut's properties looks like this: "D:\Programme\Bitcoin\bitcoin-qt.exe -datadir=D:\Programme\Bitcoin\Blockchain" The "Execute in:"-field looks like this: "D:\Programme\Bitcoin" It works for the Satoshi Client but I guess my Armory client cant find the blockchain files on my hard drive and thus doesnt synch with the network. Im posting because I couldnt find any advice on how to tell it where to look, so Im stuck with "Connected (0 Blocks)". My story: I installed the Armory Offline Wallet on a separate Linux Laptop. Imported a priv key thats loaded with some 0.001 BTC. Made a watch-only copy and saved the wallet to USB stick. Then installed the Armory client on my other laptop (Windows 7) that also runs the Bitcoin Client and imported the watch-only wallet from the USB stick. Closed it down after the import worked alright and waited for the Bitcoin Client to synch with the blockchain. Rebooted Computer, then first started the Satoshi Client, waited for the green check mark, then started the Armory and waited for the correct balance to show in the Armory. It never showed up. It says in the dash board: "Armory is online!" but shows in the bottom right corner of the window: "Connected (0 Blocks)". It doesnt seem to synch with the blockchain. Then I sent another 0.01 BTC to the Address from the imported watch-only wallet and surprise! It showed up, hence with 0 confirmations. Now I rebooted and everything but the final balance is again displayed as 0.00 BTC. Blockchain.info shows 23 confirmations though. How can I get my online wallet to synch with the blockchain!? Thx Title: Re: Armory does not appear to be scanning chain Post by: etotheipi on April 06, 2013, 04:29:50 PM I have similar issues as OP: My system: Win 7 64bit 3 GB RAM (2,87 GB usable) Intel Pentium Dual CPU T3400 @ 2.16 GHz and 2.17 GHz Bitcoin v0.8.0-beta (Satoshi Client) Armory 0.87.2-beta Other: I store the blockchain files of my Satoshi Client in a non-standard directory using the "-datadir=D:\Programme\Bitcoin\Blockchain" command in the bitcoin-qt.exe shortcut. This way the "Target"-field in the shortcut's properties looks like this: "D:\Programme\Bitcoin\bitcoin-qt.exe -datadir=D:\Programme\Bitcoin\Blockchain" The "Execute in:"-field looks like this: "D:\Programme\Bitcoin" It works for the Satoshi Client but I guess my Armory client cant find the blockchain files on my hard drive and thus doesnt synch with the network. Im posting because I couldnt find any advice on how to tell it where to look, so Im stuck with "Connected (0 Blocks)". My story: I installed the Armory Offline Wallet on a separate Linux Laptop. Imported a priv key thats loaded with some 0.001 BTC. Made a watch-only copy and saved the wallet to USB stick. Then installed the Armory client on my other laptop (Windows 7) that also runs the Bitcoin Client and imported the watch-only wallet from the USB stick. Closed it down after the import worked alright and waited for the Bitcoin Client to synch with the blockchain. Rebooted Computer, then first started the Satoshi Client, waited for the green check mark, then started the Armory and waited for the correct balance to show in the Armory. It never showed up. It says in the dash board: "Armory is online!" but shows in the bottom right corner of the window: "Connected (0 Blocks)". It doesnt seem to synch with the blockchain. Then I sent another 0.01 BTC to the Address from the imported watch-only wallet and surprise! It showed up, hence with 0 confirmations. Now I rebooted and everything but the final balance is again displayed as 0.00 BTC. Blockchain.info shows 23 confirmations though. How can I get my online wallet to synch with the blockchain!? Thx Thanks for the detailed report. I appreciate it! You didn't mention starting Armory with "--satoshi-datadir=D:\Programme\Bitcoin\Blockchain". Have you done that? If not, that would explain it ... it's probably reading whatever super-old blockfiles you have in your C:\Users\username\AppData\Roaming\Bitcoin directory, which is why it went online but didn't show any transactions. The zero-confirmation tx showed up because Bitocin-Qt passed it on to Armory, which recognized it as being part of the wallet. But it stayed at zero conf, because Armory never saw it get into a block. Or it disappeared between restarts, because Armory can't seem to keep that data persistent between loads in Windows... Title: Re: Armory does not appear to be scanning chain Post by: Spekulatius on April 06, 2013, 05:06:46 PM Hi etotheipi,
Thx, It worked now! ;D Armory is online, connected (229988 Blocks) and shows the right balance. I was looking everywhere to find this bit of info (this forum, github, your bitcoinarmory.com, google,..) but didnt find anything (yes there is something in this thread but you really have to look closely on page XX to find it). I guess it would help a lot of users if you could provide documentation for your client that also states those commands, such as "--satoshi-datadir=" and similar, also giving step by step advice on how to correctly apply them. Thx for your quick response! Cheers, Spekulatius Title: Re: Armory does not appear to be scanning chain Post by: etotheipi on April 06, 2013, 07:47:02 PM Hi etotheipi, Thx, It worked now! ;D Armory is online, connected (229988 Blocks) and shows the right balance. I was looking everywhere to find this bit of info (this forum, github, your bitcoinarmory.com, google,..) but didnt find anything (yes there is something in this thread but you really have to look closely on page XX to find it). I guess it would help a lot of users if you could provide documentation for your client that also states those commands, such as "--satoshi-datadir=" and similar, also giving step by step advice on how to correctly apply them. Thx for your quick response! Cheers, Spekulatius Glad it worked! I actually do have someone helping me to create better documentation. The first thing will be an illustrated tutorial for offline transactions, with screenshots. Then we're going to try to add better general documentation. For now, if you're curious, you can run with --help to see a list of all the command line options. |