Title: Amory stuck at Scanning Database history 1s left Post by: micha445 on December 26, 2020, 01:56:16 PM Amory stuck at Scanning Database history 1s left
Ubuntu, Amory Wallet 0.96.5-beta Title: Re: Amory stuck at Scanning Database history 1s left Post by: micha445 on December 27, 2020, 07:01:23 AM Some error logs
Log file opened at 0+: /home/user/.armory/armorycpplog.txt Log file opened at 0: /home/user/.armory/armorycpplog.txt Log file opened at 03: /home/user/.armory/armorycpplog.txt Log file opened at 0[y: /home/user/.armory/armorycpplog.txt -ERROR - : (SocketObject.cpp:423) poll() error in readAndWrite: 4 -ERROR - : (StringSockets.cpp:359) poll() error in readAndWrite: 4 -ERROR - : (SocketObject.cpp:447) POLLERR error in readAndWrite -ERROR - : (StringSockets.cpp:359) POLLERR error in readAndWrite Log file opened at 0x1: /home/user/.armory/armorycpplog.txt -ERROR - : (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version Log file opened at 0kշ: /home/user/.armory/armorycpplog.txt -ERROR - : (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version Log file opened at 0F: /home/user/.armory/armorycpplog.txt Log file opened at 0;7: /home/user/.armory/armorycpplog.txt Log file opened at 0ߕP: /home/user/.armory/armorycpplog.txt -ERROR - : (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version Log file opened at 0K9: /home/user/.armory/armorycpplog.txt -ERROR - : (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version -ERROR - : (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unknown fcgi header request byte -ERROR - : (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unknown fcgi header request byte -ERROR - : (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unknown fcgi header request byte -ERROR - : (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unknown fcgi header request byte -ERROR - : (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unknown fcgi header request byte -ERROR - : (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unknown fcgi header request byte ----------------------------------------------------------------------------------- Or here last night. Armory just stops scanning -INFO - 02:42:39: (BlockchainScanner.cpp:852) scanned from block #645216 to #645630 -INFO - 02:42:47: (BlockchainScanner.cpp:852) scanned from block #645631 to #646040 Then, nothing anymore. Title: Re: Amory stuck at Scanning Database history 1s left Post by: micha445 on December 27, 2020, 10:53:36 AM Nobody? How can I get Armory running again? Why is it stuck?
2020-12-27 11:41:56 (INFO) -- ArmoryQt.py:1824 - Connecting on port 59552 2020-12-27 11:41:56 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 1 2020-12-27 11:41:56 (INFO) -- ArmoryQt.py:1905 - loadBlockchainIfNecessary 2020-12-27 11:41:56 (ERROR) -- ArmoryQt.py:1198 - 13 attempts to load blockchain failed. Remove mempool.bin. 2020-12-27 11:41:56 (ERROR) -- ArmoryQt.py:1203 - File mempool.bin does not exist. Nothing deleted. 2020-12-27 11:41:56 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 1 2020-12-27 11:41:56 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode 2020-12-27 11:41:56 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode . . . . . Title: Re: Amory stuck at Scanning Database history 1s left Post by: goatpig on December 27, 2020, 11:54:10 PM Either there is a zombie armorydb instance or there is another process listening on the port it is trying to use.
Title: Re: Amory stuck at Scanning Database history 1s left Post by: micha445 on December 31, 2020, 09:43:01 AM Either there is a zombie armorydb instance or there is another process listening on the port it is trying to use. OK. And how can I find this out/fix? Best M Title: Re: Amory stuck at Scanning Database history 1s left Post by: goatpig on December 31, 2020, 10:31:04 AM 1. Make sure ArmoryDB isn't running
2. Run ArmoryDB from the terminal, it shouldn't require any arguments for now 3. Start ArmoryQt from another terminal, it should connect to ArmoryDB. Report here at any rate. Title: Re: Amory stuck at Scanning Database history 1s left Post by: Tolosi on April 24, 2021, 11:18:45 AM I have the same problem.
Scanning stops at 30% 1 second remaining. I did call ArmoryDB from cmd prompt and then ArmoryQT and it says at 30%: scanned from block #453890 to #454449 Missing file map for output scan, this is unexpected Has the following block files: --- #786 --- #787 --- #789 --- #789 --- #790 --- #791 --- #792 Was looking for id #793 scanned from block #454450 to #455014 and then it exits - cmd prompt starts blinking and nothing ever happens. Any idea how to solve this? Title: Re: Amory stuck at Scanning Database history 1s left Post by: HCP on April 24, 2021, 10:40:07 PM Is your Bitcoin Core node fully synced? Is your Bitcoin Core node pruned or unpruned? ???
Title: Re: Amory stuck at Scanning Database history 1s left Post by: Tolosi on April 25, 2021, 01:43:41 AM I am doing a -reidex-chainstate now and it will take one more day. Before start of reindexing it was fully synced.
On the Settings Options pruning box is Not ticked. Title: Re: Amory stuck at Scanning Database history 1s left Post by: NotATether on April 25, 2021, 07:10:21 AM It sounds like you're missing blk00793.dat on your full node's blocks folder. This is a fairly old block so what probably happened is that your armory DB is not fully synced with your full node.
Try running -reindex on Core, or click Help > Rebuild and Rescan Databases from within Armory if that option is a available. Title: Re: Amory stuck at Scanning Database history 1s left Post by: Tolosi on April 25, 2021, 07:26:58 AM I already tried that and no change.
Block 793 is on the disc with the same date as the others. Maybe it is somehow corrupted by the hard disk. Now I am doing -reindex-chainstate and it takes very very long time - 3 days already close to 70% done now. Most of this time HDD shows load of 100% and CPT only 2 - 4 % so I suspect HDD is bad somehow. Probably I will buy a new 1TB SSD and start all over Windows and then Bitcoin Core + full blockchain download + Armory on top. I see no other option now. |