Topic: 0.94.1 crashes (Read 1774 times)
0.94 is especially fast for users syncing it for the first time, compared to all previous versions. Although your machine is setting world records: how did you get it to sync up fully in less than 30 minutes? (as the posting times suggest)
Ah, so you have to rewrite stuff. That explains everything. Well for start I feel like it starts faster and certainly uses less disk space 
Wish you all the best in realising your plans and apologize for my sarcasm.
Wish you all the best in realising your plans and apologize for my sarcasm.
I noticed that Armory was removed from bitcoin.org recommended clients list. It's becasue of such overwhelming user-friendliness, or there is something more behind it?
It was removed because my fork is not the official work from ATI, nor does ATI offer links to my versions on their web page. At the same time, I don't have a web page, I just deliver my binaries through the github release feature. In other words, they think the situation is confusing.
No, I don't see how what other websites say or other wallet/client developers do has to do with Armory's software quality.
Your issue sounds strange to me, I'm not having that problem and never have. What does LastDirectory entry in ArmorySettings.txt read?
Your issue sounds strange to me, I'm not having that problem and never have. What does LastDirectory entry in ArmorySettings.txt read?
It means that low quality interface worries me about quality of safety.
LastDirectory | C:/Users/Andrzej/Downloads
I turned option "Let run Bitcoin Core in background" back and Armory read correct directory and synched at last.
It's homedir is down in size from ~65GB to 140MB - that's a nice surprise.
No, I don't see how what other websites say or other wallet/client developers do has to do with Armory's software quality.
Your issue sounds strange to me, I'm not having that problem and never have. What does LastDirectory entry in ArmorySettings.txt read?
Your issue sounds strange to me, I'm not having that problem and never have. What does LastDirectory entry in ArmorySettings.txt read?
Ah I see. Close Armory. Open \ArmorySettings.txt, and alter the SatoshiDatadir line to the correct Bitcoin home directory. Reload Armory. That might work.
It shows correct path, but it only works when "Let Armory run Bitcoin-Core in background" is turned on.
I noticed that Armory was removed from bitcoin.org recommended clients list. It's becasue of such overwhelming user-friendliness, or there is something more behind it?
Such bugs make wonder if this client is still safe at all.
Other day I tried Electrum but I couldn't even run it. I posted bug to github nad they answered "Oh, I just removed some lines cause I thought they are not needed".
I wouldn't be surprised if they one day remove code that checks if Google confirmation code is correct.
You know what I mean?
Ah I see. Close Armory. Open \ArmorySettings.txt, and alter the SatoshiDatadir line to the correct Bitcoin home directory. Reload Armory. That might work.
Are your wallet files in the Armory home directory? There's one line in that output that reads "No history to scan". That implies no wallet file is being read.
Yes, but Core directory isn't default - please see my previous post edit.
Are your wallet files in the Armory home directory? There's one line in that output that reads "No history to scan". That implies no wallet file is being read.
Code:
Log file opened at 1466953544: C:\Users\Andrzej\AppData\Roaming\Armory\armorycpplog.txt
-INFO - 1466953544: (..\BlockUtils.cpp:924) blkfile dir: C:\Users\Andrzej\AppData\Roaming\Bitcoin\blocks
-INFO - 1466953544: (..\BlockUtils.cpp:925) lmdb dir: C:\Users\Andrzej\AppData\Roaming\Armory\databases
-INFO - 1466953544: (..\lmdb_wrapper.cpp:387) Opening databases...
-INFO - 1466953545: (..\BlockUtils.cpp:1105) Executing: doInitialSyncOnLoad
-INFO - 1466953545: (..\DatabaseBuilder.cpp:162) Reading headers from db
-INFO - 1466953545: (..\DatabaseBuilder.cpp:195) Found 225 headers in db
-INFO - 1466953545: (..\DatabaseBuilder.cpp:43) updating HEADERS db
-INFO - 1466953545: (..\DatabaseBuilder.cpp:223) parsed block file #0
-DEBUG - 1466953545: (..\Blockchain.cpp:213) Organizing chain
-INFO - 1466953545: (..\DatabaseBuilder.cpp:47) updated HEADERS db in 0.021s
-INFO - 1466953545: (..\DatabaseBuilder.cpp:98) scanning new blocks from #225 to #224
-INFO - 1466953545: (..\BlockchainScanner.cpp:65) no history to scan
-INFO - 1466953545: (..\BlockchainScanner.cpp:788) no SSH to scan
-INFO - 1466953545: (..\DatabaseBuilder.cpp:149) scanned new blocks in 0s
-INFO - 1466953545: (..\DatabaseBuilder.cpp:153) init db in 0.024s
-INFO - 1466953545: (..\BlockDataViewer.cpp:155) Enabling zero-conf tracking
-INFO - 1466953544: (..\BlockUtils.cpp:924) blkfile dir: C:\Users\Andrzej\AppData\Roaming\Bitcoin\blocks
-INFO - 1466953544: (..\BlockUtils.cpp:925) lmdb dir: C:\Users\Andrzej\AppData\Roaming\Armory\databases
-INFO - 1466953544: (..\lmdb_wrapper.cpp:387) Opening databases...
-INFO - 1466953545: (..\BlockUtils.cpp:1105) Executing: doInitialSyncOnLoad
-INFO - 1466953545: (..\DatabaseBuilder.cpp:162) Reading headers from db
-INFO - 1466953545: (..\DatabaseBuilder.cpp:195) Found 225 headers in db
-INFO - 1466953545: (..\DatabaseBuilder.cpp:43) updating HEADERS db
-INFO - 1466953545: (..\DatabaseBuilder.cpp:223) parsed block file #0
-DEBUG - 1466953545: (..\Blockchain.cpp:213) Organizing chain
-INFO - 1466953545: (..\DatabaseBuilder.cpp:47) updated HEADERS db in 0.021s
-INFO - 1466953545: (..\DatabaseBuilder.cpp:98) scanning new blocks from #225 to #224
-INFO - 1466953545: (..\BlockchainScanner.cpp:65) no history to scan
-INFO - 1466953545: (..\BlockchainScanner.cpp:788) no SSH to scan
-INFO - 1466953545: (..\DatabaseBuilder.cpp:149) scanned new blocks in 0s
-INFO - 1466953545: (..\DatabaseBuilder.cpp:153) init db in 0.024s
-INFO - 1466953545: (..\BlockDataViewer.cpp:155) Enabling zero-conf tracking
I think I found the bug - Armory open's C:\Users\Andrzej\AppData\Roaming\Bitcoin\blocks - old default directory from years behind.
I have moved it to another partition with more disk space.
I pointed it in Armory settings but they aren't loaded - I guess in case of turned off option "Let Armory run Bitcoin-Core in background"?
That should point to the Bitcoin-Qt/bitcoind home directory, not the Armory home directory. It's where Armory reads the blockchain information from.
Yes it points to Bitcoin Core directory, not Armory directory. I meant Core wallet.
That should point to the Bitcoin-Qt/bitcoind home directory, not the Armory home directory. It's where Armory reads the blockchain information from.
How to rebuild database after upgrade from 0.93.x?
When I remove whole databases dir it continues to crash.
When I remove only contents of that dir Armory runs happily (at last! after 2 days) but doesn't rebuild anything.
When I remove whole databases dir it continues to crash.
When I remove only contents of that dir Armory runs happily (at last! after 2 days) but doesn't rebuild anything.
Check in Settings that Armory is pointed to the correct directory for Bitcoin's blockchain files.
Did you mean option called "Bitcoin Home Dir" in Armory? I turned off Core management as sugested in this thread, but it points to directory where wallet file is stored (same as before upgrade).
How to rebuild database after upgrade from 0.93.x?
When I remove whole databases dir it continues to crash.
When I remove only contents of that dir Armory runs happily (at last! after 2 days) but doesn't rebuild anything.
When I remove whole databases dir it continues to crash.
When I remove only contents of that dir Armory runs happily (at last! after 2 days) but doesn't rebuild anything.
Check in Settings that Armory is pointed to the correct directory for Bitcoin's blockchain files.
How to rebuild database after upgrade from 0.93.x?
When I remove whole databases dir it continues to crash.
When I remove only contents of that dir Armory runs happily (at last! after 2 days) but doesn't rebuild anything.
When I remove whole databases dir it continues to crash.
When I remove only contents of that dir Armory runs happily (at last! after 2 days) but doesn't rebuild anything.
I do, stored the <0.94 Armory database directory there too. I jumped early with SSDs.
No idea how long it will take on a mechanical disk
No idea how long it will take on a mechanical disk
Any way for me to know whether everything is going well? How long should this process take on a 2.4 Ghz 6-core with 4 GB of RAM?
Thanks!
Thanks!
Hour or less I'd guess. Using SSD disks, of course.
You can empty it or remove it. Ideally you want to back up the old DB in case 0.94 gives you a headache, but so far it has proven to be stable so you should be able to go all the way with this.
I'm adding a DB version check in the next release so this kind of issues don't happen anymore.
I'm adding a DB version check in the next release so this kind of issues don't happen anymore.
Let bitcoin resync first.
If you are experience issues with Armory controlling bitcoind, first backup your bitcoin datadir. Then turn off auto managed bitcoind in Armory (first check box in the File -> Settings menu) and run Bitcoin-Qt manually instead.
Once bitcoin is synced, you will have to do a rebuild & rescan in Armory to get it working. Also, do not let 0.94 run in the same dbdir as 0.93's.
If you are experience issues with Armory controlling bitcoind, first backup your bitcoin datadir. Then turn off auto managed bitcoind in Armory (first check box in the File -> Settings menu) and run Bitcoin-Qt manually instead.
Once bitcoin is synced, you will have to do a rebuild & rescan in Armory to get it working. Also, do not let 0.94 run in the same dbdir as 0.93's.
need armorycpplog.txt as well
Logs please.
Hi!
For my watch-only wallet setup I upgraded from an older version (I believe 0.92 but could be 0.93) but it keeps crashing. My bitcoin reference client (Satoshi) is fully synced and the Armory process becomes unresponsive after a while on startup.
I tried renaming the /Armory/databases folder in an attempt to allow Armory to regenerate the tables and left it overnight. It crashed my entire computer (screen was black in the morning but the pc was still running, I had to manually disable the PC). What is my best next course of action?
For my watch-only wallet setup I upgraded from an older version (I believe 0.92 but could be 0.93) but it keeps crashing. My bitcoin reference client (Satoshi) is fully synced and the Armory process becomes unresponsive after a while on startup.
I tried renaming the /Armory/databases folder in an attempt to allow Armory to regenerate the tables and left it overnight. It crashed my entire computer (screen was black in the morning but the pc was still running, I had to manually disable the PC). What is my best next course of action?
Jump to: