Bitcoin Forum

Bitcoin => Armory => Topic started by: micha445 on December 27, 2020, 07:09:51 AM



Title: problems with armory / How to move Armory wallet to another program?
Post by: micha445 on December 27, 2020, 07:09:51 AM
I have finally enough. I need a Full node wallet that works if I spin it up.

I have a few wallets in Armory. How can I use/move/export this to the regular bitcoin client?


Title: Re: Amory is not production ready / How to move Armory wallet to another program?
Post by: nc50lc on December 27, 2020, 07:38:43 AM
Is Armory working (just acting up)? Then the best solution is to simply send the funds to Bitcoin Core through a transaction.

Next option is to Import the private keys to Bitcoin core through core's console/command line using importprivkey (how to use (https://bitcoincore.org/en/doc/0.18.0/rpc/wallet/importprivkey/)).
You can get the address' private keys in Armory's "Wallet Properties->Backup This Wallet->See other Backup Options".
Here's an 'export from Armory' guide with pictures by HCP: https://bitcointalk.org/index.php?topic=4746784.msg43255691#msg43255691 (https://bitcointalk.org/index.php?topic=4746784.msg43255691#msg43255691)


Title: Re: Amory is not production ready / How to move Armory wallet to another program?
Post by: micha445 on December 27, 2020, 10:39:46 AM
Is Armory working (just acting up)? Then the best solution is to simply send the funds to Bitcoin Core through a transaction.

Next option is to Import the private keys to Bitcoin core through core's console/command line using importprivkey (how to use (https://bitcoincore.org/en/doc/0.18.0/rpc/wallet/importprivkey/)).
You can get the address' private keys in Armory's "Wallet Properties->Backup This Wallet->See other Backup Options".
Here's an 'export from Armory' guide with pictures by HCP: https://bitcointalk.org/index.php?topic=4746784.msg43255691#msg43255691 (https://bitcointalk.org/index.php?topic=4746784.msg43255691#msg43255691)

No. It is not working. But it will be not working the last time. Next time I get it to work I am done and move the coins to another client.

I am stuck at scanning transaction history forever.

I mean, this few times Armory worked after spin up, I can count on one hand. This wallet is a joke, potentially dangerous. I have enough.


Title: Re: Amory is not production ready / How to move Armory wallet to another program?
Post by: nc50lc on December 27, 2020, 11:10:14 AM
-snip-
No. It is not working. But it will be not working the last time. Next time I get it to work I am done and move the coins to another client.

I am stuck at scanning transaction history forever.

I mean, this few times Armory worked after spin up, I can count on one hand. This wallet is a joke, potentially dangerous. I have enough.
O...kay.. If it worked just recently then I assume that your wallets have saved the latest transactions.
So just do "HCP's export tutorial" link in my post and import the WIF (base58) private keys of addresses with balance to Bitcoin Core
(if the "standard client" is what you mean by "regular client").

You can also share the armorylog.txt from the datadir so the developer could see the actual issue.


