I was away from home when the 0.16.3 update became mandatory... and my node effectively just got stuck for 2 weeks
Topic: only 1 second left?? (Read 380 times)
I'm not that surprised. As far as I can tell, older versions of Bitcoin Core just fail to sync properly now...
I was away from home when the 0.16.3 update became mandatory... and my node effectively just got stuck for 2 weeks
I was away from home when the 0.16.3 update became mandatory... and my node effectively just got stuck for 2 weeks
Thank you! That Solved it! (updating to Bitcoin core 16.3.
You're welcome. I'm surprised that alone made a difference but I'm glad it did.Hope it remains problem free for you from now on.
Thank you! That Solved it! (updating to Bitcoin core 16.3.
Thanks for the update as I am running Bitcoin core 16.0. I will update ASAP.
OK, I tried to pull it with the code given above and only got a bunch of gibberish.
Then I pulled it another way. (Note the text at the top almost matches the text line you gave me). It is here https://pastebin.com/JK8WAdzh
Per goatpig.
The last half of the long log file is posted at https://pastebin.com/z4Ve97tY
Thanks for the logs. Definitely odd that the dblog is that short.Then I pulled it another way. (Note the text at the top almost matches the text line you gave me). It is here https://pastebin.com/JK8WAdzh
Per goatpig.
The last half of the long log file is posted at https://pastebin.com/z4Ve97tY
I just realised that nobody has asked which version of Bitcoin Core are you running. Please make sure you do have the latest version (0.16.3) https://bitcoincore.org/en/download/
If it wasn't 0.16.3, it could be helpful to know which version you had installed.
My best guess is still that the Armory database has gotten corrupted somehow.
Relatively easy fix to try, but will take time to rebuild.
Make sure Armory isn't running. If you can, check for ArmoryDB.exe in task manager's processes, and if it is there end it.
Press the Windows Key & the R key together. You'll get a popup to "Run". Enter this into the box (exactly as it is) and hit OK:
Code:
%appdata%\Armory\
You want to delete the just "databases" folder (and anything in it).
You could reboot your PC at this point for good measure if you're not sure if Armory might be running still.
Start up Armory once this is done. It should start the process of building & scanning again. Fingers crossed that once it rebuilds you'll be connected and up to date.
Yes , near as I can tell? I am NOT technical.
So guide me through how to pull more and I will pull it?
Shouldn't be much technical magic to it - just a text file and either you've copy/pasted it all or not So guide me through how to pull more and I will pull it?
Generic path to that file is
Code:
%appdata%\Armory\dbLog.txt
Code:
C:\Users\Owner\AppData\Roaming\Armory\dbLog.txt
OK, I tried to pull it with the code given above and only got a bunch of gibberish.
Then I pulled it another way. (Note the text at the top almost matches the text line you gave me). It is here https://pastebin.com/JK8WAdzh
Per goatpig.
The last half of the long log file is posted at https://pastebin.com/z4Ve97tY
Yes , near as I can tell? I am NOT technical.
So guide me through how to pull more and I will pull it?
Shouldn't be much technical magic to it - just a text file and either you've copy/pasted it all or not So guide me through how to pull more and I will pull it?
Generic path to that file is
Code:
%appdata%\Armory\dbLog.txt
Code:
C:\Users\Owner\AppData\Roaming\Armory\dbLog.txt
Yes , near as I can tell? I am NOT technical.
So guide me through how to pull more and I will pull it?
So guide me through how to pull more and I will pull it?
Is what you posted on pastebin the ENTIRE contents of dbLog.txt? 
bump?
Ok, Thanks for the info. Hopefully, I got you what you need. I have posted it at Imgur.
https://imgur.com/a/zqRmMXZ
https://imgur.com/a/zqRmMXZ
This snippet is useless.
The best would be to post the complete log. And please use https://pastebin.com/ and provide us the link.
Images are a pain in the ass to look for errors inside a log.
Ok, Thanks for the info. Hopefully, I got you what you need. I have posted it at Imgur.
https://imgur.com/a/zqRmMXZ
https://imgur.com/a/zqRmMXZ
Hi
I am not sure I understand. Is the dblog.txt file different than what I posted?
I am not sure I understand. Is the dblog.txt file different than what I posted?
Yes, what you posted is the aggregate log, I want the db specific log now.
Quote
If so where do I find it?
Armory's datadir, where your wallets reside.
Hi
I am not sure I understand. Is the dblog.txt file different than what I posted? If so where do I find it? I posted the entire log at blogmyoptions.com/test
I am not sure I understand. Is the dblog.txt file different than what I posted? If so where do I find it? I posted the entire log at blogmyoptions.com/test
Post dbLog.txt. If you have to cut it down, I'm more interested in the tail of the file than the head.
Rebooted the computer. restarted bitcoin core. Let it sync. Then restarted Armory let it sync all nite. Same issues?
Unfortunately, my armory log is so big paste bin will not let me post it.
So the log is reposted https://www.blogmyoptions.com/test/
Unfortunately, my armory log is so big paste bin will not let me post it.
So the log is reposted https://www.blogmyoptions.com/test/
Just restart the whole stack. If it fails again, post your logs.
Thanks guys.
Normally I sync bitcoin core before I start Armory. Once core is sync'd I shut it down then start Armory. On this last round, I ran Bitcoin Core and got it updated. Shut it down and started Armory let it run all night and it would never finalize itself.
Normally I sync bitcoin core before I start Armory. Once core is sync'd I shut it down then start Armory. On this last round, I ran Bitcoin Core and got it updated. Shut it down and started Armory let it run all night and it would never finalize itself.
It is quite possible that you had an "old" ArmoryDB process running.
Either restart the PC, start Bitcoin Core, then start Armory... or shutdown Armory, make sure that all the Armory related processes in Task Manager have been "killed". Then, try restarting Armory.
Either restart the PC, start Bitcoin Core, then start Armory... or shutdown Armory, make sure that all the Armory related processes in Task Manager have been "killed". Then, try restarting Armory.
I can not see core running on your screenshot. Do you have core synced and running ?
Armory needs core to be fully synced and running since it retrieves the data (incoming transations, balances, ..) from your local core installation.
Running bitcoind in the background - Note that Armory says connected, but 0 blocks - confirmed in the logs.Armory needs core to be fully synced and running since it retrieves the data (incoming transations, balances, ..) from your local core installation.
@truebits
Going on the last entry in your logs, it was still scanning the blocks at this point:
Code:
-INFO - 23:31:19.719: (e:\users\goat\code\armory3\cppforswig\blockchainscanner.cpp:852) scanned from block #507886 to #508389
Code:
2018-09-03 23:31:19 (INFO) -- ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
2018-09-04 04:57:54 (INFO) -- ArmoryQt.py:3672 - Log saved to D:/armorylog_20180904_0457.txt
Assuming Bitcoin Core is fully synced, ArmoryDB might be choking on some corrupt data... though there is or was something strange going on with the 2bW2mnkwH wallet.
I'd guess an Armory database rebuild, and failing that a reindex in Bitcoin Core. Running Bitcoin Core separately from Armory would be worth a shot too, but needs a little configuration to work.
I can not see core running on your screenshot. Do you have core synced and running ?
Armory needs core to be fully synced and running since it retrieves the data (incoming transations, balances, ..) from your local core installation.
You can paste it between [ code] and [ /code] tags (ommitting the spaces).
If the log is too long, you can upload it to any pate site (e.g. https://pastebin.com/).
Armory needs core to be fully synced and running since it retrieves the data (incoming transations, balances, ..) from your local core installation.
I tried to attach the log, but could not
You can paste it between [ code] and [ /code] tags (ommitting the spaces).
If the log is too long, you can upload it to any pate site (e.g. https://pastebin.com/).
I cannot seem to get my Armory 96.3 to sync so I can get access to view the wallets. I read here similar stories and it sounded like the problems were fixed in the 96.4 updates. So I updated to 96.4. Same issues persist see photo https://imgur.com/a/ZFa05aJ.
I tried to attach the log, but could not so it is located at https://www.blogmyoptions.com/test/
I tried to attach the log, but could not so it is located at https://www.blogmyoptions.com/test/
Jump to: