Author

Topic: Armory 0.96 odd hanging (Read 364 times)

newbie
Activity: 24
Merit: 2
May 12, 2017, 02:04:42 PM
#3
Hmmm. I use the standard file structure, everything in default positions. The working VM uses the same versions. Only difference is, it is Intel (tho running the 64-bit "AMD" labelled bitcoind as per the hanging instance on AMD).

My surprise with having to shut down bitcoind in order to restart Armory isn't that it wasn't shut down (makes sense if Armory is unhappy) but that its running would prevent Armory restarting. I had  assumed it would be fine with that.

I just tried a reboot with Armory not handling blitcoind in the backgrpound (box unchecked), running d from terminal, then starting Armory, but it made no difference, just the same symptoms and cure.

Edit: Just saw your edit. Good news, thanks!
staff
Activity: 3374
Merit: 6530
Just writing some code
May 12, 2017, 12:04:01 PM
#2
This is a known issue, but I'm not sure how to fix it. I have been experiencing the same problem for a long time. It happens because ArmoryQt is unable to connect to ArmoryDB, so when it shuts down, it is unable to shut down ArmoryDB too since there is no connection. ArmoryDB is what handles the bitcoind so that doesn't shut down either.

Edit: goatpig figured it out a few days ago and this issue has been fixed for 0.96.1
newbie
Activity: 24
Merit: 2
May 12, 2017, 12:00:49 PM
#1
Firstly, many thanks to goatpig and the team for continuing with Armory. I've happily been using it as my wallet since 0.88 and have quite enjoyed the tweaking needed to keep it running through the years. I'll be happy to donate when you're ready.

Now running 0.96 with 0.14.1 on unbuntu 14.04, 64bit, 8GB RAM.

When started from re-boot, Armory now always hangs on "Preparing Databases" (with the 2 orange progress bars). When Armory is quitted, it leaves ArmoryDB and bitcoind running. It can't then be re-started until I End Process ArmoryDB and (surprisingly) bitcoind using System Monitor. After that, it will start up fine and quickly be running properly.

After quitting Armory at this point it also properly closes both ArmoryDB and bitcoind.

So it's annoying rather than critical, and I'm really just reporting it rather than screaming for help. It does happen reproducibly, every time I start the machine. I should say that I have exactly (AFAIK) the same setup running in a (Parallels) virtual machine without any problems.



Jump to: