Topic: stuck or good? (Read 2126 times)
Is there an expectation when 0.94 is officially being released?
Thank you 
! But I was thinking that bitcoinqt should at least show it, but it's probably the same issue.
! But I was thinking that bitcoinqt should at least show it, but it's probably the same issue.Core does not know of the public keys at all. Only Armory is aware of those. The same works vice versa. If you sent those coins to an address generated through BitcoinQt, Armory would not be aware of it. Armory and Core wallets are completely separate entities.
Thank you ! But I was thinking that bitcoinqt should at least show it, but it's probably the same issue.
Rebuild and rescan is running again....
! But I was thinking that bitcoinqt should at least show it, but it's probably the same issue.Rebuild and rescan is running again....
Oke thx.
One last 'stupid' question.
Someone send me bitcoins to an address that I got from armory. When verifying online it shows that it is received.
But, bitcoinqt (seems not having any trouble) and armory didnt show this in my wallet? Whats causing this or am I missing a piece of the puzzle? Or is it because it's corrupted in some way?
One last 'stupid' question.
Someone send me bitcoins to an address that I got from armory. When verifying online it shows that it is received.
But, bitcoinqt (seems not having any trouble) and armory didnt show this in my wallet? Whats causing this or am I missing a piece of the puzzle? Or is it because it's corrupted in some way?
Your coins are here, rest assured. The particular issue your log file is exposing is that Armory believes the blockchain has stopped around block 270XXX, which is like 2 years ago or something. So obviously, it never got to see the blocks from 2015, thus any transaction from that period.
Oke thx.
One last 'stupid' question.
Someone send me bitcoins to an address that I got from armory. When verifying online it shows that it is received.
But, bitcoinqt (seems not having any trouble) and armory didnt show this in my wallet? Whats causing this or am I missing a piece of the puzzle? Or is it because it's corrupted in some way?
One last 'stupid' question.
Someone send me bitcoins to an address that I got from armory. When verifying online it shows that it is received.
But, bitcoinqt (seems not having any trouble) and armory didnt show this in my wallet? Whats causing this or am I missing a piece of the puzzle? Or is it because it's corrupted in some way?
Sorry, you have to build from source right now.
Oke! Is there a build version available to download for win7 somewhere?
At this point you are better off doing a Rebuild and Rescan.
I'm aware of all these issues and they all been thoroughly fixed in 0.94
I'm aware of all these issues and they all been thoroughly fixed in 0.94
its a continues bitcoinqt problem....everytime it seem to hang it mostly missed a bitcoinqt connection....
But it seems also very very slow in processing....
What hardware is suggested to make armory work the way it's intended and workable?
btw, lastest part of log:
Repairing database gave me 'nothing to repair'
But it seems also very very slow in processing....
What hardware is suggested to make armory work the way it's intended and workable?
btw, lastest part of log:
Quote
NFO - 1440834274: (..\lmdb_wrapper.cpp:478) Opening databases...
-INFO - 1440834275: (..\BlockUtils.cpp:1226) Executing: doInitialSyncOnLoad
-INFO - 1440834291: (..\BlockUtils.cpp:1297) Total number of blk*.dat files: 326
-INFO - 1440834291: (..\BlockUtils.cpp:1298) Total blockchain bytes: 43,682,935,981
-INFO - 1440834291: (..\BlockUtils.cpp:1671) Reading headers from db
-INFO - 1440834392: (..\BlockUtils.cpp:1697) Found 371831 headers in db
-DEBUG - 1440834392: (..\Blockchain.cpp:211) Organizing chain w/ rebuild
-WARN - 1440846304: (..\BlockUtils.cpp:1327) --- Fetching SSH summaries for 107 registered addresses
-WARN - 1440846318: (..\BlockUtils.cpp:246) Couldn't find top block hash in last seen blk file. Searching for it further down the chain
-WARN - 1440846699: (..\BlockUtils.cpp:304) Inconsistent headers DB, attempting repairs
-INFO - 1440846699: (..\BlockUtils.cpp:1340) Left off at file 0, offset 0
-INFO - 1440846699: (..\BlockUtils.cpp:1343) Reading headers and building chain...
-INFO - 1440846699: (..\BlockUtils.cpp:1344) Starting at block file 0 offset 0
-INFO - 1440846699: (..\BlockUtils.cpp:1346) Block height 273724
-ERROR - 1440846928: (..\BlockUtils.cpp:639) Next block header found at offset 41946931
-DEBUG - 1440847394: (..\Blockchain.cpp:211) Organizing chain w/ rebuild
This takes ages, not hours -INFO - 1440834275: (..\BlockUtils.cpp:1226) Executing: doInitialSyncOnLoad
-INFO - 1440834291: (..\BlockUtils.cpp:1297) Total number of blk*.dat files: 326
-INFO - 1440834291: (..\BlockUtils.cpp:1298) Total blockchain bytes: 43,682,935,981
-INFO - 1440834291: (..\BlockUtils.cpp:1671) Reading headers from db
-INFO - 1440834392: (..\BlockUtils.cpp:1697) Found 371831 headers in db
-DEBUG - 1440834392: (..\Blockchain.cpp:211) Organizing chain w/ rebuild
-WARN - 1440846304: (..\BlockUtils.cpp:1327) --- Fetching SSH summaries for 107 registered addresses
-WARN - 1440846318: (..\BlockUtils.cpp:246) Couldn't find top block hash in last seen blk file. Searching for it further down the chain
-WARN - 1440846699: (..\BlockUtils.cpp:304) Inconsistent headers DB, attempting repairs
-INFO - 1440846699: (..\BlockUtils.cpp:1340) Left off at file 0, offset 0
-INFO - 1440846699: (..\BlockUtils.cpp:1343) Reading headers and building chain...
-INFO - 1440846699: (..\BlockUtils.cpp:1344) Starting at block file 0 offset 0
-INFO - 1440846699: (..\BlockUtils.cpp:1346) Block height 273724
-ERROR - 1440846928: (..\BlockUtils.cpp:639) Next block header found at offset 41946931
-DEBUG - 1440847394: (..\Blockchain.cpp:211) Organizing chain w/ rebuild
Repairing database gave me 'nothing to repair' To make sure I understand.. Since I can't run bitcoind as a background process started from Armory, in order to keep an Armory wallet on my computer, I have to keep Bitcoin Core and Armory running side-by-side constantly..?
For Armory to go online, it needs a local instance of Core. If auto bitcoind is failing, you will have to Start BitcoinQt manually prior to starting Armory every time. It is critical that BitcoinQt is fully sync'd before you start Armory, so if you have not run Core in a few days, let it catch up before you start Armory.
Quote
Latest thing I'm having now: I start Armory and it seems suddenly stuck at organizing blockchain ?!
Log files please
Quote
any suggestions on trouble-shooting bitcoind crashing when started from Armory?
Probably something to do with your /blocks or binary path (the ones in File -> Settings). It is either getting mangled or it's invalid (non ASCII chars?). Auto bitcoind is a feature for default setups, i.e. you didn't customize your system and installation at all. If you intent to customize (like you did), I strongly suggest against using auto bitcoind.
To make sure I understand.. Since I can't run bitcoind as a background process started from Armory, in order to keep an Armory wallet on my computer, I have to keep Bitcoin Core and Armory running side-by-side constantly..?
EDIT: any suggestions on trouble-shooting bitcoind crashing when started from Armory?
EDIT: any suggestions on trouble-shooting bitcoind crashing when started from Armory?
Oke, using bitcoinqt worked. Took ages but it worked. Started armory and after a while it worked, however...
Sometimes closing armory fails, I need to start bitcoinqt en try to close again.
Latest thing I'm having now: I start Armory and it seems suddenly stuck at organizing blockchain ?!
Sometimes closing armory fails, I need to start bitcoinqt en try to close again.
Latest thing I'm having now: I start Armory and it seems suddenly stuck at organizing blockchain ?!
goatpig can correct me if I'm wrong but my understanding of this is that your blockchain is corrupt. Long story short, Bitcoin uses LevelDB to organize the blockchain, and LevelDB is a massive pile of junk. (Armory also used LevelDB from 0.90-0.92. 0.93 uses LMDB, which is much saner. Anyway....) LevelDB can be easily corrupted, especially on Windows. So, you may have to download the blockchain again and hope for the best.
Again, goatpig can correct me if I'm wrong, and give you more specific advice.
Oke, using bitcoinqt worked. Took ages but it worked. Started armory and after a while it worked, however...
Sometimes closing armory fails, I need to start bitcoinqt en try to close again.
Latest thing I'm having now: I start Armory and it seems suddenly stuck at organizing blockchain ?!
Sometimes closing armory fails, I need to start bitcoinqt en try to close again.
Latest thing I'm having now: I start Armory and it seems suddenly stuck at organizing blockchain ?!
That seems to be working. With Bitcoin Core running standalone, and synced, Armory spent a few minutes "Reading New Block Headers", then "Scan Transaction History".. Then "Building databases", for 20 minutes with progress moving. Now it's "Scanning Transaction History" - will take some 40 minutes. Awesome! Hopefully the root cause and messaging to end user about it can be figured out. Thanks for the help!!
From your log file, it appears bitcoind is crashing when Armory is trying to start it. I guess it probably has something to do with permissions on the folder holding the binary (exec permission probably). That or the blockchain folder Armory passes as an argument is getting mangled somehow.
For now, turn off auto bitcoind management. To do so, start Armory, go to File -> Settings and uncheck the first checkbox (you should also to a Help -> Rebuild and Rescan for the good measure). Close Armory, start BitcoinQt manually, then start Armory again, it should pick up from there.
For now, turn off auto bitcoind management. To do so, start Armory, go to File -> Settings and uncheck the first checkbox (you should also to a Help -> Rebuild and Rescan for the good measure). Close Armory, start BitcoinQt manually, then start Armory again, it should pick up from there.
Yes, Armory still stuck and Bitcoin Core fully synced. I have the log file. Will send PM.
If it is fully synced and Armory is still stuck, I'll need to see a log file.
Bitcoin Core finished overnight, and reports up-to-date. However, Armory still refuses to get past the "Build databases" stage. I tried to submit a bug report - but it also failed. I am on Windows 10. Maybe that's why Armory no longer works.
someone else had a perpetual 0% problem like this, Armory was looking in the wrong place for the Bitcoin Core database files. I'll see if I can find the thread and link you to it
Bitcoin Core finished overnight, and reports up-to-date. However, Armory still refuses to get past the "Build databases" stage. I tried to submit a bug report - but it also failed. I am on Windows 10. Maybe that's why Armory no longer works.
Armory needs to build its own databases, and from a fresh sync, that will also take a long time. The first startup of Armory always takes ages but after that it should not take that long.
Bitcoin Core finished overnight, and reports up-to-date. However, Armory still refuses to get past the "Build databases" stage. I tried to submit a bug report - but it also failed. I am on Windows 10. Maybe that's why Armory no longer works.
Jump to: