Quote from: SimonL on November 16, 2013, 02:58:12 PM

Code:

2013-11-17 00:29 (INFO) -- ArmoryQt.py:1633 - loadWalletsAndSettings
2013-11-17 00:29 (INFO) -- ArmoryQt.py:1680 - Loading wallets...
2013-11-17 00:29 (WARNING) -- armoryengine.py:9074 - ***WARNING: creation of backup was interrupted -- fixing
2013-11-17 00:29 (ERROR) -- ArmoryQt.py:1723 - ***WARNING: Wallet could not be loaded: /home/ferret/.armory/armory_35Fijn44X_.watchonly.wallet (skipping)
...
OSError: [Errno 1] Operation not permitted: '/home/ferret/.armory/armory_35Fijn44X_.watchonly_backup.wallet'

SimonL, you definitely earned your bounty! Thanks for looking into that! The fact that you do have a corrupted/malformed wallet file confirms that this is probably related to the last person who reported this. They removed the corrupted file and the behavior went away. It sounds like perhaps you just need to remove the WO wallet and re-export the watching-only wallet from the offline computer, to replace the corrupted one (it looks like Armory couldn't fix it). Unfortuantely, it doesn't carry the comments with it... will add that as a later feature (to merge wallet files).

Quote from: jyyst on November 16, 2013, 11:32:08 AM

I left Armory on for some time and it's crashed:
Log from console:

Code:

...

Do you have a lot of addresses? This particular crash looks like what happens when Armory gets "swamped" in processing, and falls behind trying to catch up. Still some errors in my error-handling procedures, but I haven't seen it happen under nominal conditions. There's definitely some room for improvement there...

Quote from: jyyst on November 16, 2013, 11:32:08 AM

I don't know is this bug but always when i close Armory:

Code:

-INFO - 1384625610: (BlockUtils.cpp:3999) Saving wallet history for next load
(ERROR) armoryengine.py:13216 - Resetting BDM and all wallets
(WARNING) armoryengine.py:661 - Killing process pid=8379
(ERROR) ArmoryQt.py:4337 - BitcoindNotAvailable: should not happen...
Resetting BlockDataMgr, freeing memory

That's actually somewhat normal. It's an "error" in a code path sense, but simply because something it was trying to do was already done. I should fix the messages...

Quote from: ACVentures on November 16, 2013, 07:17:06 PM

I'm running OSX 10.8, every so often I'll get a dialog saying armory is not in sync because bitcoind/QT is off, however the QT app never quits. My laptop sometimes goes into power save mode, which disables the wifi, I think. Not sure if that has anything to do with it, but I tend to notice it more when waking up my mac. It doesn't just pop up at random while I'm active on it.

Yeah, Armory has always had a problem with this. I think it would be a serious project to fix this. Right now I guess we should add to the documentation that you need to disable sleep/power-save if you want to keep Armory running all the time. However, now that its startup time is dramatically reduced, it's not so terrible to close it when you're done ...

Quote from: cp1 on November 17, 2013, 03:41:31 AM

Quote from: etotheipi on November 15, 2013, 02:37:53 AM

Restoring paper and digital backups without restarting the app

I restored two wallets after building the database. The first rescanned fine. The second hung at 0% after the error:
Traceback (most recent call last):
File "armoryengine.pyc", line 13409, in run
File "armoryengine.pyc", line 13051, in __startRescanBlockchain
WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'I:\\armory\\blkfiles.txt'

After closing and opening Armory the rescan is going now.

Code:

...

Ahh, super interesting. There's a file that stores the scan state, and it's apparently not being released from the previous scan, in order to be opened for the next one. I will look at that. 1x bounty for you!

Quote from: redphlegm on November 17, 2013, 10:43:41 PM

Mac OSX 10.8.5 Crash

Code:

...

Can you please open Armory and use "File"->Export Log File and email the result to support @ bitcoinarmory.com? Those crash reports are pretty much useless for us. It gives us a tiny hint of where the problem is, but the log gives us the whole story. And please use the menu, since there's multiple logs that Armory will collapse into one. Or maybe you can find some interesting error messages in the log and post them here.