Topic: Transaction History Scan, fails (Read 318 times)

Rebuilding and rescan databases fix most common issues related to transactions and databases and also fix crashes.

Newbies or users should do that first as Armory suggested in their troubleshooting guide. The given solution from previous posts on this thread is only if Rebuild and rescan do not work. You might have the same issue as OP but if you check the Armorylog.txt or dblog.txt you will notice the differences.

It's been a while so i don't know if what might of been fixed since, yesterday i just ran the Help>Rebuild and Rescan Databases, let it complete and wallet is functioning again.

The thread title's issue comes in variety of reasons.
OP's issue is seemingly a wrong block in his blockchain; in your case, check the logs (Armorylog.txt & dblog.txt) if the issue you're experiencing is the same as OP's.

Hello everyone, seem to be having this issue myself. Armory gets to Scanning Transaction History then freezes or halts. Don't have much to ask at the moment, just following the conversation and searching for a resolution myself, if i happen to come by one i'll post it.

Thanks to all those involved and helping.

I've seen some developers suggest that before doing a -reindex but I haven't tried it myself.
Specifically this stackoverflow post: https://bitcoin.stackexchange.com/a/54455

Hypothetically speaking  
If i knew whick blockchain file was suspected to be in someway corrupt, if it was deleted or renamed, would
bitcoin rebuild it when it scans the blockchain files and correct the error?

Personally i don't know the answer, nor do i know which blockchain file.
 

Bitcoin Core will still use the one in the default directory, plus it created one in the custom data directory that you put in it so it's using the config.

Now for the same error,
Hmm, everything now checks-out, getblockchaininfo's result is good, pathing is good and Armory's database is fresh.
At this point, I'd guess it's the blockchain, there may be a corrupted block at the point of the error.

-edit-
In the newer versions of Core, if the custom datadir was set in the 'welcome screen' of the GUI, then it wont use the config in the default datadir.
Anyways, it's pointing to the same datadir so, nothing's changed.

>(figured because the actual Bitcoin datadir should have more than one folders in it)
>So we're back to square one, looking for the issue.
H:/Bitcoin       420 GB (451,118,116,864 bytes)   8,430 Files, 9 Folders 
H:/Bitcoin/data  420 GB (451,053,727,744 bytes)   8,326 Files, 4 Folders
Dir as of this moment.

>'bitcoin.conf' 'bitcoin.conf.txt'  hidden extension.
yeah , aware of windows tricks.

>we don't know how did you install bitcoin core and Armory in my experience
It's a win10 machine, and these are the Windows executables install files used most recently, run as user:
 bitcoin-22.0-win64-setup.exe
 armory_0.96.5_win64.exe

 C:\Users\greyaliens\AppData\Roaming\Bitcoin , did not have a bitcoin.conf, it was in the H:\Bitcoin.
 Generated bitcoin.conf in the Roaming\Bitcoin dir, with suggested configs,  and removed existing config from H:/Bitcoin. (just to be sure)
started bitcoin, allow to sync and ran getblockchaininfo in console.
 11:38:51
 getblockchaininfo
  "chain": "main",
  "blocks": 724911,
  "headers": 724911,
  "initialblockdownload": false,
  "size_on_disk": 446030677731,
  "pruned": false,
  "warnings": ""

>If everything checks-out, continue with Armory.
ok.
 Removed config option from shortcut.
"C:\Users\greyaliens\AppData\Roaming\Armory"
added satoshi-datadir line to armoryqt.conf
renamed armoury database dir.

> Now open Armory without the start parameters in the shortcut
Ok,  ran armoury, again

Just looked at Bitcoin/data  and found bitcoin had generated another bitcoin.conf file, 0 length.
I assume when it did not find the bitcoin.conf file there... hmmm

That's the same pathing setting as the previous.

What I want to confirm is: if the correct blocks directory is actually "H:\Bitcoin\data\blocks".
Because it's the one that Armory is using, and it keeps on getting an error that indicates that the blockdir doesn't have the whole blockchain.
But this kinda answered it:
"1 Folders" must be the 'data' folder, so Armory may be using the correct satoshi-datadir "H:\Bitcoin\data" afterall.
(figured because the actual Bitcoin datadir should have more than one folders in it)
So we're back to square one, looking for the issue.

---

Anyways, try these setup

In Bitcoin Core:

• Go to "C:\Users\greyaliens\AppData\Roaming\Bitcoin"
• Find bitcoin.conf file (create one if you don't have it)
• Open it as text, and add the configs datadir=H:\Bitcoin\data and prune=0 (one config per line) then save.
• Start Bitcoin Core, open the console (Window->Console), and enter: getblockchaininfo
• In the result, the line "initialblockdownload" should be false because it indicates that you have the complete blockchain in that datadir;
  you may as well check "blocks": 724826 (value as of now) if the value isn't lower.
  
  

If everything checks-out, continue with Armory.
In Armory:

• Go to "C:\Users\greyaliens\AppData\Roaming\Armory"
• Find armoryqt.conf file (create one if you don't have it)
• Open it as text, and add a line satoshi-datadir="H:\Bitcoin\data" then save.
• Find and rename "database" folder into "database_backup"
• Now open Armory without the start parameters in the shortcut and see if it'll be able to build the database this time.
  
  

BTW, the config files should have the ".conf" as the extension if you have to create them manually by creating a text file and renaming that text file.
Because in Windows, it might display as 'bitcoin.conf' but it's actually 'bitcoin.conf.txt' because of the hidden extension.
In that case, you might need to enable it in Windows File Explorer's setting, tick: "View->File Name Extensions".

Your post looks messy better don't use the quote if you don't know how to use it and better use insert code tag to put all of your logs because it's messy and hard to read without pasting the whole logs.

Look at this sample

You are stuck on this error actually your issue is weird we don't know how did you install bitcoin core and Armory in my experience never had any issue installing and running them. I have only 3 suspected issues why you are stuck here the block #1323 is missing the reason might be your Bitcoin core is set to prune mode or path issue or maybe you have two or multiple Bitcoin data folders and armory is confused.

Why not try to start everything uninstall armory and Bitcoin core and reinstall them again?
Just make sure that you have copies or backup of blocks so that you won't need to redownload them again and start installing the Bitcoin core first before you install Armory again. To clear everything and to point them on the right path.

Yes, -reindex checks the local blockchain for blocks to rebuild the 'block index', so if any of the block is corrupted, it'll have to resync the blockchain from that point.
So I think it may just be "pathing issue" in Armory.

Since you've set that directory as "SatoshiDatadir" to Armory, check if Bitcoin Core is using that as datadir as well.
How did you set Drive H as Bitcoin datadir?
What's the exact directory did you set as Bitcoin datadir?

If you decided to browse to "H:\Bitcoin\data" folder instead, you can check if the blockchain's size is appropriate for a full-synced blockchain.
the blockchain that Armory is using is: "H:\Bitcoin\data\blocks", check the blocks folder's properties and see if the size is about 445GB.
[/quote]

-------------------------
Ok  from today.
Yesterday I went through and put the \data dir  into the shortcuts, as (above) referred to in the troubleshooting guide.
If memory serves,  when bitcoin was re-installed,  the data dir was set back then in the dim past install.  (It was the drive with space)
(dir)   H:\Bitcoin  419 GB (450,776,633,913 bytes) 5,942 Files, 1 Folders

ran armoury, Let bitcoin sync, and... wait for armoury to rebuild it's databases(again)..
sad to say the logs, show things grind to a halt at the same spot, again.
trying not to clutter the post with log entries...but...

----------------- from the logs
Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe --satoshi-datadir=H:\Bitcoin\data
Spawning DB with command: C:\Program Files (x86)\Armory\ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="H:\Bitcoin\data\blocks" --satoshi-port=8333 --datadir="C:\Users\greyaliens\AppData\Roaming\Armory\" --dbdir="C:\Users\greyaliens\AppData\Roaming\Armory\databases"

Log file opened at 07:56:13.000: C:\Users\greyaliens\AppData\Roaming\Armory\dbLog.txt
-INFO  - 07:56:13.000: (e:\users\goat\code\armory3\cppforswig\main.cpp:32) Running on 8 threads
-INFO  - 07:56:13.000: (e:\users\goat\code\armory3\cppforswig\main.cpp:33) Ram usage level: 50
-INFO  - 07:56:13.000: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:915) blkfile dir: H:\Bitcoin\data\blocks
-INFO  - 07:56:13.000: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:916) lmdb dir: C:\Users\greyaliens\AppData\Roaming\Armory\databases
-INFO  - 07:56:13.000: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 07:56:13.016: (e:\users\goat\code\armory3\cppforswig\bdm_server.h:263) Listening on port
-INFO  - 07:56:15.141: (e:\users\goat\code\armory3\cppforswig\bdm_server.cpp:1121) registered bdv:
-INFO  - 07:58:35.844: (e:\users\goat\code\armory3\cppforswig\noderpc.cpp:57) RPC connection established
-INFO  - 07:58:35.844: (e:\users\goat\code\armory3\cppforswig\bitcoinp2p.cpp:947) Connected to Bitcoin node
-INFO  - 07:58:35.109: (e:\users\goat\code\armory3\cppforswig\blockdatamanagerconfig.cpp:919) waiting on node sync: 99.9851%
-INFO  - 07:58:35.109: (e:\users\goat\code\armory3\cppforswig\noderpc.cpp:425) Node is ready
-INFO  - 07:58:35.109: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:1108) Executing: doInitialSyncOnLoad
-INFO  - 07:58:36.250: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:199) Reading headers from db
-WARN  - 07:58:36.250: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:1241) No headers in DB yet!
-INFO  - 07:58:36.250: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:238) Found 1 headers in db
-INFO  - 07:58:36.250: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:71) updating HEADERS db
-INFO  - 07:58:47.313: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4
........blah blah blah.......
-INFO  - 11:46:58.172: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #531204 to #531708
-ERROR - 11:47:21.188: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:445) Missing file map for output scan, this is unexpected
-ERROR - 11:47:21.188: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:447) Has the following block files:
-ERROR - 11:47:21.188: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449)  --- #1316
-ERROR - 11:47:21.188: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449)  --- #1317
-ERROR - 11:47:21.188: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449)  --- #1318
-ERROR - 11:47:21.188: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449)  --- #1319
-ERROR - 11:47:21.188: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449)  --- #1320
-ERROR - 11:47:21.188: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449)  --- #1321
-ERROR - 11:47:21.188: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449)  --- #1322
-ERROR - 11:47:21.188: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:451) Was looking for id #1323

Yes, -reindex checks the local blockchain for blocks to rebuild the 'block index', so if any of the block is corrupted, it'll have to resync the blockchain from that point.
So I think it may just be "pathing issue" in Armory.

Since you've set that directory as "SatoshiDatadir" to Armory, check if Bitcoin Core is using that as datadir as well.
How did you set Drive H as Bitcoin datadir?
What's the exact directory did you set as Bitcoin datadir?

If you decided to browse to "H:\Bitcoin\data" folder instead, you can check if the blockchain's size is appropriate for a full-synced blockchain.
the blockchain that Armory is using is: "H:\Bitcoin\data\blocks", check the blocks folder's properties and see if the size is about 445GB.

He's pointing if your bitcoin core data is in "H:\Bitcoin\data" so manually check that folder and check the bitcoin core if it's also pointing on that location folder.

Also, take note of your PC if the time and date are correct.

If all are fine but the issue is still the same then I suggest you try pointing bitcoin data manually follow the guide from this link below
- https://www.bitcoinarmory.com/troubleshooting/#how-can-i-change-the-blockchain-database-storage-location-for-armory-and-bitcoin-core

Can you confirm that "H:\Bitcoin\data" is your Bitcoin Core's custom data directory?
Otherwise, if it's "H:\Bitcoin", then Armory's blkfile dir should be "H:\Bitcoin\blocks".
If no, then look for hardware issues specially the "H" drive before attempting to re-download the whole blockchain.
[/quote]


This from the ArmourySettings file   shows the correct pathing.
SatoshiDatadir                       | H:\Bitcoin\data
----------------------                        ----------------------
As for hardware issues, i will run drive checks on the H:  ,  but my brain suggests that any errors in the bitcoin files, should have been caught by bitcoincore during the -reindex.
Am i using correct assumptions?   

Hmm, same result even after -reindex and rebuild database   :-\

Is Armory perhaps looking for a different directory where there's an incomplete blockchain?
Specifically this:

