Bitcoin Forum>Bitcoin>Development & Technical Discussion>Wallet software>Armory
Pages:
Author

Topic: Cannot start Armory on Linux Debian, stuck on "Preparing Databases" (Read 1024 times)

goatpig
legendary
Activity: 3640
Merit: 1345
Armory Developer
Cannot start Armory on Linux Debian, stuck on "Preparing Databases"
July 09, 2017, 09:48:16 AM
#25
Quote
But is it just me? I can't believe I'm having this weird errors, I don't have any strange configuration, I'm just trying to run "normally" armory on Debian... is it such an unpopular thing?

You are getting outright crashes, you should build the binaries against your actual hardware, that would at least isolate the issue somewhat. If it persist, you can then debug build and show me the traceback of the actual crash.
gaglia
newbie
Activity: 28
Merit: 0
Re: Cannot start Armory on Linux Debian, stuck on "Preparing Databases"
July 09, 2017, 09:23:44 AM
#24
I've deleted again the "databases" folder, and now I'm running ArmoryDB again.
gaglia
newbie
Activity: 28
Merit: 0
Re: Cannot start Armory on Linux Debian, stuck on "Preparing Databases"
July 09, 2017, 08:48:40 AM
#23
There is an update. I think either some corruption of the database or a bug in the build.

I gave another try. This time I did not start bitcoind, and I also closed all other applications running. So I run ArmoryDB (with no options) and on the terminal I see this:

Code:
gaglia@myhost:~$ ArmoryDB
/home/gaglia
/home/gaglia
logging in /home/gaglia/.armory/dbLog.txt
-INFO  - 13:52:35: (main.cpp:32) Running on 4 threads
-INFO  - 13:52:35: (main.cpp:33) Ram usage level: 4
-INFO  - 13:52:35: (BlockUtils.cpp:908) blkfile dir: /home/gaglia/.bitcoin/blocks
-INFO  - 13:52:35: (BlockUtils.cpp:909) lmdb dir: /home/gaglia/.armory/databases
-INFO  - 13:52:35: (lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 13:52:36: (BDM_Server.h:249) Listening on port 9001
-INFO  - 13:52:36: (BlockUtils.cpp:1092) Executing: doInitialSyncOnLoad
-INFO  - 13:52:36: (DatabaseBuilder.cpp:190) Reading headers from db
-INFO  - 13:53:07: (DatabaseBuilder.cpp:229) Found 474952 headers in db
-INFO  - 13:53:09: (DatabaseBuilder.cpp:63) Rewinding 100 blocks
-INFO  - 13:53:09: (DatabaseBuilder.cpp:70) updating HEADERS db
-INFO  - 13:53:14: (DatabaseBuilder.cpp:482) Found next block after skipping 998187bytes
-INFO  - 13:53:17: (DatabaseBuilder.cpp:272) parsed block file #888
-INFO  - 13:53:17: (Blockchain.cpp:246) Organizing chain 
-INFO  - 13:53:18: (Blockchain.cpp:360) Organized chain in 0.033253s
-INFO  - 13:53:18: (DatabaseBuilder.cpp:75) updated HEADERS db in 1.04113s
-INFO  - 13:53:18: (DatabaseBuilder.cpp:1121) verifying txfilters integrity
-INFO  - 13:54:06: (DatabaseBuilder.cpp:1205) done checking txfilters
-INFO  - 13:54:06: (BDM_supportClasses.cpp:1873) Enabling zero-conf tracking


At that point I start armory (again, with no bitcoind), and after some time I see that it connects to ArmoryDB, which starts scanning blocks until after a few minutes it crashes with an error:

Code:
-INFO  - 13:56:06: (BDM_Server.cpp:1074) registered bdv: de33372f76586bce256e
-INFO  - 13:56:07: (BDM_supportClasses.cpp:378) Starting address registration process
-INFO  - 14:03:23: (BlockchainScanner.cpp:665) scanned from height #0 to #223709
-INFO  - 14:03:33: (BlockchainScanner.cpp:665) scanned from height #223710 to #227221
-INFO  - 14:03:41: (BlockchainScanner.cpp:665) scanned from height #227222 to #230415
-INFO  - 14:03:48: (BlockchainScanner.cpp:665) scanned from height #230416 to #233652
...
...
...
-INFO  - 14:33:29: (BlockchainScanner.cpp:665) scanned from height #473510 to #474154
-INFO  - 14:33:38: (BlockchainScanner.cpp:665) scanned from height #474155 to #474726
-ERROR - 14:33:38: (BlockchainScanner.cpp:271) raw data does not match expected block hash
-ERROR - 14:33:38: (BlockchainScanner.cpp:271) raw data does not match expected block hash
-ERROR - 14:33:38: (BlockchainScanner.cpp:271) raw data does not match expected block hash
terminate called recursively
Aborted
gaglia@myhost:~$

When this happens, the Armory window is at 99% of "Scanning Transaction History". At the same time, the armory terminal window shows this:

Code:
gaglia@myhost:~$ armory
Gtk-Message: Failed to load module "canberra-gtk-module"
/home/gaglia
(ERROR) ArmoryUtils.py:3747 - Unsupported language  specified. Defaulting to English (en)
/usr/lib/armory/armoryengine/Transaction.py:2790: SyntaxWarning: import * only allowed at module level
  def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
(ERROR) ArmoryQt.py:1194 - 3 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:1199 - File mempool.bin does not exist. Nothing deleted.
-ERROR - 14:33:38: (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version

What I tried to do at this point is, instead of closing armory, I left the wondow open and tried to run again ArmoryDB, but then armory crashes:

Code:
(ERROR) ArmoryQt.py:1199 - File mempool.bin does not exist. Nothing deleted.
-ERROR - 14:33:38: (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
terminate called after throwing an instance of 'DbErrorMsg'
Aborted
gaglia@myhost:~$

Any idea? I'd rather prefer to not build my own armory if not strictly necessary.

But is it just me? I can't believe I'm having this weird errors, I don't have any strange configuration, I'm just trying to run "normally" armory on Debian... is it such an unpopular thing? Smiley
goatpig
legendary
Activity: 3640
Merit: 1345
Armory Developer
Re: Cannot start Armory on Linux Debian, stuck on "Preparing Databases"
July 08, 2017, 06:06:23 PM
#22
Quote from: gaglia on July 08, 2017, 03:29:35 PM
Nope, that's the 0.96.0.4 build from your github Sad

Try with your own build.
gaglia
newbie
Activity: 28
Merit: 0
Re: Cannot start Armory on Linux Debian, stuck on "Preparing Databases"
July 08, 2017, 03:29:35 PM
#21
Nope, that's the 0.96.0.4 build from your github Sad

I don't think it's a blockchain problem, bitcoin core works fine...
goatpig
legendary
Activity: 3640
Merit: 1345
Armory Developer
Re: Cannot start Armory on Linux Debian, stuck on "Preparing Databases"
July 08, 2017, 03:18:50 PM
#20
Quote
What's going on here? Sad thanks in advance again for any help!

No idea. Are you building the binaries yourself?
gaglia
newbie
Activity: 28
Merit: 0
Re: Cannot start Armory on Linux Debian, stuck on "Preparing Databases"
July 08, 2017, 02:54:29 PM
#19
OK, I did as requested, just I noticed that I left enabled the "allow armory to run its own bitcoind process" enabled. Let me know if it's critical and I should try again without. Anyway, here's what happens:

I delete (move) the "databases" dir and the old logs.

I launch "ArmoryDB --db-type=DB_BARE" from a shell (bitcoind not running). I see a lot of lines like "-INFO  - 20:05:31: (DatabaseBuilder.cpp:272) parsed block file #843" and after some time it finishes:

Code:
gaglia@myhost:~$ ArmoryDB --db-type=DB_BARE 
/home/gaglia
/home/gaglia
/home/gaglia/.armory/databases is not a valid path
logging in /home/gaglia/.armory/dbLog.txt
-INFO  - 18:39:54: (main.cpp:32) Running on 4 threads
-INFO  - 18:39:54: (main.cpp:33) Ram usage level: 4
-INFO  - 18:39:54: (BlockUtils.cpp:908) blkfile dir: /home/gaglia/.bitcoin/blocks
-INFO  - 18:39:54: (BlockUtils.cpp:909) lmdb dir: /home/gaglia/.armory/databases
-INFO  - 18:39:54: (lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 18:39:54: (BDM_Server.h:249) Listening on port 9001
-INFO  - 18:39:54: (BlockUtils.cpp:1092) Executing: doInitialSyncOnLoad
-INFO  - 18:39:54: (DatabaseBuilder.cpp:190) Reading headers from db
-WARN  - 18:39:54: (lmdb_wrapper.cpp:1175) No headers in DB yet!
-INFO  - 18:39:54: (DatabaseBuilder.cpp:229) Found 1 headers in db
-INFO  - 18:39:54: (DatabaseBuilder.cpp:70) updating HEADERS db
-INFO  - 18:46:06: (DatabaseBuilder.cpp:272) parsed block file #3
-INFO  - 18:46:23: (DatabaseBuilder.cpp:272) parsed block file #7
-INFO  - 18:46:41: (DatabaseBuilder.cpp:272) parsed block file #11
...
...
...
-INFO  - 20:14:40: (DatabaseBuilder.cpp:272) parsed block file #887
-INFO  - 20:18:51: (Blockchain.cpp:246) Organizing chain 
-INFO  - 20:18:53: (Blockchain.cpp:360) Organized chain in 1.57471s
-INFO  - 20:18:57: (DatabaseBuilder.cpp:75) updated HEADERS db in 5943s
-INFO  - 20:18:57: (BDM_supportClasses.cpp:1873) Enabling zero-conf tracking

After a couple of minutes I open another terminal and run armory. The GUI starts, but it's stuck at 0% of "Scanning Transaction History". After a few seconds, the ArmoryDB process exits:

Code:
-INFO  - 20:18:57: (DatabaseBuilder.cpp:75) updated HEADERS db in 5943s
-INFO  - 20:18:57: (BDM_supportClasses.cpp:1873) Enabling zero-conf tracking
-INFO  - 20:23:46: (BDM_Server.cpp:1074) registered bdv: 23b472deb9079773902f
-INFO  - 20:23:50: (BDM_supportClasses.cpp:378) Starting address registration process
Killed
gaglia@myhost:~$

On the armory side nothing changed: the GUI is still stuck with the bar at 0%. The terminal window says:

Code:
gaglia@myhost:~$ armory 
Gtk-Message: Failed to load module "canberra-gtk-module"
/home/gaglia
Log file doesn't exist [yet]
(ERROR) ArmoryUtils.py:3747 - Unsupported language  specified. Defaulting to English (en)
/usr/lib/armory/armoryengine/Transaction.py:2790: SyntaxWarning: import * only allowed at module level
  def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
(ERROR) ArmoryQt.py:1194 - 8 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:1199 - File mempool.bin does not exist. Nothing deleted.
-ERROR - 20:26:47: (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version

Then I close the armory window. Here is what happens on terminal:

Code:
  File "/usr/bin/../lib/armory/ArmoryQt.py", line 5950, in 
    os._exit(QAPP.exec_())
  File "/usr/bin/../lib/armory/ArmoryQt.py", line 5426, in closeForReal
    TheSDM.stopBitcoind()
  File "/usr/lib/armory/SDM.py", line 490, in stopBitcoind
    LOGERROR(e)
  File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 833, in LOGERROR
    traceback.print_stack()
(ERROR) ArmoryQt.py:5435 - Strange error during shutdown
Traceback (most recent call last):
  File "/usr/bin/../lib/armory/ArmoryQt.py", line 5426, in closeForReal
    TheSDM.stopBitcoind()
  File "/usr/lib/armory/SDM.py", line 490, in stopBitcoind
    LOGERROR(e)
  File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 831, in LOGERROR
    logging.error(callerStr + logstr)
TypeError: cannot concatenate 'str' and 'exceptions.RuntimeError' objects

Notice that the bitcoin daemon is still running, and I have to kill it:

Code:
root@myhost:/home/gaglia# pgrep bitcoind
6197

The dbLog.txt doesn't show anything more than what I reported, up to the "killed" line. Here is the armorylog.txt :

Code:
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1138 - C++ block utilities loaded successfully
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:667 - Executing popen: free -m
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:667 - Executing popen: ['cat', '/proc/cpuinfo']
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1255 - 
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1256 - 
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1257 - 
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1258 - ************************************************************
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1259 - Invoked: /usr/bin/../lib/armory/ArmoryQt.py
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1260 - ************************************************************
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1261 - Loading Armory Engine:
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1262 -    Armory Version        : 0.96.0.4
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1263 -    Armory Build:         : 98578163de
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1264 -    PyBtcWallet  Version  : 1.35
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1265 - Detected Operating system: Linux
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1266 -    OS Variant            : debian-9.0-
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1267 -    User home-directory   : /home/gaglia
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1268 -    Satoshi BTC directory : /home/gaglia/.bitcoin/
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1269 -    Armory home dir       : /home/gaglia/.armory/
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1270 - Detected System Specs    : 
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1271 -    Total Available RAM   : 7.68 GB
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1272 -    CPU ID string         : Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1273 -    Number of CPU cores   : 4 cores
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1274 -    System is 64-bit      : True
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1275 -    Preferred Encoding    : UTF-8
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1276 -    Machine Arch          : x86_64
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1277 -    Available HDD (ARM)   : 58 GB
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1278 -    Available HDD (BTC)   : 58 GB
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1279 - 
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1280 - Network Name: Main Network
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1281 - Satoshi Port: 8333
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1282 - Do wlt check: True
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1283 - Named options/arguments to armoryengine.py:
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     thread_count    : -1
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     rescan          : False
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     ignoreAllZC     : False
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     rescanBalance   : False
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     disableModules  : False
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     port            : None
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     interport       : 8223
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     coverageOutputDir: None
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     forceWalletCheck: False
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     regtest         : False
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     rebuild         : False
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     nettimeout      : 2
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     datadir         : DEFAULT
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     clearMempool    : False
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     offline         : False
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     armoryDBDir     : DEFAULT
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     armorydb_port   : 9001
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     satoshiPort     : DEFAULT
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     useTorSettings  : False
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     netlog          : False
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     keypool         : 100
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     coverageInclude : None
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     forceOnline     : False
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     redownload      : False
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     rpcBindAddr     : 127.0.0.1
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     armorydb_ip     : 127.0.0.1
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     multisigFile    : DEFAULT
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     ram_usage       : -1
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     mtdebug         : False
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     logDisable      : False
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     settingsPath    : /home/gaglia/.armory/ArmorySettings.txt
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     language        : en
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     db_type         : DB_FULL
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     doDebug         : False
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     enableDetSign   : True
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     disableConfPermis: False
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     testnet         : False
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     rpcport         : DEFAULT
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     satoshiHome     : DEFAULT
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     satoshiRpcport  : DEFAULT
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     logFile         : /home/gaglia/.armory/ArmoryQt.py.log.txt
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1285 -     verbosity       : None
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1286 - Other arguments:
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1289 - ************************************************************
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:1692 - C++ block utilities loaded successfully
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:3590 - Using settings file: /home/gaglia/.armory/ArmorySettings.txt
2017-07-08 20:23:43 (ERROR) -- ArmoryUtils.py:3747 - Unsupported language  specified. Defaulting to English (en)
2017-07-08 20:23:43 (INFO) -- ArmoryUtils.py:3750 - Using Language: en
2017-07-08 20:23:43 (INFO) -- BDM.py:365 - Using the asynchronous/multi-threaded BlockDataManager.
2017-07-08 20:23:43 (INFO) -- BDM.py:366 - Blockchain operations will happen in the background.  
2017-07-08 20:23:43 (INFO) -- BDM.py:367 - Devs: check TheBDM.getState() before asking for data.
2017-07-08 20:23:43 (INFO) -- BDM.py:368 - Registering addresses during rescans will queue them for 
2017-07-08 20:23:43 (INFO) -- BDM.py:369 - inclusion after the current scan is completed.
2017-07-08 20:23:44 (INFO) -- ArmoryUtils.py:3590 - Using settings file: /home/gaglia/.armory/ArmorySettings.txt
2017-07-08 20:23:44 (INFO) -- ArmoryQt.py:2050 - loadWalletsAndSettings
2017-07-08 20:23:44 (INFO) -- ArmoryQt.py:2110 - Loading wallets...
2017-07-08 20:23:46 (INFO) -- ArmoryQt.py:2175 - Number of wallets read in: 4
2017-07-08 20:23:46 (INFO) -- ArmoryQt.py:2180 -    Wallet (XXX):   "Wallet test1    "   (Encrypted)
2017-07-08 20:23:46 (INFO) -- ArmoryQt.py:2180 -    Wallet (XXX):   "Wallet test2 "   (Encrypted)
2017-07-08 20:23:46 (INFO) -- ArmoryQt.py:2180 -    Wallet (XXX):    "Wallet test3 "   (Encrypted)
2017-07-08 20:23:46 (INFO) -- ArmoryQt.py:2180 -    Wallet (XXX):   "Primary Wallet                  "   (Encrypted)
2017-07-08 20:23:46 (INFO) -- ArmoryQt.py:1752 - acquiring process mutex...
2017-07-08 20:23:46 (INFO) -- ArmoryQt.py:1391 - setupUriRegistration
2017-07-08 20:23:46 (INFO) -- ArmoryUtils.py:667 - Executing popen: gconftool-2 --get /desktop/gnome/url-handlers/bitcoin/command
2017-07-08 20:23:46 (INFO) -- ArmoryUtils.py:667 - Executing popen: xdg-mime query default x-scheme-handler/bitcoin
2017-07-08 20:23:46 (INFO) -- ArmoryQt.py:565 - Usermode: Advanced
2017-07-08 20:23:46 (INFO) -- ArmoryQt.py:1687 - Changing usermode:
2017-07-08 20:23:46 (INFO) -- ArmoryQt.py:1688 -    From: Advanced
2017-07-08 20:23:46 (INFO) -- ArmoryQt.py:1696 -      To: Advanced
2017-07-08 20:23:46 (INFO) -- ArmoryQt.py:1825 - startBitcoindIfNecessary
2017-07-08 20:23:46 (INFO) -- ArmoryQt.py:1861 - setSatoshiPaths
2017-07-08 20:23:46 (INFO) -- ArmoryUtils.py:667 - Executing popen: ['whereis', 'bitcoind']
2017-07-08 20:23:46 (INFO) -- SDM.py:289 - "whereis" returned: ['/opt/bitcoin-0.14.1/bin/bitcoind']
2017-07-08 20:23:46 (INFO) -- SDM.py:169 - Found bitcoind in the following places:
2017-07-08 20:23:46 (INFO) -- SDM.py:171 -    /opt/bitcoin-0.14.1/bin/bitcoind
2017-07-08 20:23:46 (INFO) -- SDM.py:171 -    /opt/bitcoin-0.14.1/bin/bitcoind
2017-07-08 20:23:46 (INFO) -- SDM.py:173 - Using: /opt/bitcoin-0.14.1/bin/bitcoind
2017-07-08 20:23:46 (INFO) -- SDM.py:337 - Called startBitcoind
2017-07-08 20:23:46 (INFO) -- ArmoryUtils.py:667 - Executing popen: [u'/opt/bitcoin-0.14.1/bin/bitcoind', '-datadir=/home/gaglia/.bitcoin/']
2017-07-08 20:23:46 (INFO) -- SDM.py:450 - PID of bitcoind: 6197
2017-07-08 20:23:46 (INFO) -- SDM.py:451 - PID of armory:   6170
2017-07-08 20:23:46 (INFO) -- ArmoryUtils.py:667 - Executing popen: ['python', '/usr/lib/armory/guardian.py', '6170', '6197']
2017-07-08 20:23:46 (INFO) -- ArmoryQt.py:1913 - Setting netmode: 1
2017-07-08 20:23:49 (INFO) -- ArmoryQt.py:1895 - loadBlockchainIfNecessary
2017-07-08 20:23:49 (ERROR) -- ArmoryQt.py:1194 - 8 attempts to load blockchain failed.  Remove mempool.bin.
2017-07-08 20:23:49 (ERROR) -- ArmoryQt.py:1199 - File mempool.bin does not exist. Nothing deleted.
2017-07-08 20:23:50 (INFO) -- ArmoryQt.py:1913 - Setting netmode: 1
2017-07-08 20:23:50 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-07-08 20:23:50 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-07-08 20:23:50 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-07-08 20:45:18 (INFO) -- ArmoryQt.py:5422 - BDM state is scanning -- force shutdown BDM
2017-07-08 20:45:18 (INFO) -- SDM.py:464 - Called stopBitcoind
2017-07-08 20:45:18 (ERROR) -- ArmoryQt.py:5435 - Strange error during shutdown
Traceback (most recent call last):
  File "/usr/bin/../lib/armory/ArmoryQt.py", line 5426, in closeForReal
    TheSDM.stopBitcoind()
  File "/usr/lib/armory/SDM.py", line 490, in stopBitcoind
    LOGERROR(e)
  File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 831, in LOGERROR
    logging.error(callerStr + logstr)
TypeError: cannot concatenate 'str' and 'exceptions.RuntimeError' objects
2017-07-08 20:45:18 (INFO) -- ArmoryQt.py:5437 - Attempting to close the main window!

What's going on here? Sad thanks in advance again for any help!
gaglia
newbie
Activity: 28
Merit: 0
Re: Cannot start Armory on Linux Debian, stuck on "Preparing Databases"
July 08, 2017, 12:45:16 PM
#18
Quote from: goatpig on July 08, 2017, 04:38:27 AM
https://bitcointalksearch.org/topic/m.19997939

This these instructions.

Those instructions refer to windows but OK, I'll try those on Debian. I removed (renamed) the /home/gaglia/.armory/databases directory and (with no bitcoind running) I started "ArmoryDB --db-type=DB_BARE" from a shell. This is what I see:

Code:
gaglia@myhost:~$ ArmoryDB --db-type=DB_BARE 
/home/gaglia
/home/gaglia
/home/gaglia/.armory/databases is not a valid path
logging in /home/gaglia/.armory/dbLog.txt
-INFO  - 18:39:54: (main.cpp:32) Running on 4 threads
-INFO  - 18:39:54: (main.cpp:33) Ram usage level: 4
-INFO  - 18:39:54: (BlockUtils.cpp:908) blkfile dir: /home/gaglia/.bitcoin/blocks
-INFO  - 18:39:54: (BlockUtils.cpp:909) lmdb dir: /home/gaglia/.armory/databases
-INFO  - 18:39:54: (lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 18:39:54: (BDM_Server.h:249) Listening on port 9001
-INFO  - 18:39:54: (BlockUtils.cpp:1092) Executing: doInitialSyncOnLoad
-INFO  - 18:39:54: (DatabaseBuilder.cpp:190) Reading headers from db
-WARN  - 18:39:54: (lmdb_wrapper.cpp:1175) No headers in DB yet!
-INFO  - 18:39:54: (DatabaseBuilder.cpp:229) Found 1 headers in db
-INFO  - 18:39:54: (DatabaseBuilder.cpp:70) updating HEADERS db

As far as I understand I should see "enabling zero conf parsing" at some point. I'll wait for that for a couple of hours. Then (or anyway in a couple of hours) I will launch Armory without closing the window and see what happens.

Thanks for the help Smiley
goatpig
legendary
Activity: 3640
Merit: 1345
Armory Developer
Re: Cannot start Armory on Linux Debian, stuck on "Preparing Databases"
July 08, 2017, 04:38:27 AM
#17
https://bitcointalksearch.org/topic/m.19997939

This these instructions.
gaglia
newbie
Activity: 28
Merit: 0
Re: Cannot start Armory on Linux Debian, stuck on "Preparing Databases"
July 08, 2017, 04:30:30 AM
#16
Nothing changed, it just runs fine until 99% of "Scanning Transaction History", and then it gets stuck. Also bottom right corner of the windows is always a red "offline". I do not have any strange firewall rules preventing connection as far as I know.

I'd really appreciate any help Sad
gaglia
newbie
Activity: 28
Merit: 0
Re: Cannot start Armory on Linux Debian, stuck on "Preparing Databases"
July 07, 2017, 05:27:29 AM
#15
I've noticed something interesting.

I stopped armory and let it run again. What happens, again, is that everything seems to work fine up to 99% of "Scanning Transaction History" (1 sec left). Then everything gets stuck and I see this error message from the command line:

Code:
(python2:24260): Gtk-CRITICAL **: IA__gtk_progress_configure: assertion 'value >= min && value <= max' failed
-ERROR - 10:51:19: (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version

I'm still keeping it running in this state for a while. In the meantime, here are the last few lines of this huge dbLog.txt - the thing I noticed is that the timestamp of the last few lines of the log, where the ERROR appears, coincide with the ERROR line above:

Code:
gaglia@mydomain:~/.armory$ tail -n 50 dbLog.txt 
-INFO  - 10:48:47: (BlockchainScanner.cpp:665) scanned from height #465333 to #466010
-INFO  - 10:48:50: (BlockchainScanner.cpp:665) scanned from height #466011 to #466023
-INFO  - 10:48:50: (BlockchainScanner.cpp:665) scanned from height #466024 to #466032
-INFO  - 10:48:52: (BlockchainScanner.cpp:665) scanned from height #466033 to #466034
-INFO  - 10:48:54: (BlockchainScanner.cpp:665) scanned from height #466035 to #466039
-INFO  - 10:48:55: (BlockchainScanner.cpp:665) scanned from height #466040 to #466067
-INFO  - 10:48:55: (BlockchainScanner.cpp:665) scanned from height #466068 to #466072
-INFO  - 10:48:55: (BlockchainScanner.cpp:665) scanned from height #466073 to #466084
-INFO  - 10:49:15: (BlockchainScanner.cpp:665) scanned from height #466085 to #467411
-INFO  - 10:49:22: (BlockchainScanner.cpp:665) scanned from height #467412 to #467729
-INFO  - 10:49:27: (BlockchainScanner.cpp:665) scanned from height #467730 to #467740
-INFO  - 10:49:31: (BlockchainScanner.cpp:665) scanned from height #467741 to #467751
-INFO  - 10:49:32: (BlockchainScanner.cpp:665) scanned from height #467752 to #467757
-INFO  - 10:49:34: (BlockchainScanner.cpp:665) scanned from height #467758 to #467771
-INFO  - 10:49:36: (BlockchainScanner.cpp:665) scanned from height #467772 to #467775
-INFO  - 10:49:36: (BlockchainScanner.cpp:665) scanned from height #467776 to #467806
-INFO  - 10:49:36: (BlockchainScanner.cpp:665) scanned from height #467807 to #467811
-INFO  - 10:49:37: (BlockchainScanner.cpp:665) scanned from height #467812 to #467824
-INFO  - 10:49:37: (BlockchainScanner.cpp:665) scanned from height #467825 to #467837
-INFO  - 10:49:37: (BlockchainScanner.cpp:665) scanned from height #467838 to #467842
-INFO  - 10:49:38: (BlockchainScanner.cpp:665) scanned from height #467843 to #467854
-INFO  - 10:49:38: (BlockchainScanner.cpp:665) scanned from height #467855 to #467876
-INFO  - 10:49:39: (BlockchainScanner.cpp:665) scanned from height #467877 to #467948
-INFO  - 10:49:39: (BlockchainScanner.cpp:665) scanned from height #467949 to #468000
-INFO  - 10:49:39: (BlockchainScanner.cpp:665) scanned from height #468001 to #468021
-INFO  - 10:49:39: (BlockchainScanner.cpp:665) scanned from height #468022 to #468063
-INFO  - 10:49:39: (BlockchainScanner.cpp:665) scanned from height #468064 to #468071
-INFO  - 10:49:39: (BlockchainScanner.cpp:665) scanned from height #468072 to #468081
-INFO  - 10:49:39: (BlockchainScanner.cpp:665) scanned from height #468082 to #468088
-INFO  - 10:49:39: (BlockchainScanner.cpp:665) scanned from height #468089 to #468095
-INFO  - 10:49:39: (BlockchainScanner.cpp:665) scanned from height #468096 to #468106
-INFO  - 10:49:39: (BlockchainScanner.cpp:665) scanned from height #468107 to #468150
-INFO  - 10:49:39: (BlockchainScanner.cpp:665) scanned from height #468151 to #468192
-INFO  - 10:49:41: (BlockchainScanner.cpp:665) scanned from height #468193 to #468292
-INFO  - 10:49:41: (BlockchainScanner.cpp:665) scanned from height #468293 to #468300
-INFO  - 10:49:41: (BlockchainScanner.cpp:665) scanned from height #468301 to #468507
-INFO  - 10:49:45: (BlockchainScanner.cpp:665) scanned from height #468508 to #468924
-INFO  - 10:49:51: (BlockchainScanner.cpp:665) scanned from height #468925 to #469300
-INFO  - 10:49:55: (BlockchainScanner.cpp:665) scanned from height #469301 to #469637
-INFO  - 10:50:00: (BlockchainScanner.cpp:665) scanned from height #469638 to #469950
-INFO  - 10:50:12: (BlockchainScanner.cpp:665) scanned from height #469951 to #470583
-INFO  - 10:50:17: (BlockchainScanner.cpp:665) scanned from height #470584 to #470835
-INFO  - 10:50:29: (BlockchainScanner.cpp:665) scanned from height #470836 to #471542
-INFO  - 10:50:38: (BlockchainScanner.cpp:665) scanned from height #471543 to #472044
-INFO  - 10:51:05: (BlockchainScanner.cpp:665) scanned from height #472045 to #473066
-INFO  - 10:51:14: (BlockchainScanner.cpp:665) scanned from height #473067 to #473509
-ERROR - 10:51:19: (BlockchainScanner.cpp:271) raw data does not match expected block hash
-ERROR - 10:51:19: (BlockchainScanner.cpp:271) raw data does not match expected block hash
-ERROR - 10:51:19: (BlockchainScanner.cpp:271) raw data does not match expected block hash
-ERROR - 10:51:19: (BlockchainScanner.cpp:271) raw data does not match expected block hash
gaglia
newbie
Activity: 28
Merit: 0
Re: Cannot start Armory on Linux Debian, stuck on "Preparing Databases"
July 07, 2017, 04:06:09 AM
#14
Nothing, I still cannot make Armory work, any help is appreciated to understand what's happening here Sad

I've let Armory run overnight but it was always stuck at 99% of "Scanning Transaction History" when I woke up.

When I closed it, I noticed this from the command line:

Code:
gaglia@mydomain:~$ armory
Gtk-Message: Failed to load module "canberra-gtk-module"
/home/gaglia
(ERROR) ArmoryUtils.py:3747 - Unsupported language  specified. Defaulting to English (en)
/usr/lib/armory/armoryengine/Transaction.py:2790: SyntaxWarning: import * only allowed at module level
  def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
(WARNING) SDM.py:403 - Spawning DB with command:ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/home/gaglia/.bitcoin/" --datadir="/home/gaglia/.armory/" --dbdir="/home/gaglia/.armory/databases"
(ERROR) ArmoryQt.py:1194 - 4 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:1199 - File mempool.bin does not exist. Nothing deleted.

(python2:1869): Gtk-CRITICAL **: IA__gtk_progress_configure: assertion 'value >= min && value <= max' failed
-ERROR - 04:39:41: (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
  File "/usr/bin/../lib/armory/ArmoryQt.py", line 5950, in 
    os._exit(QAPP.exec_())
  File "/usr/bin/../lib/armory/ArmoryQt.py", line 5426, in closeForReal
    TheSDM.stopBitcoind()
  File "/usr/lib/armory/SDM.py", line 490, in stopBitcoind
    LOGERROR(e)
  File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 833, in LOGERROR
    traceback.print_stack()
(ERROR) ArmoryQt.py:5435 - Strange error during shutdown
Traceback (most recent call last):
  File "/usr/bin/../lib/armory/ArmoryQt.py", line 5426, in closeForReal
    TheSDM.stopBitcoind()
  File "/usr/lib/armory/SDM.py", line 490, in stopBitcoind
    LOGERROR(e)
  File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 831, in LOGERROR
    logging.error(callerStr + logstr)
TypeError: cannot concatenate 'str' and 'exceptions.RuntimeError' objects
gaglia@pandemonium:~$

This was with the "allow armory to run bitcoind in the background" option enabled. However, when I closed Armory, apparently it failed to close bitcoind, so I had to kill bitcoind manually.

Here is the armorylog.txt between the start and the end of the last run (the dbLog.tst file is over 600 MiB in size, is it normal?)

Code:
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1138 - C++ block utilities loaded successfully
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:667 - Executing popen: free -m
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:667 - Executing popen: ['cat', '/proc/cpuinfo']
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1255 - 
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1256 - 
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1257 - 
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1258 - ************************************************************
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1259 - Invoked: /usr/bin/../lib/armory/ArmoryQt.py
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1260 - ************************************************************
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1261 - Loading Armory Engine:
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1262 -    Armory Version        : 0.96.0.4
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1263 -    Armory Build:         : 98578163de
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1264 -    PyBtcWallet  Version  : 1.35
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1265 - Detected Operating system: Linux
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1266 -    OS Variant            : debian-9.0-
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1267 -    User home-directory   : /home/gaglia
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1268 -    Satoshi BTC directory : /home/gaglia/.bitcoin/
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1269 -    Armory home dir       : /home/gaglia/.armory/
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1270 - Detected System Specs    : 
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1271 -    Total Available RAM   : 7.68 GB
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1272 -    CPU ID string         : Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1273 -    Number of CPU cores   : 4 cores
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1274 -    System is 64-bit      : True
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1275 -    Preferred Encoding    : UTF-8
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1276 -    Machine Arch          : x86_64
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1277 -    Available HDD (ARM)   : 62 GB
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1278 -    Available HDD (BTC)   : 62 GB
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1279 - 
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1280 - Network Name: Main Network
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1281 - Satoshi Port: 8333
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1282 - Do wlt check: True
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1283 - Named options/arguments to armoryengine.py:
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     thread_count    : -1
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     rescan          : False
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     ignoreAllZC     : False
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     rescanBalance   : False
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     disableModules  : False
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     port            : None
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     interport       : 8223
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     coverageOutputDir: None
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     forceWalletCheck: False
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     regtest         : False
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     rebuild         : False
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     nettimeout      : 2
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     datadir         : DEFAULT
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     clearMempool    : False
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     offline         : False
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     armoryDBDir     : DEFAULT
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     armorydb_port   : 9001
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     satoshiPort     : DEFAULT
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     useTorSettings  : False
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     netlog          : False
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     keypool         : 100
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     coverageInclude : None
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     forceOnline     : False
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     redownload      : False
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     rpcBindAddr     : 127.0.0.1
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     armorydb_ip     : 127.0.0.1
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     multisigFile    : DEFAULT
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     ram_usage       : -1
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     mtdebug         : False
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     logDisable      : False
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     settingsPath    : /home/gaglia/.armory/ArmorySettings.txt
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     language        : en
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     db_type         : DB_FULL
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     doDebug         : False
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     enableDetSign   : True
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     disableConfPermis: False
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     testnet         : False
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     rpcport         : DEFAULT
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     satoshiHome     : DEFAULT
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     satoshiRpcport  : DEFAULT
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     logFile         : /home/gaglia/.armory/ArmoryQt.py.log.txt
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1285 -     verbosity       : None
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1286 - Other arguments:
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1289 - ************************************************************
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:1692 - C++ block utilities loaded successfully
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:3590 - Using settings file: /home/gaglia/.armory/ArmorySettings.txt
2017-07-07 01:57:21 (ERROR) -- ArmoryUtils.py:3747 - Unsupported language  specified. Defaulting to English (en)
2017-07-07 01:57:21 (INFO) -- ArmoryUtils.py:3750 - Using Language: en
2017-07-07 01:57:21 (INFO) -- BDM.py:365 - Using the asynchronous/multi-threaded BlockDataManager.
2017-07-07 01:57:21 (INFO) -- BDM.py:366 - Blockchain operations will happen in the background.  
2017-07-07 01:57:21 (INFO) -- BDM.py:367 - Devs: check TheBDM.getState() before asking for data.
2017-07-07 01:57:21 (INFO) -- BDM.py:368 - Registering addresses during rescans will queue them for 
2017-07-07 01:57:21 (INFO) -- BDM.py:369 - inclusion after the current scan is completed.
2017-07-07 01:57:22 (INFO) -- ArmoryUtils.py:3590 - Using settings file: /home/gaglia/.armory/ArmorySettings.txt
2017-07-07 01:57:22 (INFO) -- ArmoryQt.py:2050 - loadWalletsAndSettings
2017-07-07 01:57:22 (INFO) -- ArmoryQt.py:2110 - Loading wallets...
2017-07-07 01:57:22 (INFO) -- ArmoryQt.py:2175 - Number of wallets read in: 4
2017-07-07 01:57:22 (INFO) -- ArmoryQt.py:2180 -    Wallet (XXXXXXXXX):   "Wallet test 1"   (Encrypted)
2017-07-07 01:57:22 (INFO) -- ArmoryQt.py:2180 -    Wallet (XXXXXXXXX):   "Wallet test 2"   (Encrypted)
2017-07-07 01:57:22 (INFO) -- ArmoryQt.py:2180 -    Wallet (XXXXXXXXX):    "Wallet test 3"   (Encrypted)
2017-07-07 01:57:22 (INFO) -- ArmoryQt.py:2180 -    Wallet (XXXXXXXXX):   "Primary Wallet                  "   (Encrypted)
2017-07-07 01:57:22 (INFO) -- ArmoryQt.py:1752 - acquiring process mutex...
2017-07-07 01:57:22 (INFO) -- ArmoryQt.py:1391 - setupUriRegistration
2017-07-07 01:57:22 (INFO) -- ArmoryUtils.py:667 - Executing popen: gconftool-2 --get /desktop/gnome/url-handlers/bitcoin/command
2017-07-07 01:57:23 (INFO) -- ArmoryUtils.py:667 - Executing popen: xdg-mime query default x-scheme-handler/bitcoin
2017-07-07 01:57:23 (INFO) -- ArmoryQt.py:565 - Usermode: Advanced
2017-07-07 01:57:23 (INFO) -- ArmoryQt.py:1687 - Changing usermode:
2017-07-07 01:57:23 (INFO) -- ArmoryQt.py:1688 -    From: Advanced
2017-07-07 01:57:23 (INFO) -- ArmoryQt.py:1696 -      To: Advanced
2017-07-07 01:57:23 (INFO) -- ArmoryQt.py:1825 - startBitcoindIfNecessary
2017-07-07 01:57:23 (INFO) -- ArmoryQt.py:1861 - setSatoshiPaths
2017-07-07 01:57:23 (INFO) -- ArmoryUtils.py:667 - Executing popen: ['whereis', 'bitcoind']
2017-07-07 01:57:23 (INFO) -- SDM.py:289 - "whereis" returned: ['/opt/bitcoin-0.14.1/bin/bitcoind']
2017-07-07 01:57:23 (INFO) -- SDM.py:169 - Found bitcoind in the following places:
2017-07-07 01:57:23 (INFO) -- SDM.py:171 -    /opt/bitcoin-0.14.1/bin/bitcoind
2017-07-07 01:57:23 (INFO) -- SDM.py:171 -    /opt/bitcoin-0.14.1/bin/bitcoind
2017-07-07 01:57:23 (INFO) -- SDM.py:173 - Using: /opt/bitcoin-0.14.1/bin/bitcoind
2017-07-07 01:57:23 (INFO) -- SDM.py:337 - Called startBitcoind
2017-07-07 01:57:23 (INFO) -- ArmoryUtils.py:667 - Executing popen: [u'/opt/bitcoin-0.14.1/bin/bitcoind', '-datadir=/home/gaglia/.bitcoin/']
2017-07-07 01:57:23 (INFO) -- SDM.py:450 - PID of bitcoind: 1897
2017-07-07 01:57:23 (INFO) -- SDM.py:451 - PID of armory:   1869
2017-07-07 01:57:23 (INFO) -- ArmoryUtils.py:667 - Executing popen: ['python', '/usr/lib/armory/guardian.py', '1869', '1897']
2017-07-07 01:57:23 (INFO) -- ArmoryQt.py:1861 - setSatoshiPaths
2017-07-07 01:57:23 (WARNING) -- SDM.py:403 - Spawning DB with command:ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/home/gaglia/.bitcoin/" --datadir="/home/gaglia/.armory/" --dbdir="/home/gaglia/.armory/databases"
2017-07-07 01:57:23 (INFO) -- ArmoryUtils.py:667 - Executing popen: ['ArmoryDB', '--db-type="DB_FULL"', '--cookie', '--satoshi-datadir="/home/gaglia/.bitcoin/"', '--datadir="/home/gaglia/.armory/"', '--dbdir="/home/gaglia/.armory/databases"']
2017-07-07 01:57:24 (INFO) -- ArmoryQt.py:1813 - Connecting on port 63945
2017-07-07 01:57:24 (INFO) -- ArmoryQt.py:1913 - Setting netmode: 1
2017-07-07 01:57:25 (INFO) -- ArmoryQt.py:1895 - loadBlockchainIfNecessary
2017-07-07 01:57:25 (ERROR) -- ArmoryQt.py:1194 - 4 attempts to load blockchain failed.  Remove mempool.bin.
2017-07-07 01:57:25 (ERROR) -- ArmoryQt.py:1199 - File mempool.bin does not exist. Nothing deleted.
2017-07-07 01:57:25 (INFO) -- ArmoryQt.py:1913 - Setting netmode: 1
2017-07-07 01:57:25 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-07-07 01:57:25 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-07-07 01:57:37 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-07-07 01:57:39 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-07-07 01:57:41 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-07-07 01:57:46 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-07-07 01:57:49 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-07-07 01:57:51 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-07-07 01:57:53 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-07-07 01:57:55 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-07-07 01:57:56 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-07-07 01:58:05 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-07-07 01:58:07 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-07-07 01:58:11 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-07-07 01:58:16 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-07-07 01:58:16 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-07-07 01:59:16 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-07-07 02:21:05 (INFO) -- ArmoryQt.py:4586 - Dashboard switched to auto-InitSync
2017-07-07 02:21:06 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
[more than 300 lines like these]
2017-07-07 04:39:24 (INFO) -- ArmoryQt.py:4644 - Dashboard switched to "Scanning" mode
2017-07-07 09:36:26 (INFO) -- ArmoryQt.py:5422 - BDM state is scanning -- force shutdown BDM
2017-07-07 09:36:26 (INFO) -- SDM.py:464 - Called stopBitcoind
2017-07-07 09:36:26 (ERROR) -- ArmoryQt.py:5435 - Strange error during shutdown
Traceback (most recent call last):
  File "/usr/bin/../lib/armory/ArmoryQt.py", line 5426, in closeForReal
    TheSDM.stopBitcoind()
  File "/usr/lib/armory/SDM.py", line 490, in stopBitcoind
    LOGERROR(e)
  File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 831, in LOGERROR
    logging.error(callerStr + logstr)
TypeError: cannot concatenate 'str' and 'exceptions.RuntimeError' objects
2017-07-07 09:36:26 (INFO) -- ArmoryQt.py:5437 - Attempting to close the main window!



gaglia
newbie
Activity: 28
Merit: 0
Re: Cannot start Armory on Linux Debian, stuck on "Preparing Databases"
July 06, 2017, 04:50:52 PM
#13
Wait, something is happening... the "Scanning Transaction History" bar has completed, just it's stuck at 99% with "1 second" time remaining... I'll give it some more time to run and see what happens, will keep you updated Smiley
achow101
staff
Activity: 3374
Merit: 6530
Just writing some code
Re: Cannot start Armory on Linux Debian, stuck on "Preparing Databases"
July 06, 2017, 04:34:20 PM
#12
Quote from: gaglia on July 06, 2017, 02:58:12 PM
Sorry, forget about the "GUI not appearing", obviously I was running the wrong command. Anyway, now the GUI appears but it still seems to be unable to sync (stuck at "Scanning Transaction History"):

Code:
gaglia@mydomain:~$ armory
Gtk-Message: Failed to load module "canberra-gtk-module"
/home/gaglia
(ERROR) ArmoryUtils.py:3747 - Unsupported language  specified. Defaulting to English (en)
/usr/lib/armory/armoryengine/Transaction.py:2790: SyntaxWarning: import * only allowed at module level
  def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
(WARNING) SDM.py:403 - Spawning DB with command:ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/home/gaglia/.bitcoin/" --datadir="/home/gaglia/.armory/" --dbdir="/home/gaglia/.armory/databases"
(ERROR) ArmoryQt.py:1194 - 3 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:1199 - File mempool.bin does not exist. Nothing deleted.

(python2:14420): Gtk-CRITICAL **: IA__gtk_progress_configure: assertion 'value >= min && value <= max' failed


Can you post the armorylog.txt and dbLog.tst files from after you run it again and see the problem?
gaglia
newbie
Activity: 28
Merit: 0
Re: Cannot start Armory on Linux Debian, stuck on "Preparing Databases"
July 06, 2017, 02:58:12 PM
#11
Sorry, forget about the "GUI not appearing", obviously I was running the wrong command. Anyway, now the GUI appears but it still seems to be unable to sync (stuck at "Scanning Transaction History"):

Code:
gaglia@mydomain:~$ armory
Gtk-Message: Failed to load module "canberra-gtk-module"
/home/gaglia
(ERROR) ArmoryUtils.py:3747 - Unsupported language  specified. Defaulting to English (en)
/usr/lib/armory/armoryengine/Transaction.py:2790: SyntaxWarning: import * only allowed at module level
  def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
(WARNING) SDM.py:403 - Spawning DB with command:ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/home/gaglia/.bitcoin/" --datadir="/home/gaglia/.armory/" --dbdir="/home/gaglia/.armory/databases"
(ERROR) ArmoryQt.py:1194 - 3 attempts to load blockchain failed.  Remove mempool.bin.
(ERROR) ArmoryQt.py:1199 - File mempool.bin does not exist. Nothing deleted.

(python2:14420): Gtk-CRITICAL **: IA__gtk_progress_configure: assertion 'value >= min && value <= max' failed

gaglia
newbie
Activity: 28
Merit: 0
Re: Cannot start Armory on Linux Debian, stuck on "Preparing Databases"
July 06, 2017, 02:07:11 PM
#10
Quote from: achow101 on July 06, 2017, 01:58:07 PM
Try using our latest testing build, 0.96.0.4: https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.0.4

GUI not appearing, stuck at this:

Code:
gaglia@mydomain:~/Downloads$ ArmoryDB 
/home/gaglia
/home/gaglia
logging in /home/gaglia/.armory/dbLog.txt
-INFO  - 20:02:16: (main.cpp:32) Running on 4 threads
-INFO  - 20:02:16: (main.cpp:33) Ram usage level: 4
-INFO  - 20:02:16: (BlockUtils.cpp:908) blkfile dir: /home/gaglia/.bitcoin/blocks
-INFO  - 20:02:16: (BlockUtils.cpp:909) lmdb dir: /home/gaglia/.armory/databases
-INFO  - 20:02:16: (lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 20:02:16: (BDM_Server.h:249) Listening on port 9001
-INFO  - 20:02:16: (BlockUtils.cpp:1092) Executing: doInitialSyncOnLoad
-INFO  - 20:02:16: (BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO  - 20:02:16: (DatabaseBuilder.cpp:190) Reading headers from db
-WARN  - 20:02:18: (Blockchain.cpp:63) block id duplicate: 474067
-INFO  - 20:02:18: (DatabaseBuilder.cpp:229) Found 474540 headers in db
-INFO  - 20:02:20: (DatabaseBuilder.cpp:63) Rewinding 100 blocks
-INFO  - 20:02:20: (DatabaseBuilder.cpp:70) updating HEADERS db
-INFO  - 20:02:20: (DatabaseBuilder.cpp:482) Found next block after skipping 998189bytes
-INFO  - 20:02:21: (DatabaseBuilder.cpp:272) parsed block file #885
-INFO  - 20:02:22: (Blockchain.cpp:246) Organizing chain 
-INFO  - 20:02:22: (Blockchain.cpp:360) Organized chain in 0.028874s
-INFO  - 20:02:22: (DatabaseBuilder.cpp:75) updated HEADERS db in 1.80588s
-INFO  - 20:02:22: (DatabaseBuilder.cpp:1121) verifying txfilters integrity
-INFO  - 20:03:17: (DatabaseBuilder.cpp:1205) done checking txfilters
-INFO  - 20:03:17: (BDM_supportClasses.cpp:1873) Enabling zero-conf tracking
-INFO  - 20:04:21: (BlockchainScanner.cpp:52) no history to scan
-INFO  - 20:06:54: (BlockchainScanner.cpp:52) no history to scan



achow101
staff
Activity: 3374
Merit: 6530
Just writing some code
Re: Cannot start Armory on Linux Debian, stuck on "Preparing Databases"
July 06, 2017, 01:58:07 PM
#9
Try using our latest testing build, 0.96.0.4: https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.0.4
gaglia
newbie
Activity: 28
Merit: 0
Re: Cannot start Armory on Linux Debian, stuck on "Preparing Databases"
July 06, 2017, 01:47:01 PM
#8
Thanks for the clarification Smiley

However, I still cannot manage to make Armory work. It happened only once, and I have no idea for which reasons, that the progress bar for "building database" moved, however after that it remained offline. Now, regardless of what I do, every time I open Armory (Online or Offline, with or without Bitcoin-QT running, with or without "allow Armory to run bicoind" enabled), the two progress bars remain stuck at 0%.

If I try to first run Bitcoin-QT (and wait that it's synced) and then after that I concurrently run Armory (Online) from a terminal window I see this:

Code:
gaglia@mydomain:~$ ArmoryDB 
/home/gaglia
/home/gaglia
logging in /home/gaglia/.armory/dbLog.txt
-INFO  - 1499362735: (main.cpp:23) Running on 4 threads
-INFO  - 1499362735: (main.cpp:24) Ram usage level: 4
-INFO  - 1499362735: (BlockUtils.cpp:907) blkfile dir: /home/gaglia/.bitcoin/blocks
-INFO  - 1499362735: (BlockUtils.cpp:908) lmdb dir: /home/gaglia/.armory/databases
-INFO  - 1499362735: (lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 1499362735: (BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO  - 1499362735: (BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO  - 1499362735: (DatabaseBuilder.cpp:169) Reading headers from db
-INFO  - 1499362737: (DatabaseBuilder.cpp:208) Found 474536 headers in db
-INFO  - 1499362739: (DatabaseBuilder.cpp:51) updating HEADERS db
-INFO  - 1499362739: (DatabaseBuilder.cpp:477) Found next block after skipping 732484bytes
-INFO  - 1499362740: (DatabaseBuilder.cpp:268) parsed block file #885
-DEBUG - 1499362740: (Blockchain.cpp:242) Organizing chain 
-INFO  - 1499362740: (DatabaseBuilder.cpp:56) updated HEADERS db in 0.456405s
-INFO  - 1499362740: (BlockUtils.cpp:1206) Enabling zero-conf tracking 
-WARN  - 1499362745: (BDM_supportClasses.cpp:1891) running 10 zc parser threads
-WARN  - 1499362745: (BDM_supportClasses.cpp:1891) running 15 zc parser threads
-WARN  - 1499362745: (BDM_supportClasses.cpp:1891) running 20 zc parser threads
-WARN  - 1499362745: (BDM_supportClasses.cpp:1891) running 25 zc parser threads
-WARN  - 1499362745: (BDM_supportClasses.cpp:1891) running 30 zc parser threads
-WARN  - 1499362745: (BDM_supportClasses.cpp:1891) running 35 zc parser threads
-INFO  - 1499362878: (BlockchainScanner.cpp:52) no history to scan

What am I doing wrong? My bitcoin binaries are at /opt/bitcoin/bin
achow101
staff
Activity: 3374
Merit: 6530
Just writing some code
Re: Cannot start Armory on Linux Debian, stuck on "Preparing Databases"
July 02, 2017, 05:25:13 PM
#7
Quote from: gaglia on July 02, 2017, 05:05:54 PM
It predicts a few hours until the end of "Building Databases", although I'm not sure what this means... what databases is Armory building? Doesn't it use the same blockchain as in the .bitcoin directory?
Yes it uses the same blockchain, but the blockchain is not the database. The blockchain is just a bunch of data which has to be interpreted. In order to know where blocks and transactions are in the blockchain, Armory and Core must build separate (they can't share databases) databases to keep track of where everything is in the blockchain.
gaglia
newbie
Activity: 28
Merit: 0
Re: Cannot start Armory on Linux Debian, stuck on "Preparing Databases"
July 02, 2017, 05:05:54 PM
#6
Some updates: I realized I was still running an old version of Debian, forgot to update to the new stable... So I did the update, and consequently all the libraries needed for the GCC 5.3 version were also updated. However: the latest build you mentioned, achow101 does not ship with icons and integration in the Gnome menu. Anyway, at least the 0.96.0 version with GCC 5.3 (default download from Armory website) seems to work now, or at least it's not stuck at 0% anymore. It predicts a few hours until the end of "Building Databases", although I'm not sure what this means... what databases is Armory building? Doesn't it use the same blockchain as in the .bitcoin directory?

I'm not marking this as solved yet, need to see if it completes successfully...
Pages:
Bitcoin Forum>Bitcoin>Development & Technical Discussion>Wallet software>Armory
Jump to: