Most likely a race condition in the shutdown process.
This is a likely culprit. Can't confirm if it's the culprit, unfortunately. In any event, thanks for pointing out that ArmoryDB doesn't shut down. I only now noticed this. I'm guessing there's a shutdown signal that's either not sent or is the wrong signal. I'll look into it. Most likely the FCGI library doesn't shutdown its listen socket as expected. |
|
|
|
ArmoryDB is working fine, with all provided paths. Running armory client locally (same linux instance) or from another linux instance is working nicely. Only from Windows client I get this error.
Windows client to linux server? |
|
|
|
|
Most likely a race condition in the shutdown process.
|
|
|
|
|
Is ArmoryDB db running? Chances are it can't resolve your paths. Force the datadir and satoshi-datadir manually.
|
|
|
|
|
I am considering an additional approach to shutting down the DB already. The current DB will not shutdown on its own if the client that spawned it crashes or terminates without sending the shutdown signal. This should cover most other cases.
|
|
|
|
So right now the way to get armory to run is to disable it running core in the options, have core running then start armory?
Fixed in 0.95.1 |
|
|
|
|
Delete the log. Start Armory, do you thing, try again, the db log will be smaller.
|
|
|
|
|
In the Users top menu, pick expert, restart Armory and try again. Post the error message, as well as dbLog.txt and armorylog.txt
|
|
|
|
|
Pull request. The website is open source, the code is available on the gh-pages branch. If you write a patch to modify the page and PR it, I will review it and merge.
|
|
|
|
|
Yes, if you removed python-qt4 after installing Armory, since it is a dependency it should uninstall Armory as well. However I'd imagine dpkg would give you a warning about that. Not sure how apt-get would react here.
I'd suggest using dpkg rather than apt-get to remove packages.
|
|
|
|
|
1) Start Armory. In Files -> Settings, turn off auto bitcoind management (in the first section). Shut it down. Make sure there are no ArmoryDB.exe nor bitcoind.exe process running before proceeding to the next step.
2) Delete your databases folder: C:\Users\Zeeshan\AppData\Roaming\Armory\databases
3) Start BitcoinQt manually, let it sync with the network.
4) Start ArmoryDB manually: open the command line, browse to the Armory binaries folder (C:\Program Files (x86)\Armory\ by default), run ArmoryDB.exe. Your log file indicates you don't use custom paths or arguments, so that alone should do it.
5) Start ArmoryQt the regular way. It will find the DB instance on its own and start showing you progress information.
If it fails at any stage, post your dbLog.txt (found here: C:\Users\Zeeshan\AppData\Roaming\Armory).
|
|
|
|
|
Delete your databases folder, try again. Make sure there is no ArmoryDB process running in the background before you do any of that.
|
|
|
|
|
What you see in the Armory log are actual C style time stamps. So there is time, just not human readable =D
I just realized your computer has very little RAM (4GB). It's very possible Core and Armory are fighting over RAM. I'd suggest you reduce the ram usage of ArmoryDB and observe it.
Start ArmoryDB manually, lower the ram use with this command line argument: --ram_usage=1 (defaults to 4). If it's still failing, delete your databases folder, then add this cli arg: --db-type=DB_BARE
|
|
|
|
|
ArmoryQt will basically crash in its current state if the underlying communication with ArmoryDB is severed, or ArmoryDB itself hangs. The most likely reason is that Bitcoin is not running, or that ArmoryDB can't connect to it (maybe because it filled up with other nodes).
Let's see a log file if anything. I want dblog.txt in particular.
|
|
|
|
|
Does it work with 0.94.1?
|
|
|
|
|
Show Posts
