I can't get armory online and I am having difficulty migrating to another platfo

[newnube]

Hi there I am having trouble syncing and bringing online armory. Additionally I have used private keys to migrate most funds. however, some still remains on armory.

I am using:
Bitcoin Core v22.0
Armory 96.5
Windows 11 64-bit
For both armory and bitcoin core The blocks are pathed to the same external harddrive (hdd)


Armory is stuck on older blocks, it finishes syncing, and it shows wallets and balances up to around 6 years ago, likely where the old block that can't be synced beyond is. It can't seem to move past that point.

I don't think my bitcoin core blocks are pruned, that option on bitcoin core client is not selected. Maybe, I did do that briefly at some point in the past, but can't remember. The node has been used on a number of computers over the years.
I have not synced armory to the point of being online in a long time
Bitcoin core syncs fully, however armory won't, and it also remains offline when bitcoin core is running prior and during armory's syncing .


I have tried some of the usual fixes, found here on this forum:

Deleting armory data bases and running bitcoin core synced and then allowing armory to rebuild it's database in the usual place C:\Users\[Your Username\AppData\Roaming\Armory\databases

I don't think there is a compatibility issue with the blockchain, since I am running an old bitcoin core v22 (Which may be an issue security wise, however my wallets are on armory and not bitcoin core).
However, the log files are throwing out 'POLLERR error in readAndWrite' and 'FcgiSocket::writeAndRead FcgiError: unknown fcgi header request byte' .  So, I guess my antivirus may be causing problems, maybe a port conflict on 9001?





I have migrated most of my funds to another platform, by exporting private keys and then sending to a separate secured platform . Sadly this does not work for all my armory wallets. One address won't show any balance in it's corresponding private keys, on the platform used to migrate. However, on mempool.space , the public key still shows the up-to-date balance as it should be, that gives me hope that I haven't been compromised?
The address that won't migrate is a change received address on a segregated witness transaction. The change I received is an address type different from the usual public address, starting with a 3 rather than a 1.
My hope is, that since my armory is not fully synced, it is not producing the correct corresponding private key for the public address beginning with 3? But, I don't know why the private key would change if synced and online. (Note; I don't check the private keys while online).

I looked at the export of private keys in armory and tried the private base58 relating to the public key with that up-to-date balance. I also tried unused keys (omitting spaces). Nothing shows any value when imported to the migratory platform.

Is my only option to get armory to sync fully and hopefully the balance is there and I can then send the funds through armory with it's correctly generated private? Or have I potentially lost the funds that for whatever reason has nothing in its corresponding base58? I tried adding the prepend of p2wpkh-p2sh: ... In the migratory platform, I get told: 'invalid private key: only compressed public keys can be used with segwit scripts'.
No desired result using the other two prepends either.


I have not tried the rescan, rebuild or factory reset options in the armoury client.





My main concern is retrieving the funds. Ideally through it's private key.

Or syncing armory correctely to send that way, if the funds are there. If so how do I go about that (sorry, my tech savvyness is not good, slightly above average 🫩). If going with this option, what version of core should I use? I will use an external SSD rather than HDD, if resyncing the Blockchain, or maybe I should use ssd anyway?


Any advice would be much appreciated.

Thanks all for your time.







Some exerts from the log file is as follows, if more or full is required let me know:

