Bitcoin Forum
November 09, 2024, 10:49:10 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1] 2 »  All
  Print  
Author Topic: Restore Wallet - Merge, Overwrite Failure  (Read 579 times)
Craners (OP)
Newbie
*
Offline Offline

Activity: 12
Merit: 0


View Profile
March 19, 2017, 05:19:31 PM
 #1

Hi All,

I'm trying to restore an old wallet as I have forgotten the passphrase. (classic). Armory is online and all up to date.
I have my paper backup and I've verified it is working correctly by doing a test import.

However, after I type my root key in to restore the wallet I get the pop up saying I already have this wallet so I have the choice to Cancel / Merge / Overwrite. Neither Merge nor Overwrite buttons do anything when I click them, so I'm unable to import my wallet to change the passphrase.

Any ideas? I'm not sure what else to try.
I'm on Windows. Armory 0.95.1-beta.
achow101
Staff
Legendary
*
Offline Offline

Activity: 3542
Merit: 6886


Just writing some code


View Profile WWW
March 19, 2017, 05:23:23 PM
 #2

Go to the Armory datadir and find the wallet file for your wallet. It should be named in the pattern armory_id_.wallet. where id is the wallet id of the wallet you want to restore. Move that file out of that folder to a safe location. Then restart Armory and try importing again.

