|
Run armory from the command line and post the result.
|
|
|
|
|
1) Don't use 0.96, it's old.
2) You can't have non ASCII characters in your paths.
|
|
|
|
|
Update, you're using an old version.
|
|
|
|
|
You have to import the private keys into your offline wallet, get a new WO off of that and sync the online side with that new wallet. Then you can create a transaction to get back to the offline wallet to sign with.
|
|
|
|
|
No, don't use those if you plan on exporting your private keys in the future.
|
|
|
|
|
Export the private keys, import them in another piece of software.
|
|
|
|
|
Consider setting up a Ubuntu VM on your Mac and installing Armory in there.
|
|
|
|
|
Have not looked at it. Unless they become relevant, I most likely won't be looking.
|
|
|
|
|
The signer is updated as well?
|
|
|
|
|
1) Upgrade, you're using an over a year old version.
2) Make sure your user has read write permissions in that folder.
|
|
|
|
|
What is your system locale? You can't have non ASCII characters in your paths.
|
|
|
|
Oops, of course you are right, my armorydb service stopped..
Thanks, now I know how that looks like too! :-)
Did it crash or did you stop it on your own? |
|
|
|
Question : If we loose the wallet but i see that somehow we still store the private key and multiplier in the app data of armory for every recieving address generated for every wallet , is there a way i can use these to restore the deleted wallet or some way of getting hold of my lost wallet ?
The multipliers are basically useless. You need the private keys. |
|
|
|
After two weeks, suddenly Armory doesn't load up properly any more. The GUI hangs at "preparing databases". The shell says -ERROR - ���iGx: (SwigClient.cpp:61) ser/deser type error:
expected type id: 4
got type id: 0 instead
..with changing random bytes in the first line. Armorydb is on a remote host. I didn't change anything that I know of lately. Anything I can do except updating to 0.06.4R1? Thank you, ente It's trying to register with the DB and gets an empty message in return. Make sure the http daemon is running properly. Alternatively you can 0.96.4 and get rid of the http daemon part. |
|
|
|
Did you warn people not to upgrade to 0.15.0.1?
0.96.4 has a fix for that. |
|
|
|
|
Show Posts
