Topic: Upgrade information needed (Read 283 times)

Finished reindexing yet?

2018-01-18 22:50:48 Loaded 749 blocks from external file in 20216ms
2018-01-18 22:50:48 Reindexing block file blk00100.dat...

That would probably explain why your block count has been stuck.
Yes, generally the right thing to do, though will take some time. If you open up "D:\BTC datadir 96-2\debug.log" and look at the end of the file you should be able to see how it is progressing.

The bitcoin core error message indicated a corrupted database. It prompted me to let it rebuild the database, so I am rebuilding it. Is that the right procedure?

Sorry, that should have been:

Usually bitcoind is run from Armory, instead of bitcoin-qt, to update the blockchain. Something has been going wrong down the line there. Hoping that running qt manually on that directory will tell us more.

error: Specified data directory "D:\BTC" does not exist.
Is it possible that a different version of bitcoin-qt is running? Maybe it isn't running at all. I wouldn't be surprised if the db hasn't been updated in some time.

Going on your logs, you have a few issues. Increasing the fee isn't going to help if your Armory can't communicate with the network.
If I'm reading this right:
The Bitcoin blockchain and chainstate is downloaded to D:\BTC datadir 96-2\ (blocks and chainstate subfolder)
Armory is installed to D:\BTC datadir 96-2\Armory\

While it could work as is, nesting these folders is not a great idea. Please consider moving/reinstalling Armory outside this directory.

Unless you've fixed it you recently starting passing in this to Armory (As part of a shortcut?):
This is incorrect. Space between "--" and "datadir", and as far as I understand it, d:\btc datadir 96-2\ is your satoshi/bitcoin data directory, not your datadir (armory). Did you mean to pass it to Bitcoin Core?


From further back in your logs Armory has been scanning the blocks in D:\BTC datadir 96-2\blocks and can't find any more after #494345.
Are you sure Bitcoin Core has got an up to date copy of the blockchain in D:\BTC datadir 96-2\blocks ? Also saw a reference to D:\Bitcoin? A backup/original copy?

Close down Armory, check task manager for bitcoind and armorydb (kill them if they are there).
Then run this, please:
Bitcoin Core should open up. Wait for it to load then go to Help -> Debug window.
On the "Information" tab, what does it say next to "Current Number of blocks" ? If it isn't 504876 or higher, that copy of the blockchain is not up to date.

Is it possible that I'm not syncing up to the network correctly? After the upgrade, the error message is that the node is offline. I increased the fee to 1100 s/Byte with the same result.
 I did upgrade the watching node to 0.96.3.992

I found armory_0.96.3.992_win64.exe on the page titled 0.96.4 RC3

Please upgrade the online machine to 0.96.4 RC3, kill ArmoryDB if it's still in the task manager, and try again.

logs
https://pastebin.com/uK9jhvL0
https://pastebin.com/iPjyPKyY
https://pastebin.com/rP9VxNBG
https://pastebin.com/1JWMCt3M

Thanks.
Well on your offline, I'd create a copy of the Armory folder in C:\Users\YourNameHere\AppData\Roaming and rename C:\Program Files\Armory\ ArmoryOld, then as a worst case scenario you could just roll back.
32bit... yeah that does matter, thinking about it. 32bit should work, but there aren't any official windows 32bit builds available for 0.96.4 at the moment. 0.96.2 is available for 32bit windows, though.
Posting your logs will still help give info, but without that and in your case, I'd recommend upgrading to 0.96.2 on your online and offline pc and see how that goes.
Could need a rebuild of the Armory database too, but try the less time consuming suggestions first.

I will post the log files in a few minutes. bitcoin-0.14.2-win64
Also, what is the procedure forupgrading the signer? It's win7 32-bit -- does that matter?

Sorry, was mobile before so my response was a bit brief.
We need full logs, not just the last snippets. Add dblog.txt and armorylog.txt to pastebin (or a site of your choice) and post the links here, please. And privacy issues are your username and some debug info about your hardware.
Which version of Bitcoin Core are you using? I vaguely remember older versions of Armory choking on newer versions of Core, but not completely sure.
Are you dead set on not upgrading your offline setup? That offline signer is really old now - 2 years ish?

