Topic: Bitcoin Armory failed to spawn ArmoryDB (Read 67 times)

Can you start ArmoryDB from the command prompt and see if it chokes?

Can you list the things you've tried so far?
That's necessary so users won't suggest what you've already tried.

For the follow-up, since it's seems normal and there's not enough info in armorylog.txt, I honestly can't find the issue.
It couldn't be the blocks based from the logs, that's as far as I can tell.

I'musing the most current version of Armory.

This was in dbLog.txt:

Log file opened at 22:38:33.000: C:\Users\Christopher\AppData\Roaming\Armory\dbLog.txt
-INFO  - 22:38:33.000: (e:\users\goat\code\armory3\cppforswig\main.cpp:32) Running on 4 threads
-INFO  - 22:38:33.000: (e:\users\goat\code\armory3\cppforswig\main.cpp:33) Ram usage level: 50
-INFO  - 22:38:33.000: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:915) blkfile dir: I:\Bitcoin Blockchain\blocks
-INFO  - 22:38:33.000: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:916) lmdb dir: C:\Users\Christopher\AppData\Roaming\Armory\databases
-INFO  - 22:38:33.000: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 22:38:33.015: (e:\users\goat\code\armory3\cppforswig\bdm_server.h:263) Listening on port 50583
-INFO  - 22:39:15.011: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:1108) Executing: doInitialSyncOnLoad
-INFO  - 22:39:20.221: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:199) Reading headers from db
-INFO  - 22:40:37.457: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:238) Found 691513 headers in db
-INFO  - 22:40:43.713: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:64) Rewinding 100 blocks
-INFO  - 22:40:43.713: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:71) updating HEADERS db
-INFO  - 22:40:43.728: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:493) Found next block after skipping 467695bytes
-INFO  - 22:40:45.647: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #2656
-INFO  - 22:40:46.396: (e:\users\goat\code\armory3\cppforswig\blockchain.cpp:248) Organizing chain
-INFO  - 22:40:46.474: (e:\users\goat\code\armory3\cppforswig\blockchain.cpp:370) Organized chain in 0s
-INFO  - 22:40:46.490: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:76) updated HEADERS db in 2s
-INFO  - 22:40:46.521: (e:\users\goat\code\armory3\cppforswig\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 22:40:46.536: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:1231) verifying txfilters integrity
-INFO  - 22:46:26.885: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:1314) done checking txfilters
-INFO  - 22:46:26.932: (e:\users\goat\code\armory3\cppforswig\bdm_supportclasses.cpp:1891) Enabling zero-conf tracking


I don't know if there's anything useful there I don't see any errors like I used to. I've been trying quite a few different things with no luck. Starting to think maybe delete everything and start over. I was hoping to avoid having to download the blockchain again, could a problem with that cause something like this do you think?

dbLog.txt contains logs, there nothing to change there.
Upon examining the thread: martyman just posted what was in the command line after running armorydb manually.
I've also noticed that the linked thread was quite chaotic because there were other two posters who claimed to have the "same issue" but didn't seem like it. And they replied after one another.

The "glitch" may have been a "zombie armorydb" process that wasn't terminated after the last Armory session.
In that case, a PC restart, end task or the manual armorydb launch attempt(s) might have fixed the issue.

Possible only glitch problem, not passing the correct data-dir through to ArmoryDB. Same case like This and has resolved when he changes form databases to dbLog.txt

What version of Armory are you using? You should be using the latest version 0.96.5.

Your log says ArmoryQt couldn't launch ArmoryDB.exe by itself but there are no other useful info.
You may need to check the other log file: "dbLog.txt" for additional info why it's failing to run.

I've also ask a Moderator to move this to Armory board so the developer himself can look at the issue.

So I keep having this issue and was wondering if anyone could lend a hand. I've searched for possible solutions and tried a few and still haven't been able to solve it.

(ERROR) ArmoryUtils.pyc:3735 - Unsupported language  specified. Defaulting to English (en)
(WARNING) ArmoryQt.py:2147 - ***WARNING: Duplicate wallet detected, 2Vc1i7BZR
(WARNING) ArmoryQt.py:2158 - Second wallet is more useful than the first one...
(WARNING) ArmoryQt.py:2159 -      Wallet 1 (skipped): C:\Users\Christopher\AppData\Roaming\Armory\armory_2Vc1i7BZR_decrypt.wallet
(WARNING) ArmoryQt.py:2160 -      Wallet 2 (loaded):  C:\Users\Christopher\AppData\Roaming\Armory\armory_2Vc1i7BZR_.wallet
(WARNING) SDM.pyc:445 - Spawning bitcoind with command: C:\Program Files\Bitcoin\daemon\bitcoind.exe -datadir=I:\Bitcoin Blockchain
(WARNING) SDM.pyc:402 - Spawning DB with command: C:\Program Files (x86)\Armory\ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="I:\Bitcoin Blockchain\blocks" --satoshi-port=8333 --datadir="C:\Users\Christopher\AppData\Roaming\Armory\" --dbdir="C:\Users\Christopher\AppData\Roaming\Armory\databases"
(ERROR) ArmoryQt.py:1821 - Failed to spawn ArmoryDB
(WARNING) SDM.pyc:515 - bitcoind exited, bitcoind STDOUT:
(WARNING) SDM.pyc:517 -
(WARNING) SDM.pyc:518 - bitcoind exited, bitcoind STDERR:
(WARNING) SDM.pyc:520 -