Topic: armory stuck scanning transaction history win10 new wallet (Read 67 times)

I did a rebuild and rescan and it's scanning now. It didn't have any progress status before so I think it's OK now. Thanks.

It would be easier if you presented full logs, it's hard to go off with just this. For now, the line suggests something went wrong when registering addresses with the DB, which is to say that never started scanning in the first place.

so I decided to create a new wallet with the intention of actually starting to invest in bitcoin and as i had armory installed i thought i might as well try that, but my armory is stuck scanning transaction history.

i have bitcoin core installed and its not pruned, i have the entire blockchain downloaded and bitcoin core is connected and synced up, armory did connect yesterday during the day but now its just scanning transaction history, its been doing this for like 15 hours. it was working for a bit yesterday, but since restarting armory last night at 8pm it just doesn't seem to be doing anything.

how can i tell if its crashed or actually doing something? the log files seems suspiciously quiet since yesterday when it started scanning, this is the latest output

\blockchainscanner.cpp:852) scanned from block #708666 to #708676
-INFO  - 20:09:41.844: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 20:09:41.859: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:186) scanned new blocks in 0s
-INFO  - 20:09:41.859: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:190) init db in 17s
-INFO  - 20:09:41.859: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:1891) Enabling zero-conf tracking
-INFO  - 20:09:41.906: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:401) Starting address registration process

so that log entry hasn't changed since last night.

any ideas?