Hi,
I try to restore an old paper wallet (2 years) since many weeks already.
First I tried to get it work on ubuntu, which I managed to a point that armory was online but the node was offline. Tried to get that working beeing not the only one with this problem and at end I resigned.
Then I tried to do it on a windows 10 professional machine, using the synched blockchain from ubuntu on an external USB drive.
At first armory did not do anything, no spinners no progression in progress bars.
I tried to startbitcoin QT alongside with armory disabling the bitcoind from armory - did not work either.
Bitcoin QT was fully synced and properly uses the external blockdata on my external harddrive.
I did countless restarts and reboots doing try&error of different configurations and at the and magically armory started to build the database and can the blockchain - bingo.
This happend in a very strange configuration: Bitcoin QT running in background but bitcoind-option in armory set as well! Additionally the path to the blockdata gven explicitelly in armory config.
After scanning and organizing the blockchain I was now able to see my balance and armory was online as well as the node. bingo!
Now I wanted to test the transfer from my armory wallet to my trezor by sending a small BTC amount which worked, but now armory is not able to fetch the confirmations, it just says I have no spendable funds!
The balance in wallet is OK, the small test amount went to my trezor successfully and has been confirmed countless times.
But the "spendable funds" are 0.00000000 BTC.
The green status in the lower right corner says "online (3xxxxx blocks)". So 3 hundred something - not the current block height of 504665.
I regrett not to have transfered the full amount directly first time but it was to dangereous for me, since I never really used armory before.
I just installed it years ago and did a paper backup straight away, then just forgot about bitcoin for a long while.
Please help - I am so tierd trying, each restart takes hopurs to evluate the result because of all this blockchain scanning and organizing beeing very slow - if it start at all.
I let it run, then check next day with very different results
I just want to transfer my funds out of this thing once and for all. Please help !!! :-)
BTW. I configured bitcoin QT to start the RPC server
bitcoin QT seems to have a problem starting the RPC server (2018-01-17 12:05:20 Binding RPC on address ::1 port 8332 failed.) but when I check the used ports afterwards, windows states the following:
TCP 127.0.0.1:8332 DELL-T3500-PC3:0 LISTENING
[bitcoin-qt.exe]
Here is the full log from bitcoin QT
2018-01-17 12:05:19 Bitcoin version v0.15.1
2018-01-17 12:05:19 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2018-01-17 12:05:20 Assuming ancestors of block 0000000000000000003b9ce759c2a087d52abc4266f8f4ebd6d768b89defa50a have valid signatures.
2018-01-17 12:05:20 Setting nMinimumChainWork=000000000000000000000000000000000000000000723d3581fe1bd55373540a
2018-01-17 12:05:20 Using the 'standard' SHA256 implementation
2018-01-17 12:05:20 Default data directory C:\Users\artur\AppData\Roaming\Bitcoin
2018-01-17 12:05:20 Using data directory F:\__BACKUP\_bitcoin_new
2018-01-17 12:05:20 Using config file F:\__BACKUP\_bitcoin_new\bitcoin.conf
2018-01-17 12:05:20 Using at most 125 automatic connections (2048 file descriptors available)
2018-01-17 12:05:20 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2018-01-17 12:05:20 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2018-01-17 12:05:20 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2018-01-17 12:05:20 Using 2 threads for script verification
2018-01-17 12:05:20 scheduler thread start
2018-01-17 12:05:20 libevent: getaddrinfo: nodename nor servname provided, or not known
2018-01-17 12:05:20 Binding RPC on address ::1 port 8332 failed.
2018-01-17 12:05:20 HTTP: creating work queue of depth 16
2018-01-17 12:05:20 No rpcpassword set - using random cookie authentication
2018-01-17 12:05:20 Generated RPC authentication cookie F:\__BACKUP\_bitcoin_new\.cookie
2018-01-17 12:05:20 HTTP: starting 4 worker threads
2018-01-17 12:05:20 init message: Verifying wallet(s)...
2018-01-17 12:05:20 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2018-01-17 12:05:20 Using wallet wallet.dat
2018-01-17 12:05:20 CDBEnv::Open: LogDir=F:\__BACKUP\_bitcoin_new\database ErrorFile=F:\__BACKUP\_bitcoin_new\db.log
2018-01-17 12:05:20 Cache configuration:
2018-01-17 12:05:20 * Using 2.0MiB for block index database
2018-01-17 12:05:20 * Using 8.0MiB for chain state database
2018-01-17 12:05:20 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2018-01-17 12:05:20 init message: Loading block index...
2018-01-17 12:05:20 Opening LevelDB in F:\__BACKUP\_bitcoin_new\blocks\index
2018-01-17 12:05:20 Opened LevelDB successfully
2018-01-17 12:05:20 Using obfuscation key for F:\__BACKUP\_bitcoin_new\blocks\index: 0000000000000000
2018-01-17 12:05:30 LoadBlockIndexDB: last block file = 1142
2018-01-17 12:05:30 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=126, size=132902296, heights=504538...504663, time=2018-01-16...2018-01-17)
2018-01-17 12:05:30 Checking all blk files are present...
2018-01-17 12:05:35 LoadBlockIndexDB: transaction index disabled
2018-01-17 12:05:35 Opening LevelDB in F:\__BACKUP\_bitcoin_new\chainstate
2018-01-17 12:05:36 Opened LevelDB successfully
2018-01-17 12:05:36 Using obfuscation key for F:\__BACKUP\_bitcoin_new\chainstate: babf7d912f9469c5
2018-01-17 12:05:36 Loaded best chain: hashBestChain=0000000000000000001f3293288fdb981c8aee2ac4311b76695c337363204263 height=504663 date=2018-01-17 11:54:33 progress=0.999993
2018-01-17 12:05:36 init message: Rewinding blocks...
2018-01-17 12:05:38 init message: Verifying blocks...
2018-01-17 12:05:38 Verifying last 6 blocks at level 3
2018-01-17 12:05:38 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2018-01-17 12:05:45 No coin database inconsistencies in last 7 blocks (7690 transactions)
2018-01-17 12:05:45 block index 24781ms
2018-01-17 12:05:45 init message: Loading wallet...
2018-01-17 12:05:45 nFileVersion = 150100
2018-01-17 12:05:45 Keys: 1002 plaintext, 0 encrypted, 1002 w/ metadata, 1002 total
2018-01-17 12:05:45 wallet 116ms
2018-01-17 12:05:45 setKeyPool.size() = 1000
2018-01-17 12:05:45 mapWallet.size() = 0
2018-01-17 12:05:45 mapAddressBook.size() = 1
2018-01-17 12:05:45 mapBlockIndex.size() = 504687
2018-01-17 12:05:45 nBestHeight = 504663
2018-01-17 12:05:45 torcontrol thread start
2018-01-17 12:05:45 Bound to [::]:8333
2018-01-17 12:05:45 Bound to 0.0.0.0:8333
2018-01-17 12:05:45 init message: Loading P2P addresses...
2018-01-17 12:05:45 Leaving InitialBlockDownload (latching to false)
2018-01-17 12:05:46 Loaded 66025 addresses from peers.dat 547ms
2018-01-17 12:05:46 init message: Loading banlist...
2018-01-17 12:05:46 init message: Starting network threads...
2018-01-17 12:05:46 net thread start
2018-01-17 12:05:46 dnsseed thread start
2018-01-17 12:05:46 addcon thread start
2018-01-17 12:05:46 opencon thread start
2018-01-17 12:05:46 msghand thread start
2018-01-17 12:05:46 init message: Done loading
2018-01-17 12:05:46 GUI: Platform customization: "windows"
2018-01-17 12:05:46 GUI: PaymentServer::LoadRootCAs: Loaded 42 root certificates
2018-01-17 12:05:47 receive version message: /Satoshi:0.15.1/: version 70015, blocks=504663, us=89.78.6.75:49946, peer=0
2018-01-17 12:05:47 receive version message: /Satoshi:0.15.0/: version 70015, blocks=504663, us=89.78.6.75:49947, peer=1
2018-01-17 12:05:52 receive version message: /Satoshi:0.13.2/: version 70015, blocks=504663, us=89.78.6.75:49949, peer=2
2018-01-17 12:05:57 P2P peers available. Skipped DNS seeding.
2018-01-17 12:05:57 dnsseed thread exit
2018-01-17 12:06:52 receive version message: /Satoshi:0.15.0.1/: version 70015, blocks=504663, us=89.78.6.75:49960, peer=3
2018-01-17 12:07:17 version handshake timeout from 3
2018-01-17 12:07:25 receive version message: /Satoshi:0.15.1/: version 70015, blocks=504663, us=89.78.6.75:49966, peer=4
2018-01-17 12:07:26 receive version message: /Satoshi:0.15.0.1/: version 70015, blocks=504663, us=89.78.6.75:49968, peer=5
2018-01-17 12:07:26 receive version message: /Satoshi:0.15.1/: version 70015, blocks=504664, us=89.78.6.75:49969, peer=6
2018-01-17 12:07:28 receive version message: /Satoshi:0.15.1/: version 70015, blocks=504664, us=89.78.6.75:49973, peer=7
2018-01-17 12:07:48 receive version message: /Satoshi:0.15.0.1/: version 70015, blocks=504664, us=89.78.6.75:49975, peer=8
And here is what armory is logging for this scenario. Armory does nothing, no progress in bars, no spinner, no syncing, no activity in process manager:
Log file opened at 12:56:02.000: C:\Users\artur\AppData\Roaming\Armory\dbLog.txt
-INFO - 12:56:02.000: (..\main.cpp:32) Running on 2 threads
-INFO - 12:56:02.000: (..\main.cpp:33) Ram usage level: 4
-INFO - 12:56:02.000: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:263) Listening on port 9001
For the other working (sometimes working and just to some extend working!) scenario (Armory magaes bitcoind and the blockchain itself) this is what is in the logs.
But then as I stated above I get no confirmations of my latest test transaction because armory seems to be stuck somewhere in the past
Log file opened at 08:57:39.000: C:\Users\artur\AppData\Roaming\Armory\dbLog.txt
-INFO - 08:57:39.000: (..\main.cpp:32) Running on 2 threads
-INFO - 08:57:39.000: (..\main.cpp:33) Ram usage level: 4
-INFO - 08:57:39.000: (..\BlockUtils.cpp:915) blkfile dir: F:\__BACKUP\_bitcoin_new\blocks
-INFO - 08:57:39.000: (..\BlockUtils.cpp:916) lmdb dir: C:\Users\artur\AppData\Roaming\Armory\databases
-INFO - 08:57:39.000: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 08:57:39.172: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:263) Listening on port 55069
-INFO - 08:57:40.250: (..\BDM_Server.cpp:1114) registered bdv: 5f11321b77dcdca7e14e
-INFO - 08:58:46.610: (..\nodeRPC.cpp:57) RPC connection established
-INFO - 08:58:46.641: (..\nodeRPC.cpp:346) Node is ready
-INFO - 08:58:46.641: (..\BlockUtils.cpp:1108) Executing: doInitialSyncOnLoad
-INFO - 08:58:47.766: (..\DatabaseBuilder.cpp:199) Reading headers from db
-INFO - 08:58:48.781: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO - 08:58:51.969: (..\DatabaseBuilder.cpp:238) Found 352780 headers in db
-INFO - 08:58:54.344: (..\DatabaseBuilder.cpp:64) Rewinding 100 blocks
-INFO - 08:58:54.344: (..\DatabaseBuilder.cpp:71) updating HEADERS db
-INFO - 08:58:54.391: (..\DatabaseBuilder.cpp:493) Found next block after skipping 605177bytes
-INFO - 08:58:55.016: (..\DatabaseBuilder.cpp:281) parsed block file #258
-INFO - 08:59:17.453: (..\DatabaseBuilder.cpp:281) parsed block file #260
[...]
-INFO - 11:11:28.297: (..\DatabaseBuilder.cpp:281) parsed block file #1138
-INFO - 11:11:29.297: (..\DatabaseBuilder.cpp:281) parsed block file #1140
-INFO - 11:11:29.563: (..\Blockchain.cpp:248) Organizing chain
-INFO - 19:08:31.781: (..\Blockchain.cpp:370) Organized chain in 28621s
-INFO - 19:08:31.828: (..\DatabaseBuilder.cpp:76) updated HEADERS db in 36576s
-INFO - 19:08:31.906: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 19:08:31.906: (..\DatabaseBuilder.cpp:1231) verifying txfilters integrity
-INFO - 19:08:31.547: (..\DatabaseBuilder.cpp:1314) done checking txfilters
-INFO - 19:08:31.672: (..\DatabaseBuilder.cpp:134) scanning new blocks from #352780 to #352779
-INFO - 19:08:31.672: (..\BlockchainScanner.cpp:52) no history to scan
-INFO - 19:08:31.688: (..\BlockchainScanner.cpp:1019) no SSH to scan
-INFO - 19:08:32.969: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO - 19:08:32.969: (..\DatabaseBuilder.cpp:186) scanned new blocks in 0s
-INFO - 19:08:32.969: (..\DatabaseBuilder.cpp:190) init db in 36585s
-INFO - 19:08:32.969: (..\BDM_supportClasses.cpp:1890) Enabling zero-conf tracking
-WARN - 19:08:36.078: (..\BDM_supportClasses.cpp:1943) running 5 zc parser threads
-WARN - 19:08:36.078: (..\BDM_supportClasses.cpp:1943) running 10 zc parser threads
-WARN - 19:08:36.094: (..\BDM_supportClasses.cpp:1943) running 15 zc parser threads
-WARN - 19:08:49.610: (..\BDM_supportClasses.cpp:1943) running 20 zc parser threads
-WARN - 19:08:49.610: (..\BDM_supportClasses.cpp:1943) running 25 zc parser threads
-WARN - 19:08:49.610: (..\BDM_supportClasses.cpp:1943) running 30 zc parser threads
-WARN - 19:08:49.610: (..\BDM_supportClasses.cpp:1943) running 35 zc parser threads
-WARN - 21:33:03.156: (..\BDM_supportClasses.cpp:1943) running 40 zc parser threads
-WARN - 21:33:03.172: (..\BDM_supportClasses.cpp:1943) running 45 zc parser threads
-WARN - 21:33:03.172: (..\BDM_supportClasses.cpp:1943) running 50 zc parser threads
-WARN - 21:33:03.172: (..\BDM_supportClasses.cpp:1943) running 55 zc parser threads
-WARN - 21:33:03.172: (..\BDM_supportClasses.cpp:1943) running 60 zc parser threads
-WARN - 21:33:03.172: (..\BDM_supportClasses.cpp:1943) running 65 zc parser threads
-WARN - 22:13:39.875: (..\BDM_supportClasses.cpp:1943) running 70 zc parser threads
-WARN - 18:40:18.547: (..\BDM_supportClasses.cpp:1943) running 75 zc parser threads
-WARN - 18:40:18.563: (..\BDM_supportClasses.cpp:1943) running 80 zc parser threads
-WARN - 22:34:40.156: (..\BDM_supportClasses.cpp:1943) running 85 zc parser threads
-WARN - 22:34:40.156: (..\BDM_supportClasses.cpp:1943) running 90 zc parser threads
-WARN - 22:34:40.156: (..\BDM_supportClasses.cpp:1943) running 95 zc parser threads
-WARN - 22:34:40.156: (..\BDM_supportClasses.cpp:1943) running 100 zc parser threads
-INFO - 12:47:46.891: (..\nodeRPC.cpp:415) Bitcoin server stopping
-ERROR - 12:47:46.688: (..\BitcoinP2P.cpp:1037) caught StopBlockingLoop in processDataStackThread
-INFO - 12:47:46.703: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node
-INFO - 12:47:59.328: (..\BDM_Server.cpp:1143) unregistered bdv: 5f11321b77dcdca7e14e
-INFO - 12:47:59.344: (..\BDM_Server.cpp:1054) proceeding to shutdown
-ERROR - 12:48:02.438: (..\SocketObject.cpp:267) poll() error in readFromSocketThread: 10038
-ERROR - 12:48:02.438: (..\BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: poll() error in readFromSocketThread: 10038
-INFO - 12:48:05.453: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node