Can you confirm that "H:\Bitcoin\data" is your Bitcoin Core's custom data directory?
Otherwise, if it's "H:\Bitcoin", then Armory's blkfile dir should be "H:\Bitcoin\blocks".
If no, then look for hardware issues specially the "H" drive before attempting to re-download the whole blockchain.

Instead of starting from scratch,
try -reindex instead, it's slower than -reindex-chainstate but a lot faster than a full resync (plus it wont cost you any bandwidth).

You mentioned that you've used -reindex-chainstate a few times but that won't find if there's any corrupted block in your blockchain
because it'll only rebuild the UTXO set from the already built block index.
[/quote]

Back on the 14th  post,  i did let bitcoincore do a -reindex
Armoury ran the full scan and rebuild of it's databases
With the exact same result.  
 
I appreciate the sugggestion, don't get me wrong.   I just want it to work  
Not 100%  convinced that a 400+gb DL and time will result in a different outcome.

Instead of starting from scratch,
try -reindex instead, it's slower than -reindex-chainstate but a lot faster than a full resync (plus it wont cost you any bandwidth).

You mentioned that you've used -reindex-chainstate a few times but that won't find if there's any corrupted block in your blockchain
because it'll only rebuild the UTXO set from the already built block index.

It seems that many users have the same issue but I can't find that they solve the issue. Bitcoin core is keep developing and releasing new versions and maybe the armory can't detect the latest version of Bitcoin core. Look the last update of Armory is 2018 and no latest update with this wallet.

So if you downgrade the Bitcoin core when taproot is not implemented yet maybe Armory will work properly. That's just my theory but you can try it.



Do you need the BTC from your wallet right away?
If you don't want too much hassle you can export your private keys from Armory(Run it offline) and then import it to Electrum. You don't need to download the whole blockchain or wait to be fully synced.

EDIT:  Begininning to think i should just let bitcoincore start from scratch.  Opinions?


  Prune mode is not in the bitcoin config file, and is unchecked in the settings console.
  The server=1  was not in the bitcoin.config, but added it in.  
i hate to say it...  same thing happens.
will try letting armoury re-do the databases again tomorrow...
and
Found this in the armourylog for this run.

-INFO  - 15:16:01.484: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #138
-INFO  - 15:16:14.734: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #146
-ERROR - 15:16:20.312: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:366) block deser except:
-ERROR - 15:16:20.312: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:367) block fileID: 128
-INFO  - 15:16:29.187: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #154
-INFO  - 15:16:42.609: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #162

-INFO  - 17:05:08.281: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #2917
-INFO  - 17:05:08.281: (e:\users\goat\code\armory3\cppforswig\blockchain.cpp:248) Organizing chain
-INFO  - 17:05:10.156: (e:\users\goat\code\armory3\cppforswig\blockchain.cpp:370) Organized chain in 1s
-INFO  - 17:05:15.156: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:76) updated HEADERS db in 6765s
-INFO  - 17:05:15.203: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 17:05:15.203: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:1231) verifying txfilters integrity
-INFO  - 17:05:21.937: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:1314) done checking txfilters
-INFO  - 17:05:21.969: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:1891) Enabling zero-conf tracking
-INFO  - 17:05:21.047: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:401) Starting address registration process
-INFO  - 17:05:33.484: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #0 to #142691
-INFO  - 17:05:45.359: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #142692 to #170004

-INFO  - 19:03:37.828: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #531204 to #531708
-ERROR - 19:03:59.094: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:445) Missing file map for output scan, this is unexpected
-ERROR - 19:03:59.094: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:447) Has the following block files:
-ERROR - 19:03:59.094: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449)  --- #1316
-ERROR - 19:03:59.094: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449)  --- #1317
-ERROR - 19:03:59.094: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449)  --- #1318
-ERROR - 19:03:59.094: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449)  --- #1319
-ERROR - 19:03:59.094: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449)  --- #1320
-ERROR - 19:03:59.094: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449)  --- #1321
-ERROR - 19:03:59.094: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:449)  --- #1322
-ERROR - 19:03:59.094: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:451) Was looking for id #1323

That doesn't seem to be the problem.
According to the Armory log that has been posted in the OP, 531708 blocks were scanned successfully.
If prune mode was enabled in bitcoin core, those blocks data wouldn't be available and Armory wouldn't be able to scan any block.