Can you also post your armorylog.txt file? (copy and paste the contents to a new paste on http://pastebin.com/ and post the link here)

Craners (OP)
Newbie
*
Offline Offline

Activity: 12
Merit: 0


View Profile
March 19, 2017, 07:23:57 PM
 #3

Thanks for the quick reply.

I removed my wallet, opened Armory and my wallet was successfully gone, but then Armory just got stuck loading and couldn't get online.

So I put my wallet file back where it was, and Armory got online fine straight away. I tried to import again but still the same issue.

I'm getting this repeating in the console:

Code:
-INFO  - 1489950311: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-INFO  - 1489950311: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
-ERROR - 1489950372: (..\BitcoinP2P.cpp:861) caught StopBlockingLoop in processDataStackThread
-INFO  - 1489950372: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-INFO  - 1489950372: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node
-ERROR - 1489950433: (..\BitcoinP2P.cpp:861) caught StopBlockingLoop in processDataStackThread
-INFO  - 1489950433: (..\BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-INFO  - 1489950433: (..\BitcoinP2P.cpp:783) Connected to Bitcoin node

My armorylog file is too big for pastebin so I've trimmed out a load of repeated backgroundRequestTopBlock sections from the start. There's a few removeWalletFromApplication sections at the end which might be helpful?
Here's the link - http://pastebin.com/8ANHWYXW
Craners (OP)
Newbie
*
Offline Offline

Activity: 12
Merit: 0


View Profile
March 21, 2017, 09:18:13 PM
Last edit: March 21, 2017, 09:41:22 PM by Craners
 #4

I tried a fresh install of Armory and got stuck even getting online. Armory is trying to synchronise with the network but the console is stuck in the "StopBlockingLoop in processDataStackThread" loop as above.

I checked my log and everything seems fine until Armory tries to go to "Scanning" mode.
Here's the snippet of the end of my log:
Code:
2017-03-21 20:21 (INFO) -- ArmoryQt.py:2217 - startBitcoindIfNecessary
2017-03-21 20:21 (INFO) -- ArmoryQt.py:2257 - setSatoshiPaths
2017-03-21 20:21 (INFO) -- ArmoryQt.py:2275 - Setting satoshi datadir = D:\Bitcoin
2017-03-21 20:21 (INFO) -- SDM.pyc:301 - Found Bitcoin-Core link on desktop: C:\Program Files
2017-03-21 20:21 (INFO) -- SDM.pyc:301 - Found Bitcoin-Core link on desktop: D:\
2017-03-21 20:21 (INFO) -- SDM.pyc:301 - Found Bitcoin-Core link on desktop: C:\Program Files\Bitcoin
2017-03-21 20:21 (INFO) -- SDM.pyc:182 - Found bitcoind in the following places:
2017-03-21 20:21 (INFO) -- SDM.pyc:184 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-03-21 20:21 (INFO) -- SDM.pyc:184 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-03-21 20:21 (INFO) -- SDM.pyc:184 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-03-21 20:21 (INFO) -- SDM.pyc:184 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-03-21 20:21 (INFO) -- SDM.pyc:186 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-03-21 20:21 (INFO) -- SDM.pyc:382 - Reading bitcoin.conf file
2017-03-21 20:21 (INFO) -- SDM.pyc:395 - Setting permissions on bitcoin.conf
2017-03-21 20:21 (INFO) -- SDM.pyc:404 - Setting permissions on bitcoin.conf
2017-03-21 20:21 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: [u'icacls', u'D:\\Bitcoin\\bitcoin.conf', u'/inheritance:r', u'/grant:r', u'Main:F']
2017-03-21 20:21 (INFO) -- SDM.pyc:410 - icacls returned:
2017-03-21 20:21 (INFO) -- SDM.pyc:460 - Called startBitcoind
2017-03-21 20:21 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: [u'C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=D:\\Bitcoin']
2017-03-21 20:21 (INFO) -- SDM.pyc:574 - PID of bitcoind: 1336
2017-03-21 20:21 (INFO) -- SDM.pyc:575 - PID of armory:   11144
2017-03-21 20:21 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: ['.\\guardian.exe', '11144', '1336']
2017-03-21 20:21 (INFO) -- SDM.pyc:756 - Creating proxy in SDM: host=127.0.0.1, port=8332
2017-03-21 20:21 (INFO) -- SDM.pyc:756 - Creating proxy in SDM: host=127.0.0.1, port=8332
2017-03-21 20:21 (INFO) -- ArmoryQt.py:5542 - Dashboard switched to auto-InitSync
2017-03-21 20:22 (INFO) -- ArmoryQt.py:2257 - setSatoshiPaths
2017-03-21 20:22 (INFO) -- ArmoryQt.py:2275 - Setting satoshi datadir = D:\Bitcoin
2017-03-21 20:22 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--spawnId="2os6m3fWVt4fCtDdT8FFjt7kQMBW7U4wEcvmvDT8awrV"', u'--satoshi-datadir="D:\\Bitcoin\\blocks"', u'--datadir="C:\\Users\\Main\\AppData\\Roaming\\Armory\\"', u'--dbdir="C:\\Users\\Main\\AppData\\Roaming\\Armory\\databases"']
2017-03-21 20:22 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 1
2017-03-21 20:22 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 0
2017-03-21 20:22 (INFO) -- ArmoryQt.py:2289 - loadBlockchainIfNecessary
2017-03-21 20:22 (INFO) -- ArmoryQt.py:5645 - Dashboard switched to "Scanning" mode

Interestingly - if I put my .wallet file into my Armory data folder and relaunch Armory, it will get online fine. However I still can't restore it as I have the same issue as I explained in the first post. The merge or overwrite buttons don't do anything.
The log for this is below. The final line appears to be an error but I have no idea what to do about it:
Code:
2017-03-21 21:36 (INFO) -- ArmoryQt.py:3260 - removeWalletFromApplication
2017-03-21 21:36 (ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 13908, in SaveMeta
  File "qtdialogs.pyc", line 13872, in Replace
  File "ArmoryQt.py", line 3268, in removeWalletFromApplication
  File "armoryengine\PyBtcWallet.pyc", line 288, in unregisterWallet
  File "armoryengine\BDM.pyc", line 116, in inner
  File "armoryengine\BDM.pyc", line 251, in unregisterWallet
  File "CppBlockUtils.pyc", line 2692, in <lambda>
  File "CppBlockUtils.pyc", line 74, in _swig_getattr
  File "CppBlockUtils.pyc", line 69, in _swig_getattr_nondynamic
AttributeError: type object 'object' has no attribute '__getattr__'

I'm now out of ideas. Any further help would be much appreciated.
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3752
Merit: 1364

Armory Developer


View Profile
March 21, 2017, 09:43:39 PM
 #5

If you know how to build the code, go ahead and run 0.96 off of the dev branch. Otherwise, wait for 0.96 testing binaries, coming soon (TM)

Craners (OP)
Newbie
*
Offline Offline

Activity: 12
Merit: 0


View Profile
December 04, 2017, 02:14:40 PM
 #6

Hi all,

Trying to pick this up again using 0.96.3 however I'm stuck at a different point this time.

I ran bitcoin qt and got that to the latest, then launched Armory. Armory connected fine and build the databases but has gotten stuck at "Scanning Transaction History". I got a countdown which went down from about 3 hours to 1 hour quite quickly, but then incremented up to 5 hours and has now been stuck like that for a couple hours and my computer has churned to a halt.

My log file says:

Code:
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1147 - C++ block utilities loaded successfully
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1264 -
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1265 -
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1266 -
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1267 - ************************************************************
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1268 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1269 - ************************************************************
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1270 - Loading Armory Engine:
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1271 -    Armory Version        : 0.96.3
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1272 -    Armory Build:         : 2b65ac0648
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1273 -    PyBtcWallet  Version  : 1.35
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1274 - Detected Operating system: Windows
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1275 -    OS Variant            : 8-6.2.9200--Multiprocessor Free
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1276 -    User home-directory   : C:\Users\Main\AppData\Roaming
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1277 -    Satoshi BTC directory : C:\Users\Main\AppData\Roaming\Bitcoin
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1278 -    Armory home dir       : C:\Users\Main\AppData\Roaming\Armory\
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1279 - Detected System Specs    :
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1280 -    Total Available RAM   : 7.87 GB
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1281 -    CPU ID string         : Intel64 Family 6 Model 58 Stepping 9, GenuineIntel
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1282 -    Number of CPU cores   : 8 cores
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1283 -    System is 64-bit      : True
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1284 -    Preferred Encoding    : cp1252
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1285 -    Machine Arch          : amd64
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1286 -    Available HDD (ARM)   : 111 GB
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1287 -    Available HDD (BTC)   : 111 GB
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1288 -
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1289 - Network Name: Main Network
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1290 - Satoshi Port: 8333
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1291 - Do wlt check: True
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1292 - Named options/arguments to armoryengine.py:
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     thread_count    : -1
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     rescan          : False
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     ignoreAllZC     : False
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     rescanBalance   : False
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     disableModules  : False
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     port            : None
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     interport       : 8223
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     coverageOutputDir: None
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     forceWalletCheck: False
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     regtest         : False
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     rebuild         : False
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     nettimeout      : 2
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     datadir         : DEFAULT
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     clearMempool    : False
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     offline         : False
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     armoryDBDir     : DEFAULT
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     armorydb_port   : 9001
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     satoshiPort     : DEFAULT
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     useTorSettings  : False
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     netlog          : False
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     keypool         : 100
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     coverageInclude : None
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     forceOnline     : False
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     redownload      : False
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     rpcBindAddr     : 127.0.0.1
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     armorydb_ip     : 127.0.0.1
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     multisigFile    : DEFAULT
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     ram_usage       : -1
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     mtdebug         : False
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     logDisable      : False
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     settingsPath    : C:\Users\Main\AppData\Roaming\Armory\ArmorySettings.txt
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     language        : en
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     db_type         : DB_FULL
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     doDebug         : False
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     enableDetSign   : True
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     disableConfPermis: False
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     testnet         : False
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     rpcport         : DEFAULT
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     satoshiHome     : DEFAULT
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     satoshiRpcport  : DEFAULT
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     logFile         : C:\Users\Main\AppData\Roaming\Armory\ArmoryQt.exe.log.txt
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1294 -     verbosity       : None
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1295 - Other arguments:
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1298 - ************************************************************
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:1701 - C++ block utilities loaded successfully
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:3559 - Using settings file: C:\Users\Main\AppData\Roaming\Armory\ArmorySettings.txt
2017-12-04 11:26:40 (ERROR) -- ArmoryUtils.pyc:3716 - Unsupported language  specified. Defaulting to English (en)
2017-12-04 11:26:40 (INFO) -- ArmoryUtils.pyc:3719 - Using Language: en
2017-12-04 11:26:40 (INFO) -- BDM.pyc:355 - Using the asynchronous/multi-threaded BlockDataManager.
2017-12-04 11:26:40 (INFO) -- BDM.pyc:356 - Blockchain operations will happen in the background.  
2017-12-04 11:26:40 (INFO) -- BDM.pyc:357 - Devs: check TheBDM.getState() before asking for data.
2017-12-04 11:26:40 (INFO) -- BDM.pyc:358 - Registering addresses during rescans will queue them for
2017-12-04 11:26:40 (INFO) -- BDM.pyc:359 - inclusion after the current scan is completed.
2017-12-04 11:26:42 (INFO) -- ArmoryUtils.pyc:3559 - Using settings file: C:\Users\Tam\AppData\Roaming\Armory\ArmorySettings.txt
2017-12-04 11:26:42 (INFO) -- ArmoryQt.py:2061 - loadWalletsAndSettings
2017-12-04 11:26:42 (INFO) -- ArmoryQt.py:2121 - Loading wallets...
2017-12-04 11:26:43 (INFO) -- ArmoryQt.py:2186 - Number of wallets read in: 1
2017-12-04 11:26:43 (INFO) -- ArmoryQt.py:2191 -    Wallet (walletID):   "WalletName                       "   (Encrypted)
2017-12-04 11:26:43 (INFO) -- ArmoryQt.py:1763 - acquiring process mutex...
2017-12-04 11:26:44 (INFO) -- ArmoryQt.py:1395 - setupUriRegistration
2017-12-04 11:26:44 (INFO) -- ArmoryQt.py:1463 - Armory already registered for current user.  Done!
2017-12-04 11:26:44 (INFO) -- ArmoryQt.py:566 - Usermode: Advanced
2017-12-04 11:26:44 (INFO) -- ArmoryQt.py:1698 - Changing usermode:
2017-12-04 11:26:44 (INFO) -- ArmoryQt.py:1699 -    From: Advanced
2017-12-04 11:26:44 (INFO) -- ArmoryQt.py:1707 -      To: Advanced
2017-12-04 11:26:44 (INFO) -- ArmoryQt.py:1836 - startBitcoindIfNecessary
2017-12-04 11:26:44 (INFO) -- ArmoryQt.py:1872 - setSatoshiPaths
2017-12-04 11:26:44 (INFO) -- ArmoryQt.py:1892 - Setting satoshi datadir = D:\Bitcoin
2017-12-04 11:26:44 (INFO) -- SDM.pyc:251 - Found Bitcoin Core link on desktop: C:\Program Files
2017-12-04 11:26:44 (INFO) -- SDM.pyc:251 - Found Bitcoin Core link on desktop: D:\
2017-12-04 11:26:44 (INFO) -- SDM.pyc:251 - Found Bitcoin Core link on desktop: C:\Program Files\Bitcoin
2017-12-04 11:26:44 (INFO) -- SDM.pyc:169 - Found bitcoind in the following places:
2017-12-04 11:26:44 (INFO) -- SDM.pyc:171 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-12-04 11:26:44 (INFO) -- SDM.pyc:171 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-12-04 11:26:44 (INFO) -- SDM.pyc:171 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-12-04 11:26:44 (INFO) -- SDM.pyc:171 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-12-04 11:26:44 (INFO) -- SDM.pyc:173 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
2017-12-04 11:26:44 (INFO) -- SDM.pyc:337 - Called startBitcoind
2017-12-04 11:26:45 (WARNING) -- SDM.pyc:439 - Spawning bitcoind with command: C:\Program Files\Bitcoin\daemon\bitcoind.exe -datadir=D:\Bitcoin
2017-12-04 11:26:45 (INFO) -- ArmoryUtils.pyc:672 - Executing popen: [u'C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=D:\\Bitcoin']
2017-12-04 11:26:45 (INFO) -- SDM.pyc:445 - PID of bitcoind: 12644
2017-12-04 11:26:45 (INFO) -- SDM.pyc:446 - PID of armory:   12772
2017-12-04 11:26:45 (INFO) -- ArmoryUtils.pyc:672 - Executing popen: ['.\\guardian.exe', '12772', '12644']
2017-12-04 11:26:48 (INFO) -- ArmoryQt.py:1872 - setSatoshiPaths
2017-12-04 11:26:48 (INFO) -- ArmoryQt.py:1892 - Setting satoshi datadir = D:\Bitcoin
2017-12-04 11:26:48 (WARNING) -- SDM.pyc:396 - Spawning DB with command: ./ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="D:\Bitcoin\blocks" --datadir="C:\Users\Main\AppData\Roaming\Armory\" --dbdir="C:\Users\Main\AppData\Roaming\Armory\databases"
2017-12-04 11:26:48 (INFO) -- ArmoryUtils.pyc:672 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', u'--satoshi-datadir="D:\\Bitcoin\\blocks"', '--datadir="C:\\Users\\Main\\AppData\\Roaming\\Armory\\"', u'--dbdir="C:\\Users\\Main\\AppData\\Roaming\\Armory\\databases"']
2017-12-04 11:26:52 (INFO) -- ArmoryQt.py:1824 - Connecting on port 60170
2017-12-04 11:26:52 (INFO) -- ArmoryQt.py:1924 - Setting netmode: 1
2017-12-04 11:26:53 (INFO) -- ArmoryQt.py:1906 - loadBlockchainIfNecessary
2017-12-04 11:26:53 (INFO) -- ArmoryQt.py:1924 - Setting netmode: 1
2017-12-04 11:26:53 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:26:53 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:32:00 (WARNING) -- ArmoryQt.py:4108 - Called updateSyncProgress while not sync'ing
2017-12-04 11:32:01 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:32:47 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:33:20 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:33:51 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:34:23 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:34:55 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:35:28 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:36:00 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:36:28 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:36:58 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:37:25 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:37:28 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:37:35 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:37:35 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:40:59 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:40:59 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:40:59 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:40:59 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:41:00 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:42:42 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:43:14 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:43:31 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:43:46 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:44:03 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:44:19 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:44:37 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:44:55 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:45:11 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:45:29 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:45:42 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:45:58 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:46:14 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:46:30 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:46:45 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:47:02 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:47:15 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:47:27 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:47:43 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:48:00 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:48:16 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:48:32 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:48:50 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:49:08 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:49:30 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:49:51 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:50:15 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:50:33 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:51:10 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:51:46 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:52:28 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:53:17 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:54:14 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:55:07 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:56:10 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:56:50 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:57:20 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:58:08 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 11:59:11 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:00:18 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:01:02 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:02:05 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:03:05 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:03:46 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:04:18 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:05:11 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:06:12 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:07:52 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:09:47 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:11:41 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:13:41 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:15:29 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:17:29 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:19:27 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:21:24 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:23:32 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:25:28 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:27:25 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:29:17 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:31:03 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:32:57 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:34:25 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:36:05 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:37:43 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:39:20 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:41:00 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:42:39 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:44:23 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:46:00 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:47:40 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:49:24 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:51:06 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:52:46 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:54:22 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:55:51 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:57:34 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 12:59:11 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 13:00:50 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 13:02:31 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 13:04:22 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 13:06:05 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 13:07:37 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 13:09:18 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 13:11:09 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 13:12:55 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 13:14:38 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 13:16:25 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 13:18:20 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 13:20:09 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 13:22:02 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 13:23:48 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 13:25:47 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 13:27:30 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 13:29:20 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 13:31:03 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 13:32:53 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode
2017-12-04 13:34:42 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode

goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3752
Merit: 1364

Armory Developer


View Profile
December 04, 2017, 02:32:24 PM
 #7

Use RC1

Craners (OP)
Newbie
*
Offline Offline

Activity: 12
Merit: 0


View Profile
December 21, 2017, 11:28:34 PM
 #8

9.6.4 RC1 loads fine and gets online and I can see my correct balance in Spendable Funds.
However I still cannot merge or overwrite the wallet. When I press Merge or Overwrite nothing happens.

The log says:
Code:
2017-12-21 23:00:57 (INFO) -- ArmoryQt.py:2887 - removeWalletFromApplication
2017-12-21 23:00:57 (ERROR) -- Traceback (most recent call last):
   File "qtdialogs.pyc", line 12556, in SaveMeta
   File "qtdialogs.pyc", line 12520, in Replace
   File "ArmoryQt.py", line 2907, in removeWalletFromApplication
   File "ArmoryQt.py", line 2724, in walletListChanged
   File "ArmoryQt.py", line 787, in changeWltFilter
IndexError: list assignment index out of range

2017-12-21 23:01:12 (INFO) -- ArmoryQt.py:2887 - removeWalletFromApplication
2017-12-21 23:01:12 (ERROR) -- ArmoryQt.py:2892 - Invalid wallet ID
passed to "removeWalletFromApplication"
2017-12-21 23:01:12 (ERROR) -- Traceback (most recent call last):
   File "qtdialogs.pyc", line 12556, in SaveMeta
   File "qtdialogs.pyc", line 12520, in Replace
   File "ArmoryQt.py", line 2893, in removeWalletFromApplication
WalletExistsError

So I assumed I needed to remove the wallet from my data as suggested above. However I went to my AppData Armory folder and found my old wallet file is there as well as what looks like a new wallet file which was created today, but instead of a .wallet file it is a .lmdb file.

So I'm not sure how to proceed. What do you suggest I do next?
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3752
Merit: 1364

Armory Developer


View Profile
December 22, 2017, 12:29:37 AM
 #9

The .lmdb are WO copies. You can delete them, they're built on the fly. Only the .wallet files matter

Craners (OP)
Newbie
*
Offline Offline

Activity: 12
Merit: 0


View Profile
December 22, 2017, 07:05:26 PM
 #10

I removed the .wallet and .lmdb files but now when I run Armory before it launches past the loading screen I get an error saying an error occurred, look in the logs.

The end of my log file now says:
Code:
2017-12-22 18:48:11 (WARNING) -- SDM.pyc:439 - Spawning bitcoind with
command: C:\Program Files\Bitcoin\daemon\bitcoind.exe -datadir=D:\Bitcoin
2017-12-22 18:48:11 (INFO) -- ArmoryUtils.pyc:676 - Executing popen:
[u'C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe',
u'-datadir=D:\\Bitcoin']
2017-12-22 18:48:11 (INFO) -- SDM.pyc:445 - PID of bitcoind: 9792
2017-12-22 18:48:11 (INFO) -- SDM.pyc:446 - PID of armory:   9436
2017-12-22 18:48:11 (INFO) -- ArmoryUtils.pyc:676 - Executing popen:
['.\\guardian.exe', '9436', '9792']
2017-12-22 18:48:13 (INFO) -- ArmoryQt.py:1924 - Setting netmode: 1
2017-12-22 18:48:13 (ERROR) -- Traceback (most recent call last):
   File "ArmoryQt.py", line 5979, in <module>
   File "ArmoryQt.py", line 685, in __init__
   File "ArmoryQt.py", line 5740, in startBlockchainProcessingInitialization
   File "ArmoryQt.py", line 5764, in
completeBlockchainProcessingInitialization
   File "ArmoryQt.py", line 5841, in setupLedgerViews
   File "ArmoryQt.py", line 787, in changeWltFilter
IndexError: list assignment index out of range
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3752
Merit: 1364

Armory Developer


View Profile
December 22, 2017, 07:07:55 PM
 #11

Can you start ArmoryQt in offline mode?

Craners (OP)
Newbie
*
Offline Offline

Activity: 12
Merit: 0


View Profile
December 22, 2017, 11:46:34 PM
 #12

I'm not sure how to start it in offline mode? How do I do that?

If I add the wallet files back to the data folder then Armory opens fine and begins doing the Loading Database Headers phase. If I remove the wallet files from the data folder then I only get the splash page with Loading: X% at the top, and then I get the error message before anything else happens.
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3752
Merit: 1364

Armory Developer


View Profile
December 23, 2017, 01:06:54 AM
 #13

Run it with the --offline command line argument

Craners (OP)
Newbie
*
Offline Offline

Activity: 12
Merit: 0


View Profile
December 23, 2017, 11:08:38 AM
 #14

Yep, that loads fine both with and without the wallet files.
Craners (OP)
Newbie
*
Offline Offline

Activity: 12
Merit: 0


View Profile
January 07, 2018, 03:47:10 PM
 #15

Sorry, I wasn't very useful with my previous post - the offline trick works and Armory loads fine like that.
Can I restore my wallet with Armory in that state or do I need to do something further?
PhoenixFire
Member
**
Offline Offline

Activity: 270
Merit: 36


View Profile
January 07, 2018, 04:14:04 PM
 #16

Sorry, I wasn't very useful with my previous post - the offline trick works and Armory loads fine like that.
Can I restore my wallet with Armory in that state or do I need to do something further?

I think the intention is that you try restoring the wallet in that state and then go online again afterwards.
Craners (OP)
Newbie
*
Offline Offline

Activity: 12
Merit: 0


View Profile
January 27, 2018, 09:14:09 PM
 #17

I got Armory loading up in offline mode, I restored my wallet with my paper backup and the wallet name is showing as such.
I ran bitcoinqt to get that up to date.
I restarted Armory in online mode, but eventually got stuck again in Scanning Transaction History and is showing Node offline (0 blocks)

I am completely out of ideas now.

Latest log file snippet here:
Code:
2018-01-27 16:54:13 (INFO) -- SDM.pyc:169 - Found bitcoind in the following places:
2018-01-27 16:54:13 (INFO) -- SDM.pyc:171 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2018-01-27 16:54:13 (INFO) -- SDM.pyc:171 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2018-01-27 16:54:13 (INFO) -- SDM.pyc:171 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2018-01-27 16:54:13 (INFO) -- SDM.pyc:171 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2018-01-27 16:54:13 (INFO) -- SDM.pyc:173 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
2018-01-27 16:54:13 (INFO) -- SDM.pyc:337 - Called startBitcoind
2018-01-27 16:54:14 (WARNING) -- SDM.pyc:439 - Spawning bitcoind with command: C:\Program Files\Bitcoin\daemon\bitcoind.exe -datadir=D:\Bitcoin
2018-01-27 16:54:14 (INFO) -- ArmoryUtils.pyc:676 - Executing popen: [u'C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=D:\\Bitcoin']
2018-01-27 16:54:15 (INFO) -- SDM.pyc:445 - PID of bitcoind: 11488
2018-01-27 16:54:15 (INFO) -- SDM.pyc:446 - PID of armory:   224
2018-01-27 16:54:15 (INFO) -- ArmoryUtils.pyc:676 - Executing popen: ['.\\guardian.exe', '224', '11488']
2018-01-27 16:54:18 (INFO) -- ArmoryQt.py:1872 - setSatoshiPaths
2018-01-27 16:54:18 (INFO) -- ArmoryQt.py:1892 - Setting satoshi datadir = D:\Bitcoin
2018-01-27 16:54:18 (WARNING) -- SDM.pyc:396 - Spawning DB with command: ./ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="D:\Bitcoin\blocks" --datadir="C:\Users\Main\AppData\Roaming\Armory\" --dbdir="C:\Users\Main\AppData\Roaming\Armory\databases"
2018-01-27 16:54:18 (INFO) -- ArmoryUtils.pyc:676 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', u'--satoshi-datadir="D:\\Bitcoin\\blocks"', '--datadir="C:\\Users\\Main\\AppData\\Roaming\\Armory\\"', u'--dbdir="C:\\Users\\Main\\AppData\\Roaming\\Armory\\databases"']
2018-01-27 16:55:27 (INFO) -- ArmoryQt.py:1824 - Connecting on port 57569
2018-01-27 16:55:27 (INFO) -- ArmoryQt.py:1924 - Setting netmode: 1
2018-01-27 16:55:32 (INFO) -- ArmoryQt.py:1906 - loadBlockchainIfNecessary
2018-01-27 16:55:32 (INFO) -- ArmoryQt.py:1924 - Setting netmode: 1
2018-01-27 16:55:32 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 16:55:33 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 16:57:40 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 16:58:36 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 16:59:28 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:00:10 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:00:58 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:01:41 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:02:18 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:02:50 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:03:26 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:03:58 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:04:31 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:04:34 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:04:37 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:04:54 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:05:11 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:05:15 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:05:19 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:08:52 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:10:13 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:11:09 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:11:09 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:11:09 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:11:09 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:12:54 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:13:37 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:13:58 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:14:15 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:14:33 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:14:49 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:15:08 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:15:31 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:15:50 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:16:11 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:16:32 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:16:55 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:17:18 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:17:39 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:18:00 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:18:21 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:18:40 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:18:59 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:19:19 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:19:39 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:19:58 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:20:14 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:20:33 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:20:57 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:21:24 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:21:45 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:22:08 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:22:29 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:22:52 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:23:17 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:23:40 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:24:02 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:24:25 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:24:47 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:25:07 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:25:30 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:25:55 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:26:18 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:26:47 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:27:30 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:28:40 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:29:48 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:30:48 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:31:55 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:33:01 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:34:11 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:35:29 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:37:13 (INFO) -- ArmoryQt.py:4615 - Dashboard switched to auto-InitSync
2018-01-27 17:37:13 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:39:06 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:40:58 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:42:53 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:44:47 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:46:38 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:48:29 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-01-27 17:50:21 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
jojo69
Legendary
*
Offline Offline

Activity: 3346
Merit: 4621


diamond-handed zealot


View Profile
January 29, 2018, 07:34:57 AM
 #18

Are you running core manually or having Armory manage it?

This is not some pseudoeconomic post-modern Libertarian cult, it's an un-led, crowd-sourced mega startup organized around mutual self-interest where problems, whether of the theoretical or purely practical variety, are treated as temporary and, ultimately, solvable.
Censorship of e-gold was easy. Censorship of Bitcoin will be… entertaining.
clemdementhe
Newbie
*
Offline Offline

Activity: 24
Merit: 2


View Profile
January 29, 2018, 01:15:20 PM
 #19

It can take several hours for Armory to scan the entire blockchain for activity relevant to what it sees as a new wallet. This log shows only an hour of scanning.
Craners (OP)
Newbie
*
Offline Offline

Activity: 12
Merit: 0


View Profile
January 30, 2018, 03:36:54 PM
 #20

Quote
Are you running core manually or having Armory manage it?
I'm running it manually and once that completes, I close it and run Armory. That has worked fine in the past.

Quote
It can take several hours for Armory to scan the entire blockchain for activity relevant to what it sees as a new wallet. This log shows only an hour of scanning.
Sorry, I wasn't clear but I've trimmed hours off the end as it is just repeated for hours. I left it running for over a day and the timer in the UI just stated 1 second remaining endlessly.
Pages: [1] 2 »  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!