Log file opened at 1516223335: C:\Users\enduser\AppData\Roaming\Armory\dbLog.txt
-INFO  - 1516223336: (..\main.cpp:23) Running on 2 threads
-INFO  - 1516223336: (..\main.cpp:24) Ram usage level: 4
-INFO  - 1516223336: (..\BlockUtils.cpp:907) blkfile dir: D:\BTC datadir 96-2\blocks
-INFO  - 1516223336: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\enduser\AppData\Roaming\Armory\databases
-INFO  - 1516223337: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 1516223338: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO  - 1516223338: (..\DatabaseBuilder.cpp:169) Reading headers from db
-INFO  - 1516223339: (..\BDM_Server.cpp:996) registered bdv: cf606b45d9d2e08b4a5e
-INFO  - 1516223347: (..\DatabaseBuilder.cpp:208) Found 494345 headers in db
-INFO  - 1516223353: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO  - 1516223355: (..\DatabaseBuilder.cpp:477) Found next block after skipping 975916bytes
-INFO  - 1516223356: (..\DatabaseBuilder.cpp:268) parsed block file #1061
-DEBUG - 1516223356: (..\Blockchain.cpp:242) Organizing chain
-INFO  - 1516223356: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 2.371s
-INFO  - 1516223356: (..\DatabaseBuilder.cpp:106) scanning new blocks from #494345 to #494344
-INFO  - 1516223356: (..\BlockchainScanner.cpp:52) no history to scan
-INFO  - 1516223356: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO  - 1516223356: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.019s
-INFO  - 1516223356: (..\DatabaseBuilder.cpp:160) init db in 18.355s
-INFO  - 1516223356: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking
-ERROR - 1516223364: (..\SocketObject.cpp:285) POLLERR error in readFromSocketThread
-ERROR - 1516223364: (..\BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: POLLERR error in readFromSocketThread
-ERROR - 1516223616: (..\SocketObject.cpp:126) poll() error in writeToSocket: 10038


Log file opened at 1516227852: C:\Users\enduser\AppData\Roaming\Armory\dbLog.txt
-INFO  - 1516227852: (..\main.cpp:23) Running on 2 threads
-INFO  - 1516227852: (..\main.cpp:24) Ram usage level: 4
-INFO  - 1516227852: (..\BlockUtils.cpp:907) blkfile dir: D:\BTC datadir 96-2\blocks
-INFO  - 1516227852: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\enduser\AppData\Roaming\Armory\databases
-INFO  - 1516227852: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 1516227853: (..\BDM_Server.cpp:996) registered bdv: c2fc4353e8e85cc80733
-INFO  - 1516227856: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO  - 1516227858: (..\DatabaseBuilder.cpp:169) Reading headers from db
-ERROR - 1516227883: (..\SocketObject.cpp:285) POLLERR error in readFromSocketThread
-ERROR - 1516227883: (..\BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: POLLERR error in readFromSocketThread
-INFO  - 1516227884: (..\DatabaseBuilder.cpp:208) Found 494345 headers in db
-INFO  - 1516227888: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO  - 1516227889: (..\DatabaseBuilder.cpp:477) Found next block after skipping 975916bytes
-INFO  - 1516227890: (..\DatabaseBuilder.cpp:268) parsed block file #1061
-DEBUG - 1516227890: (..\Blockchain.cpp:242) Organizing chain
-INFO  - 1516227890: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 2.208s
-INFO  - 1516227890: (..\DatabaseBuilder.cpp:106) scanning new blocks from #494345 to #494344
-INFO  - 1516227890: (..\BlockchainScanner.cpp:52) no history to scan
-INFO  - 1516227890: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO  - 1516227890: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.08s
-INFO  - 1516227890: (..\DatabaseBuilder.cpp:160) init db in 33.268s
-INFO  - 1516227890: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking

Why email it? There's no sensitive info in the logs, unless you consider the username on your PC to be sensitive.

Log file opened at 1516227852: C:\Users\enduser\AppData\Roaming\Armory\dbLog.txt
-INFO  - 1516227852: (..\main.cpp:23) Running on 2 threads
-INFO  - 1516227852: (..\main.cpp:24) Ram usage level: 4
-INFO  - 1516227852: (..\BlockUtils.cpp:907) blkfile dir: D:\BTC datadir 96-2\blocks
-INFO  - 1516227852: (..\BlockUtils.cpp:908) lmdb dir: C:\Users\enduser\AppData\Roaming\Armory\databases
-INFO  - 1516227852: (..\lmdb_wrapper.cpp:388) Opening databases...
-INFO  - 1516227853: (..\BDM_Server.cpp:996) registered bdv: c2fc4353e8e85cc80733
-INFO  - 1516227856: (..\BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO  - 1516227858: (..\DatabaseBuilder.cpp:169) Reading headers from db
-ERROR - 1516227883: (..\SocketObject.cpp:285) POLLERR error in readFromSocketThread
-ERROR - 1516227883: (..\BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: POLLERR error in readFromSocketThread
-INFO  - 1516227884: (..\DatabaseBuilder.cpp:208) Found 494345 headers in db
-INFO  - 1516227888: (..\DatabaseBuilder.cpp:51) updating HEADERS db
-INFO  - 1516227889: (..\DatabaseBuilder.cpp:477) Found next block after skipping 975916bytes
-INFO  - 1516227890: (..\DatabaseBuilder.cpp:268) parsed block file #1061
-DEBUG - 1516227890: (..\Blockchain.cpp:242) Organizing chain
-INFO  - 1516227890: (..\DatabaseBuilder.cpp:56) updated HEADERS db in 2.208s
-INFO  - 1516227890: (..\DatabaseBuilder.cpp:106) scanning new blocks from #494345 to #494344
-INFO  - 1516227890: (..\BlockchainScanner.cpp:52) no history to scan
-INFO  - 1516227890: (..\BlockchainScanner.cpp:813) no SSH to scan
-INFO  - 1516227890: (..\DatabaseBuilder.cpp:156) scanned new blocks in 0.08s
-INFO  - 1516227890: (..\DatabaseBuilder.cpp:160) init db in 33.268s
-INFO  - 1516227890: (..\BlockUtils.cpp:1206) Enabling zero-conf tracking

Might be a compatibility issue then... might not. Post your Armory logs please.
Fees vary, but this is a decent resource for seeing what the going rate is https://dedi.jochen-hoenicke.de/queue/more/#24h

I have attempted to broadcast a signed transaction, but it errors out: armorydb.exe stopped. Any ideas as to how to fix this? I have had the same error come up about five times on the same transaction. btw, what is the rate for sending BTC? I tried 50, and then 850 s/Byte

If you don't use Segwit or Armory's P2SH-P2PK address options (may not be present in 0.96), Then there will be no incompatibility.

I have watching wallet on Win10 0.96-beta and offline wallet on Win7 32-bit 0.92.3
How will I proceed when the time comes to sign transactions? These two version are not compatible, I am guessing? Probably should have asked for an upgrade roadmap prior to upgrading the watching wallet to 0.96-beta.