It's an online machine, and I used the Armory Installer
No x86 online for 0.93. Go back to 0.92.3 and wait for the next release for x86 Odd, your website lists 0.93 for Ubuntu 12.04+ (32bit), I thought your binaries would be compatible...  I guess I'll just install it on my 64 bit machine Yeah we forgot to rename all that stuff, sorry about that =( |
|
|
|
If you want to forcefully trigger the issue, you can point Armory to a copy of the blockchain it wasn't sync'ed against. Core 0.10 chains will definitely trigger it.
Instead of doing that, I decided to see what would happen if I just deleted the most recent block file (blk00238.dat) entirely. Turns out that Armory can't repair that. That's an interesting approach. First of all Armory is not supposed to recover from that. It expects to always start at the same or higher height than it saw on its last run. If it fails to find its highest known block, that's an acceptable condition to fail and ask for a factory reset. I don't think it should step away from that assumption at the risk of rolling back history or failing to detect newly available blocks, which are issues harder to identify. The weird thing about your log is that you say you deleted the most recent block file, yet Armory detected 239 available block files, which deserves an investigation on its own. |
|
|
|
|
Log says it's working currently
|
|
|
|
Also have not been a been able to trigger a repair log entry.
Everything just works so far.
Also have not been a been able to trigger a repair log entry.
Everything just works so far.
As long as it works I'm happy. If you want to forcefully trigger the issue, you can point Armory to a copy of the blockchain it wasn't sync'ed against. Core 0.10 chains will definitely trigger it. |
|
|
|
|
Delete your log files and Armory's databases folder. Start Armory with your wallet loaded from the start and let it go all the way, then post your log files.
|
|
|
|
|
I need to see armoryccplog.txt
|
|
|
|
Will support for HW1 be eventually added in the near future?
Yeah that's the plan, but we have to get this new DB under control first. |
|
|
|
I think I'm all good now after updating to fixes branch. Thanks!
Post that in the other thread so I can keep track =) |
|
|
|
It's an online machine, and I used the Armory Installer
No x86 online for 0.93. Go back to 0.92.3 and wait for the next release for x86 |
|
|
|
Ok, that seemed to do the trick. Armory is connecting and building the databases now. However, Armory is still insisting on building the databases in the default folder "C:\Users\owner\appdata\roaming\Armory". I have changed the folder in the settings menu to no avail. Is there a similar argument that will change the default database folder?
Can't set that in the setting menu. use --dbdir instead |
|
|
|
Yes, I am
Are you trying to use Armory on this machine as an offline signer or to get online? |
|
|
|
Thank you As I don't know how to build the version mentioned in this link, I will wait until next release, so...  Should be soon, hang in there. |
|
|
|
Tried installing 0.93 on Ubuntu 14.04 and it errored out saying it couldn't install python-gtk2:i386 and Ubuntu Software Center disappeared from my system, along with many apps (VirtualBox, Dropbox, Okular...), what am I missing?
You are using a 32bit OS? |
|
|
|
Hi,
I keep getting the error "Armory scanning interrupted unexpectedly". Armory then asks me to check the box to re-scan and rebuild the database on next time Armory starts. If I do not check the box I get prompted with the same error on restart. This happened two times already in the last few days.
I'm running the latest armory on 64-bit linux with 16gb ram. My internet connection is fairly slow though, especially upload speed.
https://bitcointalk.org/index.php?topic=970983.0 |
|
|
|
The unscanned block numbers 345607 to 345717 roughly correspond with the timestamps in the log file I sent you, that's why I'm guessing it wasn't on the top block.
Edit: sorry I'm wrong, 345607 was the most recent block after initially starting Armory (in the logs I sent). The odd logging symptom didn't start until a couple of hours later, so I'm not sure how to interpret the log pasted in above.
Is it displaying the correct top block now? |
|
|
|
I just sent a bug report which I think contains log files. I have looked through all over Armory and I don't see a way to actually read the log files. It probably wouldn't make any sense to me anyway since I am a newbie.
Are my coins lost forever or can I recover them if I get the program to work? The wallet is restored and in perfect condition. I just can't get Armory to connect even though it says it is with 0 blocks downloaded.
Your coins are fine. Syncing Armory and wallet security are 2 different things. I'll respond to your ticket from the support channel. |
|
|
|
Sorry, I should have been more specific. Ticket: ARMORY00000469, I did mention your name in the ticket body.
This looks like a benign symptom of the same general issue. Did you make sure Armory was displaying the proper top block? |
|
|
|
|
Show Posts