...
Log file opened at 19:53:20.000: C:\Users\usele\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 20:37:02.000: (e:\users\goat\code\armory3\cppforswig\socketobject.cpp:447) POLLERR error in readAndWrite
-ERROR - 20:37:02.000: (e:\users\goat\code\armory3\cppforswig\stringsockets.cpp:359) POLLERR error in readAndWrite
-ERROR - 00:13:36.031: (e:\users\goat\code\armory3\cppforswig\stringsockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unknown fcgi header request byte


Log file opened at 20:19:47.000: C:\Users\usele\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 04:00:57.391: (e:\users\goat\code\armory3\cppforswig\socketobject.cpp:447) POLLERR error in readAndWrite
-ERROR - 04:00:57.391: (e:\users\goat\code\armo...


...ta\Roaming\Armory\armorycpplog.txt


Log file opened at 14:54:07.000: C:\Users\usele\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 15:23:53.829: (e:\users\goat\code\armory3\cppforswig\socketobject.cpp:447) POLLERR error in readAndWrite
-ERROR - 15:23:53.844: (e:\users\goat\code\armory3\cppforswig\stringsockets.cpp:359) POLLERR error in readAndWrite


Log file opened at 06:43:02.000: C:\Users\usele\AppData\Roaming\Armory\armorycpplog.txt
-ERROR - 08:41:16.828: (e:\users\goat\code\armory3\cppforswig\socketobject.cpp:447) POLLERR error in readAndWrite
-ERROR - 08:41:16.828: (e:\users\goat\code\armory3\cppforswig\stringsockets.cpp:359) POLLERR error in readAndWrite


Log file opened at 09:10:43.000: C:\Users\usele\AppData\Roaming\Armory\armorycpplog.txt...


...Log file opened at 13:05:24.000: C:\Users\usele\AppData\Roaming\Armory\dbLog.txt
-INFO  - 13:05:24.000: (e:\users\goat\code\armory3\cppforswig\main.cpp:32) Running on 8 threads
-INFO  - 13:05:24.000: (e:\users\goat\code\armory3\cppforswig\main.cpp:33) Ram usage level: 50
-INFO  - 13:05:24.000: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:915) blkfile dir: D:\arm\Bitcoin\blocks
-INFO  - 13:05:24.000: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:916) lmdb dir: C:\Users\usele\AppData\Roaming\Armory\databases
-INFO  - 13:05:24.000: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 13:05:24.110: (e:\users\goat\code\armory3\cppforswig\bdm_server.h:263) Listening on port 62386
-INFO  - 13:05:26.172: (e:\users\goat\code\armory3\cppforswig\bdm_server.cpp:1121) registered bdv: 7878326c7176b5671e52
-INFO  - 13:05:28.188: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:1108) Executing: doInitialSyncOnLoad
-INFO  - 13:05:39.891: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:199) Reading headers from db
-INFO  - 13:05:44.500: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:238) Found 860046 headers in db
-INFO  - 13:05:45.422: (e:\users\goat\code\armory3\cppforswig\bitcoinp2p.cpp:947) Connected to Bitcoin node
-INFO  - 13:05:47.266: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:64) Rewinding 100 blocks
-INFO  - 13:05:47.266: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:71) updating HEADERS db
-INFO  - 13:05:50.141: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:493) Found next block after skipping 1630196bytes
-INFO  - 13:06:41.657: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4584
-ERROR - 13:06:46.407: (e:\users\goat\code\armory3\cppforswig\bitcoinp2p.cpp:1037) caught StopBlockingLoop in processDataStackThread
-INFO  - 13:06:46.407: (e:\users\goat\code\armory3\cppforswig\bitcoinp2p.cpp:969) Disconnected from Bitcoin node
-INFO  - 13:06:48.782: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4588
-INFO  - 13:07:22.328: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4589
-INFO  - 13:07:56.907: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4592
-INFO  - 13:08:20.719: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4596
-ERROR - 13:08:40.797: (e:\users\goat\code\armory3\cppforswig\socketobject.cpp:290) POLLERR error in readFromSocketThread
-ERROR - 13:08:40.797: (e:\users\goat\code\armory3\cppforswig\bitcoinp2p.cpp:1027) caught SocketError exception in processDataStackThread: POLLERR error in readFromSocketThread
-INFO  - 13:09:07.828: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #4597...




...e #5691
-INFO  - 16:21:04.594: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #5692
-INFO  - 16:22:25.141: (e:\users\goat\code\armory3\cppforswig\blockchain.cpp:248) Organizing chain
-INFO  - 18:18:15.735: (e:\users\goat\code\armory3\cppforswig\blockchain.cpp:370) Organized chain in 6949s
-INFO  - 18:18:15.750: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:76) updated HEADERS db in 18747s
-INFO  - 18:18:15.782: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 18:18:15.797: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:1231) verifying txfilters integrity
-INFO  - 18:18:17.375: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:1256) no recorded block headers in file #1076...




...le #1177
-INFO  - 18:18:17.375: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:1257) skipping
-INFO  - 18:18:17.375: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:1256) no recorded block headers in file #1178
-INFO  - 18:18:17.375: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:1257) skipping
-INFO  - 18:18:25.578: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:1314) done checking txfilters
-INFO  - 18:18:25.610: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:1891) Enabling zero-conf tracking
-INFO  - 20:14:38.125: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:401) Starting address registration process
-INFO  - 20:14:47.500: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #0 to #142691
-INFO  - 20:14:55.500: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #142692 to #170004...





...59261 to #859581
-INFO  - 20:33:58.453: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #859582 to #859891
-INFO  - 20:34:36.344: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #859892 to #860035
-INFO  - 20:34:36.469: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:214) scanned transaction history in 87598s
-INFO  - 20:34:39.250: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:1789) resolving txhashes
-INFO  - 20:34:51.297: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:1848) 24 blocks hit by tx filters
-INFO  - 20:34:55.000: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:1937) found 20 missing hashes
-INFO  - 20:34:55.016: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:1982) Resolved missing hashes in 15s
-INFO  - 20:34:55.078: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:857) scanned block #860035

[goatpig]

-INFO  - 18:18:15.735: (e:\users\goat\code\armory3\cppforswig\blockchain.cpp:370) Organized chain in 6949s

...

-INFO  - 20:34:55.078: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:857) scanned block #860035

Something looks very wrong with your blockchain data. Organizing chain should take ~60sec at most, even on old hardware. Your top block is over 100k behind current top.

Whether you resync the chain or not (SSD is preferable at any rate), try the release candidate for the new version first: https://github.com/goatpig/BitcoinArmory/releases

[newnube]

thanks

Yea I am not sure what went wrong.



I am getting somewhere with the migration. I think I need to sweep rather than import wit the correct prepend for the address beginning with 3.



If that doesn't work I will try the new version. And then maybe a rebuild 😣.



Thanks again for all the support over the years. I am glad to see this is all still going.

[goatpig]

Make sure to cleanup your armory databases folder before switching to the new version