Title: Re: Amory is not production ready / How to move Armory wallet to another program?
Post by: micha445 on December 27, 2020, 05:28:38 PM
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1164 - C++ block utilities loaded successfully
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:689 - Executing popen: free -m
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:689 - Executing popen: ['cat', '/proc/cpuinfo']
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1281 -
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1282 -
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1283 -
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1284 - ************************************************************
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1285 - Invoked: /usr/bin/../lib/armory/ArmoryQt.py
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1286 - ************************************************************
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1287 - Loading Armory Engine:
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1288 -    Armory Version        : 0.96.5
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1289 -    Armory Build:         : 1d02a6640d
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1290 -    PyBtcWallet  Version  : 1.35
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1291 - Detected Operating system: Linux
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1292 -    OS Variant            : Ubuntu-18.04-bionic
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1293 -    User home-directory   : /home/user
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1294 -    Satoshi BTC directory : /home/user/.bitcoin
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1295 -    Armory home dir       : /home/user/.armory/
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1296 - Detected System Specs    :
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1297 -    Total Available RAM   : 31.43 GB
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1298 -    CPU ID string         : AMD Ryzen 7 1700 Eight-Core Processor
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1299 -    Number of CPU cores   : 16 cores
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1300 -    System is 64-bit      : True
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1301 -    Preferred Encoding    : UTF-8
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1302 -    Machine Arch          : x86_64
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1303 -    Available HDD (ARM)   : 19 GB
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1304 -    Available HDD (BTC)   : 19 GB
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1305 -
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1306 - Network Name: Main Network
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1307 - Satoshi Port: 8333
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1308 - Do wlt check: True
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1309 - Named options/arguments to armoryengine.py:
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     force_segwit    : False
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     nettimeout      : 2
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     rescan          : False
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     force_fcgi      : False
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     ignoreAllZC     : False
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     rescanBalance   : False
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     disableModules  : False
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     port            : None
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     interport       : 8223
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     coverageOutputDir: None
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     forceWalletCheck: False
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     regtest         : False
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     rebuild         : False
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     thread_count    : -1
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     datadir         : DEFAULT
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     clearMempool    : False
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     offline         : False
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     armoryDBDir     : DEFAULT
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     armorydb_port   : 9001
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     satoshiPort     : DEFAULT
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     disableConfPermis: False
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     useTorSettings  : False
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     netlog          : False
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     keypool         : 100
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     coverageInclude : None
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     forceOnline     : False
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     disableWalletCheck: False
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     redownload      : False
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     rpcBindAddr     : 127.0.0.1
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     armorydb_ip     : 127.0.0.1
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     multisigFile    : DEFAULT
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     ram_usage       : -1
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     ignoreZC        : False
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     logDisable      : False
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     settingsPath    : /home/user/.armory/ArmorySettings.txt
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     language        : en
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     db_type         : DB_FULL
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     doDebug         : False
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     enableDetSign   : True
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     mtdebug         : False
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     testnet         : False
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     rpcport         : DEFAULT
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     satoshiHome     : DEFAULT
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     satoshiRpcport  : DEFAULT
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     logFile         : /home/user/.armory/ArmoryQt.py.log.txt
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1311 -     verbosity       : None
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1312 - Other arguments:
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1315 - ************************************************************
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:1720 - C++ block utilities loaded successfully
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:3578 - Using settings file: /home/user/.armory/ArmorySettings.txt
2020-12-27 17:06:14 (ERROR) -- ArmoryUtils.py:3735 - Unsupported language  specified. Defaulting to English (en)
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:3738 - Using Language: en
2020-12-27 17:06:14 (INFO) -- BDM.py:353 - Using the asynchronous/multi-threaded BlockDataManager.
2020-12-27 17:06:14 (INFO) -- BDM.py:354 - Blockchain operations will happen in the background.  
2020-12-27 17:06:14 (INFO) -- BDM.py:355 - Devs: check TheBDM.getState() before asking for data.
2020-12-27 17:06:14 (INFO) -- BDM.py:356 - Registering addresses during rescans will queue them for
2020-12-27 17:06:14 (INFO) -- BDM.py:357 - inclusion after the current scan is completed.
2020-12-27 17:06:14 (INFO) -- ArmoryUtils.py:3578 - Using settings file: /home/user/.armory/ArmorySettings.txt
2020-12-27 17:06:14 (INFO) -- ArmoryQt.py:2060 - loadWalletsAndSettings
2020-12-27 17:06:14 (INFO) -- ArmoryQt.py:2120 - Loading wallets...
2020-12-27 17:06:15 (WARNING) -- ArmoryQt.py:2147 - ***WARNING: Duplicate wallet detected, XXXX
2020-12-27 17:06:15 (WARNING) -- ArmoryQt.py:2158 - Second wallet is more useful than the first one...
2020-12-27 17:06:15 (WARNING) -- ArmoryQt.py:2159 -      Wallet 1 (skipped): /home/user/.armory/armory_XXXXX_.wallet
2020-12-27 17:06:15 (WARNING) -- ArmoryQt.py:2160 -      Wallet 2 (loaded):  /home/user/.armory/armory_XXXX_decrypt.wallet
2020-12-27 17:06:15 (INFO) -- ArmoryQt.py:2185 - Number of wallets read in: 3
2020-12-27 17:06:15 (INFO) -- ArmoryQt.py:2190 -    Wallet (GHxxxxx):    "Test Wallet                     "   (No Encryption)
2020-12-27 17:06:15 (INFO) -- ArmoryQt.py:2190 -    Wallet (xxxxxxcT9):   "user                             "   (Encrypted)
2020-12-27 17:06:15 (INFO) -- ArmoryQt.py:2190 -    Wallet (xxxxxxZZ):    "Tate                           "   (Encrypted)
2020-12-27 17:06:15 (INFO) -- ArmoryQt.py:2195 - Loading Multisig Lockboxes
2020-12-27 17:06:15 (INFO) -- ArmoryQt.py:1763 - acquiring process mutex...
2020-12-27 17:06:15 (INFO) -- ArmoryQt.py:1395 - setupUriRegistration
2020-12-27 17:06:15 (INFO) -- ArmoryUtils.py:689 - Executing popen: gconftool-2 --get /desktop/gnome/url-handlers/bitcoin/command
2020-12-27 17:06:15 (INFO) -- ArmoryUtils.py:689 - Executing popen: xdg-mime query default x-scheme-handler/bitcoin
2020-12-27 17:06:15 (INFO) -- ArmoryQt.py:566 - Usermode: Expert
2020-12-27 17:06:15 (INFO) -- ArmoryQt.py:1698 - Changing usermode:
2020-12-27 17:06:15 (INFO) -- ArmoryQt.py:1699 -    From: Expert
2020-12-27 17:06:15 (INFO) -- ArmoryQt.py:1707 -      To: Expert
2020-12-27 17:06:15 (INFO) -- ArmoryQt.py:1836 - startBitcoindIfNecessary
2020-12-27 17:06:15 (INFO) -- ArmoryQt.py:1872 - setSatoshiPaths
2020-12-27 17:06:15 (INFO) -- ArmoryQt.py:1891 - Setting satoshi datadir = /media/user/SDSDSDSDS/bit
2020-12-27 17:06:15 (INFO) -- ArmoryUtils.py:689 - Executing popen: ['whereis', 'bitcoind']
2020-12-27 17:06:15 (INFO) -- SDM.py:292 - "whereis" returned: ['/usr/bin/bitcoind']
2020-12-27 17:06:15 (INFO) -- SDM.py:171 - Found bitcoind in the following places:
2020-12-27 17:06:15 (INFO) -- SDM.py:173 -    /usr/bin/bitcoind
2020-12-27 17:06:15 (INFO) -- SDM.py:173 -    /usr/bin/bitcoind
2020-12-27 17:06:15 (INFO) -- SDM.py:173 -    /usr/bin/bitcoind
2020-12-27 17:06:15 (INFO) -- SDM.py:175 - Using: /usr/bin/bitcoind
2020-12-27 17:06:15 (INFO) -- SDM.py:340 - Called startBitcoind
2020-12-27 17:06:15 (WARNING) -- SDM.py:445 - Spawning bitcoind with command: /usr/bin/bitcoind -datadir=/media/user/sdsdsdsd/bit
2020-12-27 17:06:15 (INFO) -- ArmoryUtils.py:689 - Executing popen: [u'/usr/bin/bitcoind', '-datadir=/media/user/sdsdsdsd/bit']
2020-12-27 17:06:15 (INFO) -- SDM.py:451 - PID of bitcoind: 15605
2020-12-27 17:06:15 (INFO) -- SDM.py:452 - PID of armory:   15566
2020-12-27 17:06:15 (INFO) -- ArmoryUtils.py:689 - Executing popen: ['python', '/usr/lib/armory/guardian.py', '15566', '15605']
2020-12-27 17:06:15 (INFO) -- ArmoryQt.py:1872 - setSatoshiPaths
2020-12-27 17:06:15 (INFO) -- ArmoryQt.py:1891 - Setting satoshi datadir = /media/user/sdsdsdsd/bit
2020-12-27 17:06:15 (WARNING) -- SDM.py:402 - Spawning DB with command: ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/media/user/sdsdsdsd/bit/blocks" --satoshi-port=8333 --datadir="/home/user/.armory/" --dbdir="/home/user/.armory/databases"
2020-12-27 17:06:15 (INFO) -- ArmoryUtils.py:689 - Executing popen: ['ArmoryDB', '--db-type="DB_FULL"', '--cookie', '--satoshi-datadir="/media/user/sdsdsdsd/bit/blocks"', '--satoshi-port=8333', '--datadir="/home/user/.armory/"', '--dbdir="/home/user/.armory/databases"']
2020-12-27 17:06:15 (INFO) -- ArmoryQt.py:1824 - Connecting on port 63243
2020-12-27 17:06:15 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 1
2020-12-27 17:06:15 (INFO) -- ArmoryQt.py:1905 - loadBlockchainIfNecessary
2020-12-27 17:06:15 (ERROR) -- ArmoryQt.py:1198 - 14 attempts to load blockchain failed.  Remove mempool.bin.
2020-12-27 17:06:15 (ERROR) -- ArmoryQt.py:1203 - File mempool.bin does not exist. Nothing deleted.
2020-12-27 17:06:15 (INFO) -- ArmoryQt.py:1923 - Setting netmode: 1
2020-12-27 17:06:15 (INFO) -- ArmoryQt.py:4672 - Dashboard switched to "Scanning" mode

The last line is repeated a few 100 times


Title: Re: Amory is not production ready / How to move Armory wallet to another program?
Post by: micha445 on December 27, 2020, 11:08:43 PM
Please? Anyone? This is urgent? How to get Armory running again. What is the problem?

Thanks a lot.


Title: Re: Amory is not production ready / How to move Armory wallet to another program?
Post by: goatpig on December 28, 2020, 12:01:47 AM
There is something stopping ArmoryQt from connecting to ArmoryDB, probably a port conflict. You should start ArmoryDB manually then start ArmoryQt, see how that goes.


Title: Re: Amory is not production ready / How to move Armory wallet to another program?
Post by: micha445 on December 29, 2020, 01:21:53 AM
FO  - 02:03:35: (lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 02:03:35: (BDM_Server.h:263) Listening on port 9001
-INFO  - 02:03:35: (BlockUtils.cpp:1108) Executing: doInitialSyncOnLoad
-INFO  - 02:03:35: (DatabaseBuilder.cpp:199) Reading headers from db
-INFO  - 02:03:40: (DatabaseBuilder.cpp:238) Found 663421 headers in db
-INFO  - 02:03:43: (DatabaseBuilder.cpp:64) Rewinding 100 blocks
-INFO  - 02:03:43: (DatabaseBuilder.cpp:71) updating HEADERS db
-INFO  - 02:03:43: (Blockchain.cpp:248) Organizing chain
-INFO  - 02:03:43: (Blockchain.cpp:370) Organized chain in 0s
-INFO  - 02:03:43: (DatabaseBuilder.cpp:76) updated HEADERS db in 0s
-INFO  - 02:03:43: (lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 02:03:43: (DatabaseBuilder.cpp:1231) verifying txfilters integrity
-INFO  - 02:03:51: (DatabaseBuilder.cpp:1314) done checking txfilters
-INFO  - 02:03:51: (DatabaseBuilder.cpp:134) scanning new blocks from #663421 to #663420
-INFO  - 02:03:51: (BlockchainScanner.cpp:52) no history to scan
-INFO  - 02:03:51: (BlockchainScanner.cpp:1021) no SSH to scan
-INFO  - 02:03:51: (lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 02:03:51: (DatabaseBuilder.cpp:186) scanned new blocks in 0s
-INFO  - 02:03:51: (DatabaseBuilder.cpp:190) init db in 16s
-INFO  - 02:03:51: (BDM_supportClasses.cpp:1891) Enabling zero-conf tracking


Title: Re: Amory is not production ready / How to move Armory wallet to another program?
Post by: HCP on December 30, 2020, 03:01:06 AM
Just posting snippets of debug output doesn't exactly help without some context.  :-\

What exactly have you tried when you got that output? Is that just the output from running ArmoryDB.exe manually? ??? What happened when you tried to run ArmoryQT? Did it start at all? ???


Title: Re: Amory is not production ready / How to move Armory wallet to another program?
Post by: BitMaxz on December 30, 2020, 03:42:35 PM
Have you tried to check if bitcoin core is fully synced?
Armory wallet won't work if the bitcoin core is not fully synced you must run the bitcoin core first and let it sync for a while until fully synced.

Once it's done open the armory again and transfer your bitcoin to another wallet or backup the private key.


Title: Re: Amory is not production ready / How to move Armory wallet to another program?
Post by: micha445 on December 30, 2020, 10:52:28 PM
Have you tried to check if bitcoin core is fully synced?
Armory wallet won't work if the bitcoin core is not fully synced you must run the bitcoin core first and let it sync for a while until fully synced.

Once it's done open the armory again and transfer your bitcoin to another wallet or backup the private key.

Yes, I run bitcoin first to sync.



Title: Re: Amory is not production ready / How to move Armory wallet to another program?
Post by: micha445 on December 31, 2020, 09:08:28 AM
Just posting snippets of debug output doesn't exactly help without some context.  :-\

What exactly have you tried when you got that output? Is that just the output from running ArmoryDB.exe manually? ??? What happened when you tried to run ArmoryQT? Did it start at all? ???

So, I am back. Was busy. Had to update to 18.10 und armory was not spinning up at all anymore. Now it is and I still have the old problem.

My armory is not running. Based on the error log I was advised:
    
"There is something stopping ArmoryQt from connecting to ArmoryDB, probably a port conflict. You should start ArmoryDB manually then start ArmoryQt, see how that goes."

Hence I started the armorydb from the shell and this was the output I got.


Title: Re: Amory is not production ready / How to move Armory wallet to another program?
Post by: goatpig on December 31, 2020, 10:32:44 AM
FO  - 02:03:35: (lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 02:03:35: (BDM_Server.h:263) Listening on port 9001
-INFO  - 02:03:35: (BlockUtils.cpp:1108) Executing: doInitialSyncOnLoad
-INFO  - 02:03:35: (DatabaseBuilder.cpp:199) Reading headers from db
-INFO  - 02:03:40: (DatabaseBuilder.cpp:238) Found 663421 headers in db
-INFO  - 02:03:43: (DatabaseBuilder.cpp:64) Rewinding 100 blocks
-INFO  - 02:03:43: (DatabaseBuilder.cpp:71) updating HEADERS db
-INFO  - 02:03:43: (Blockchain.cpp:248) Organizing chain
-INFO  - 02:03:43: (Blockchain.cpp:370) Organized chain in 0s
-INFO  - 02:03:43: (DatabaseBuilder.cpp:76) updated HEADERS db in 0s
-INFO  - 02:03:43: (lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 02:03:43: (DatabaseBuilder.cpp:1231) verifying txfilters integrity
-INFO  - 02:03:51: (DatabaseBuilder.cpp:1314) done checking txfilters
-INFO  - 02:03:51: (DatabaseBuilder.cpp:134) scanning new blocks from #663421 to #663420
-INFO  - 02:03:51: (BlockchainScanner.cpp:52) no history to scan
-INFO  - 02:03:51: (BlockchainScanner.cpp:1021) no SSH to scan
-INFO  - 02:03:51: (lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 02:03:51: (DatabaseBuilder.cpp:186) scanned new blocks in 0s
-INFO  - 02:03:51: (DatabaseBuilder.cpp:190) init db in 16s
-INFO  - 02:03:51: (BDM_supportClasses.cpp:1891) Enabling zero-conf tracking


From this snippet, ArmoryDB is up and running fine, what you need is for ArmoryQt to connect to it. This typically happens as is when you just start it. Please run ArmoryQt from the terminal while ArmoryDB is running and report the result here. Full logs are preferred, as mentioned earlier.


Title: Re: Amory is not production ready / How to move Armory wallet to another program?
Post by: micha445 on January 22, 2021, 09:10:09 PM
FO  - 02:03:35: (lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 02:03:35: (BDM_Server.h:263) Listening on port 9001
-INFO  - 02:03:35: (BlockUtils.cpp:1108) Executing: doInitialSyncOnLoad
-INFO  - 02:03:35: (DatabaseBuilder.cpp:199) Reading headers from db
-INFO  - 02:03:40: (DatabaseBuilder.cpp:238) Found 663421 headers in db
-INFO  - 02:03:43: (DatabaseBuilder.cpp:64) Rewinding 100 blocks
-INFO  - 02:03:43: (DatabaseBuilder.cpp:71) updating HEADERS db
-INFO  - 02:03:43: (Blockchain.cpp:248) Organizing chain
-INFO  - 02:03:43: (Blockchain.cpp:370) Organized chain in 0s
-INFO  - 02:03:43: (DatabaseBuilder.cpp:76) updated HEADERS db in 0s
-INFO  - 02:03:43: (lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 02:03:43: (DatabaseBuilder.cpp:1231) verifying txfilters integrity
-INFO  - 02:03:51: (DatabaseBuilder.cpp:1314) done checking txfilters
-INFO  - 02:03:51: (DatabaseBuilder.cpp:134) scanning new blocks from #663421 to #663420
-INFO  - 02:03:51: (BlockchainScanner.cpp:52) no history to scan
-INFO  - 02:03:51: (BlockchainScanner.cpp:1021) no SSH to scan
-INFO  - 02:03:51: (lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 02:03:51: (DatabaseBuilder.cpp:186) scanned new blocks in 0s
-INFO  - 02:03:51: (DatabaseBuilder.cpp:190) init db in 16s
-INFO  - 02:03:51: (BDM_supportClasses.cpp:1891) Enabling zero-conf tracking


From this snippet, ArmoryDB is up and running fine, what you need is for ArmoryQt to connect to it. This typically happens as is when you just start it. Please run ArmoryQt from the terminal while ArmoryDB is running and report the result here. Full logs are preferred, as mentioned earlier.

Jesus. I just updated to Ubuntu 20.04, hoping that this might fix my problems.
No I cant even install armory. python-qt4 is not available and no installation candidate.

What is the last ubuntu version where I can get armory to work? What a nightmare


Appreciate help from anyone. I am getting desperate with this.


Title: Re: Amory is not production ready / How to move Armory wallet to another program?
Post by: HCP on January 23, 2021, 02:34:53 AM
Appreciate help from anyone. I am getting desperate with this.
At this point... it's time to ask... do you want to continue using Armory or are you just wanting to "rescue" funds? ???

If you just want the funds out... you'd be better of exporting your private keys and then importing them into a lightweight wallet of your choice (I would recommend Electrum). You can follow the guide here to get private keys: https://bitcointalk.org/index.php?topic=4746784.msg43255691#msg43255691


If you want to continue using Armory, then we can work on getting it up and running... I personally have had it running on an Ubuntu 18.04 instance... but my daily driver is on Windows 10.


Title: Re: Amory is not production ready / How to move Armory wallet to another program?
Post by: micha445 on January 23, 2021, 10:52:30 AM
I would like to keep using it. This is the shell output on my Desktop. It is still running there.

(base) user@computer:~$ armory
/home/user
(ERROR) ArmoryUtils.py:3735 - Unsupported language  specified. Defaulting to English (en)
/usr/lib/armory/armoryengine/Transaction.py:3126: SyntaxWarning: import * only allowed at module level
  def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
(WARNING) ArmoryQt.py:2147 - ***WARNING: Duplicate wallet detected, asA44pFAf
(WARNING) ArmoryQt.py:2158 - Second wallet is more useful than the first one...
(WARNING) ArmoryQt.py:2159 -      Wallet 1 (skipped): /home/user/.armory/armory_asA44pFAf_.wallet
(WARNING) ArmoryQt.py:2160 -      Wallet 2 (loaded):  /home/user/.armory/armory_asA44pFAf_decrypt.wallet
(WARNING) SDM.py:445 - Spawning bitcoind with command: /usr/bin/bitcoind -datadir=/media/user/hdd/bit
(WARNING) SDM.py:402 - Spawning DB with command: ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/media/user/hdd/bit/blocks" --satoshi-port=8333 --datadir="/home/user/.armory/" --dbdir="/home/user/.armory/databases"
(ERROR) ArmoryQt.py:1198 - 24 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:1203 - File mempool.bin does not exist. Nothing deleted.
-ERROR - : (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version


When will you upgrade the qt library? I think armory should run under Ubuntu 20.04. This is the current LTS Version
 


Title: Re: Amory is not production ready / How to move Armory wallet to another program?
Post by: goatpig on January 23, 2021, 03:59:00 PM
Still working on the migration to qt5.


Title: Re: Amory is not production ready / How to move Armory wallet to another program?
Post by: micha445 on January 23, 2021, 08:17:19 PM
Still working on the migration to qt5.

Any ETA?  :o


Title: Re: Amory is not production ready / How to move Armory wallet to another program?
Post by: goatpig on January 23, 2021, 10:01:02 PM
Still working on the migration to qt5.

Any ETA?  :o

Im not good with ETAs, don't ask. Soon (TM)


Title: Re: Amory is not production ready / How to move Armory wallet to another program?
Post by: micha445 on January 25, 2021, 12:02:36 AM
I have to many problems with Ubuntu 20.04 (e.g. getting fcitx to work). I will downgrade to 18.04.

Still hope to get Armory back to work.


Title: Re: Amory is not production ready / How to move Armory wallet to another program?
Post by: micha445 on April 01, 2021, 08:55:41 AM
oK, I was travelling and hence silent.

I donwgraded to ubuntu 18.04 und Armory still does not run.

"Unknownd fcgi header request by byte."

I am extremely worried Armory seems to be extraordinary fragile and hard to get running again. Any advice?


Title: Re: problems with armory / How to move Armory wallet to another program?
Post by: goatpig on April 01, 2021, 02:35:12 PM
Quote
There is something else listening on the port armory is trying to use.


Title: Re: problems with armory / How to move Armory wallet to another program?
Post by: HCP on April 02, 2021, 01:45:36 AM
As Goatpig has mentioned, there is another process that is using the port that Armory is trying to use for communcation.

You'll either have to kill or remove this process... or see if you can get Armory to use a different one. To see what is using the port number, try using:
Code:
sudo ss -tulpn

(or maybe
Code:
netstat -tulpn
)

from the terminal and see what process is using the Armory port.