Topic: Can't get armory online (Read 1023 times)
ah thank you!
When I open armory the logs says it can find the data from the dir on the local disk. I couldn't get any links I found to work...how do I point it to my external drive.
Depending on the operating system, you first need to mount the disk.
Afterwards, start armory via the commandline with the --satoshi-datadir parameter:
Code:
armory --satoshi-datadir="/your/path"
If you don't want to open armory via the command line each time, you also can edit the armoryqt.conf by adding:
Code:
satoshi-datadir="/your/path"
Tried again and my hard drive filled up before I got the whole BC Dl'd. I transferred to an external drive and when I open bitcoin core it read the BC data just fine and fully sync's.
I am on ububntu and I reinstalled the .96.4 gcc 4.7 version https://btcarmory.com/0.96.4-release/
When I open armory the logs says it can find the data from the dir on the local disk. I couldn't get any links I found to work...how do I point it to my external drive.
thx!
I am on ububntu and I reinstalled the .96.4 gcc 4.7 version https://btcarmory.com/0.96.4-release/
When I open armory the logs says it can find the data from the dir on the local disk. I couldn't get any links I found to work...how do I point it to my external drive.
thx!
no i haven't. I will do it. I think though I can sort of believe my balance though right? I only had transactions from a few years ago and they seem to be showing up.
The only way to know for sure is to check your balances against the current longest chain.
no i haven't. I will do it. I think though I can sort of believe my balance though right? I only had transactions from a few years ago and they seem to be showing up.
The only way to know for sure is to check your balances against the current longest chain.
Your chain data is borked. Have you tried deleting Armory's database folder yet?
no i haven't. I will do it. I think though I can sort of believe my balance though right? I only had transactions from a few years ago and they seem to be showing up.
Your chain data is borked. Have you tried deleting Armory's database folder yet?
When it does so, check that you have the "Connected" message in green in the bottom right corner... the number of blocks should be greater than the current block height of 531,939.
Anyways I just wanted to see the balance so I guess I got it going?
Cheers thx for the help happy I could make it work!
Hmmm left it for a day and a half after restarting since it seem to freeze on "parsing transaction hashes or something" It seemed to get further but I think its stuck again. I don't want to disturb it so i screenshotted with my phone the end of the log as the rest seems normal (other log was the same as before with nothing else different but new timestamps:
Dashboard says armorey is online. Bottom right corner says offline in red and 366869 blocks. Armory is online and orgazing block chain graphics are an orange bevelled square moving left and right. Scan tx history just has very small orange piece on it's left.
Last few entries is dblog...
Verifying tx filters
Done checking tx filters
Enabling zero conf tracking
RPC connection established
Nothing added to armory log since previous post about it. It didn't change over night. I tthink I only have 2g of ram and 7gbs of HD space left BTW.
Edit: tried to add my old wallet and it seemed to freeze. Rebooted and restarted armory. Its building databases seems to be advancing.
Edit2:I think I have 8 GB of ram
Last few entries is dblog...
Verifying tx filters
Done checking tx filters
Enabling zero conf tracking
RPC connection established
Nothing added to armory log since previous post about it. It didn't change over night. I tthink I only have 2g of ram and 7gbs of HD space left BTW.
Edit: tried to add my old wallet and it seemed to freeze. Rebooted and restarted armory. Its building databases seems to be advancing.
Edit2:I think I have 8 GB of ram
Just leave it for a couple of hours... it should eventually finish doing all the scanning and tell you that "Blockchain loading is complete".
When it does so, check that you have the "Connected" message in green in the bottom right corner... the number of blocks should be greater than the current block height of 531,939.
When it does so, check that you have the "Connected" message in green in the bottom right corner... the number of blocks should be greater than the current block height of 531,939.
Seems it finished the first process and node status is now full. Armory log says dashboard switched to scanning mode although the last entry is an hour old. Log has this repeated couple times a minute for hours.
Dblog has parsed block file many times and one last line says organizing chain.
Dashboard says organizing chain and the graphic is moving but there no progress indicator
Dblog has parsed block file many times and one last line says organizing chain.
Dashboard says organizing chain and the graphic is moving but there no progress indicator
Looking at your logs... You're running the old outdated version of Armory (0.96):
You need to update to 0.96.4 for it to work with the latest versions of Bitcoin Core.
Until you do this, Armory will not sync.
NOTE: The "official" Armory website is now: https://btcarmory.com/
ok cheers, thats a great lead ;p Quote
2018-07-13 14:07 (INFO) -- ArmoryUtils.py:1262 - Armory Version : 0.96
You need to update to 0.96.4 for it to work with the latest versions of Bitcoin Core.
Until you do this, Armory will not sync.
NOTE: The "official" Armory website is now: https://btcarmory.com/
Looking at your logs... You're running the old outdated version of Armory (0.96):
You need to update to 0.96.4 for it to work with the latest versions of Bitcoin Core.
Until you do this, Armory will not sync.
NOTE: The "official" Armory website is now: https://btcarmory.com/
Quote
2018-07-13 14:07 (INFO) -- ArmoryUtils.py:1262 - Armory Version : 0.96
You need to update to 0.96.4 for it to work with the latest versions of Bitcoin Core.
Until you do this, Armory will not sync.
NOTE: The "official" Armory website is now: https://btcarmory.com/
We can't tell if your logs are ok without seeing a lot more of it that what you think is relevant. Use https://pastebin.com/ and copy/paste as much from the end of the log as you can.
Seeing as you switched OSes, can you confirm the versions of Bitcoin Core and Armory that you have installed on your Ubuntu setup? Where did you download Armory from?
Did you use: https://github.com/goatpig/BitcoinArmory/releases or did you download from the Ubuntu "Store"?
Seeing as you switched OSes, can you confirm the versions of Bitcoin Core and Armory that you have installed on your Ubuntu setup? Where did you download Armory from?
Did you use: https://github.com/goatpig/BitcoinArmory/releases or did you download from the Ubuntu "Store"?
This is armorylog.txt the whole thing was too much here is a couple thousand lines from the end: https://pastebin.com/EPxFJuNb
Here is dblog.txt: https://pastebin.com/mk6VyEFr
I didn't switch OSes this time. I am on the orignal ubuntu I downloaded the block chain on (as I understand and remember).
I don't know ubuntu well to know what versions I have. I can't tell if there are multiple armory's possibly that are installed. How do I tell the versions?
I don't think I got it from the repo. I think I got it from the armory download page and have tried both versions that are there. Happy to reinstall etc. But hoping for direction and clarity
I couldn't get if from the ubuntu store. It only showed up once I think and I reinstalled from the armory website since I'm pretty sure. Why am I downloading from a repo instead of the official site?
We can't tell if your logs are ok without seeing a lot more of it that what you think is relevant. Use https://pastebin.com/ and copy/paste as much from the end of the log as you can.
Seeing as you switched OSes, can you confirm the versions of Bitcoin Core and Armory that you have installed on your Ubuntu setup? Where did you download Armory from?
Did you use: https://github.com/goatpig/BitcoinArmory/releases or did you download from the Ubuntu "Store"?
Seeing as you switched OSes, can you confirm the versions of Bitcoin Core and Armory that you have installed on your Ubuntu setup? Where did you download Armory from?
Did you use: https://github.com/goatpig/BitcoinArmory/releases or did you download from the Ubuntu "Store"?
still looking for verification my logs are ok and exactly what part of the process i am observing.
and exactly what part of the process i am observing. Seems like its working...am I just not being patient? Hard to tell what step I am on behind the scenes compared to what its telling me...
It will take some time, yes. For reference blk01313.dat is the latest on my machine, at least. That log file is increasing past block #74, right?I'm hoping this external drive is connected via USB3 or better - Might take an excruciatingly long time if it is USB2
Recently I decided to try lightning on this ubuntu drive and to my delight I already had most of the chain and it worked when I fully sync it.
Seems like its working...am I just not being patient? Hard to tell what step I am on behind the scenes compared to what its telling me...
It will take some time, yes. For reference blk01313.dat is the latest on my machine, at least. That log file is increasing past block #74, right?I'm hoping this external drive is connected via USB3 or better - Might take an excruciatingly long time if it is USB2
Seems like its working...am I just not being patient? Hard to tell what step I am on behind the scenes compared to what its telling me...
Quote
2018-07-13 14:07 (INFO) -- ArmoryUtils.py:665 - Executing popen: ['/usr/bin/bitcoind', '-datadir=/home/me/.bitcoin/']
2018-07-13 14:07 (INFO) -- SDM.py:443 - PID of bitcoind: 4738
2018-07-13 14:07 (INFO) -- SDM.py:444 - PID of armory: 4704
2018-07-13 14:07 (INFO) -- ArmoryUtils.py:665 - Executing popen: ['python', '/usr/local/lib/armory/guardian.py', '4704', '4738']
2018-07-13 14:07 (INFO) -- ArmoryQt.py:1850 - setSatoshiPaths
2018-07-13 14:07 (WARNING) -- SDM.py:396 - Spawning DB with command:ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/home/me/.bitcoin/blocks" --datadir="/home/me/.armory/" --dbdir="/home/me/.armory/databases"
2018-07-13 14:07 (INFO) -- ArmoryUtils.py:665 - Executing popen: ['ArmoryDB', '--db-type="DB_FULL"', '--cookie', '--satoshi-datadir="/home/me/.bitcoin/blocks"', '--datadir="/home/me/.armory/"', '--dbdir="/home/me/.armory/databases"']
2018-07-13 14:07 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2018-07-13 14:07 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 0
2018-07-13 14:07 (INFO) -- ArmoryQt.py:1882 - loadBlockchainIfNecessary
2018-07-13 14:07 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2018-07-13 14:07 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2018-07-13 14:10 (INFO) -- ArmoryQt.py:5400 - BDM is safe for clean shutdown
2018-07-13 14:10 (INFO) -- SDM.py:457 - Called stopBitcoind
2018-07-13 14:07 (INFO) -- SDM.py:443 - PID of bitcoind: 4738
2018-07-13 14:07 (INFO) -- SDM.py:444 - PID of armory: 4704
2018-07-13 14:07 (INFO) -- ArmoryUtils.py:665 - Executing popen: ['python', '/usr/local/lib/armory/guardian.py', '4704', '4738']
2018-07-13 14:07 (INFO) -- ArmoryQt.py:1850 - setSatoshiPaths
2018-07-13 14:07 (WARNING) -- SDM.py:396 - Spawning DB with command:ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/home/me/.bitcoin/blocks" --datadir="/home/me/.armory/" --dbdir="/home/me/.armory/databases"
2018-07-13 14:07 (INFO) -- ArmoryUtils.py:665 - Executing popen: ['ArmoryDB', '--db-type="DB_FULL"', '--cookie', '--satoshi-datadir="/home/me/.bitcoin/blocks"', '--datadir="/home/me/.armory/"', '--dbdir="/home/me/.armory/databases"']
2018-07-13 14:07 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 1
2018-07-13 14:07 (INFO) -- ArmoryQt.py:1900 - Setting netmode: 0
2018-07-13 14:07 (INFO) -- ArmoryQt.py:1882 - loadBlockchainIfNecessary
2018-07-13 14:07 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2018-07-13 14:07 (INFO) -- ArmoryQt.py:4619 - Dashboard switched to "Scanning" mode
2018-07-13 14:10 (INFO) -- ArmoryQt.py:5400 - BDM is safe for clean shutdown
2018-07-13 14:10 (INFO) -- SDM.py:457 - Called stopBitcoind
Quote
Log file opened at 1531516027: /home/me/.armory/dbLog.txt
-INFO - 1531516027: (main.cpp:23) Running on 4 threads
-INFO - 1531516027: (main.cpp:24) Ram usage level: 4
-INFO - 1531516027: (BlockUtils.cpp:907) blkfile dir: /home/me/.bitcoin/blocks
-INFO - 1531516027: (BlockUtils.cpp:908) lmdb dir: /home/me/.armory/databases
-INFO - 1531516027: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1531516028: (BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO - 1531516028: (DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 1531516028: (DatabaseBuilder.cpp:208) Found 7993 headers in db
-INFO - 1531516028: (DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1531516037: (DatabaseBuilder.cpp:268) parsed block file #2
-INFO - 1531516048: (DatabaseBuilder.cpp:268) parsed block file #3
-INFO - 1531516052: (DatabaseBuilder.cpp:268) parsed block file #6
-INFO - 1531516060: (DatabaseBuilder.cpp:268) parsed block file #7
-INFO - 1531516064: (DatabaseBuilder.cpp:268) parsed block file #10
-INFO - 1531516081: (DatabaseBuilder.cpp:268) parsed block file #11
-INFO - 1531516085: (DatabaseBuilder.cpp:268) parsed block file #14
-INFO - 1531516101: (DatabaseBuilder.cpp:268) parsed block file #15
-INFO - 1531516106: (DatabaseBuilder.cpp:268) parsed block file #18
-INFO - 1531516127: (DatabaseBuilder.cpp:268) parsed block file #19
-INFO - 1531516130: (DatabaseBuilder.cpp:268) parsed block file #22
-INFO - 1531516157: (DatabaseBuilder.cpp:268) parsed block file #23
-INFO - 1531516160: (DatabaseBuilder.cpp:268) parsed block file #26
-INFO - 1531516178: (DatabaseBuilder.cpp:268) parsed block file #27
-INFO - 1531516190: (DatabaseBuilder.cpp:268) parsed block file #29
-INFO - 1531516200: (DatabaseBuilder.cpp:268) parsed block file #34
-INFO - 1531516221: (DatabaseBuilder.cpp:268) parsed block file #38
-INFO - 1531516246: (DatabaseBuilder.cpp:268) parsed block file #42
-INFO - 1531516273: (DatabaseBuilder.cpp:268) parsed block file #46
-INFO - 1531516293: (DatabaseBuilder.cpp:268) parsed block file #50
-INFO - 1531516314: (DatabaseBuilder.cpp:268) parsed block file #54
-INFO - 1531516337: (DatabaseBuilder.cpp:268) parsed block file #58
-INFO - 1531516376: (DatabaseBuilder.cpp:268) parsed block file #62
-INFO - 1531516385: (DatabaseBuilder.cpp:268) parsed block file #66
-INFO - 1531516407: (DatabaseBuilder.cpp:268) parsed block file #70
-INFO - 1531516429: (DatabaseBuilder.cpp:268) parsed block file #74
-INFO - 1531516027: (main.cpp:23) Running on 4 threads
-INFO - 1531516027: (main.cpp:24) Ram usage level: 4
-INFO - 1531516027: (BlockUtils.cpp:907) blkfile dir: /home/me/.bitcoin/blocks
-INFO - 1531516027: (BlockUtils.cpp:908) lmdb dir: /home/me/.armory/databases
-INFO - 1531516027: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1531516028: (BlockUtils.cpp:1091) Executing: doInitialSyncOnLoad
-INFO - 1531516028: (DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 1531516028: (DatabaseBuilder.cpp:208) Found 7993 headers in db
-INFO - 1531516028: (DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1531516037: (DatabaseBuilder.cpp:268) parsed block file #2
-INFO - 1531516048: (DatabaseBuilder.cpp:268) parsed block file #3
-INFO - 1531516052: (DatabaseBuilder.cpp:268) parsed block file #6
-INFO - 1531516060: (DatabaseBuilder.cpp:268) parsed block file #7
-INFO - 1531516064: (DatabaseBuilder.cpp:268) parsed block file #10
-INFO - 1531516081: (DatabaseBuilder.cpp:268) parsed block file #11
-INFO - 1531516085: (DatabaseBuilder.cpp:268) parsed block file #14
-INFO - 1531516101: (DatabaseBuilder.cpp:268) parsed block file #15
-INFO - 1531516106: (DatabaseBuilder.cpp:268) parsed block file #18
-INFO - 1531516127: (DatabaseBuilder.cpp:268) parsed block file #19
-INFO - 1531516130: (DatabaseBuilder.cpp:268) parsed block file #22
-INFO - 1531516157: (DatabaseBuilder.cpp:268) parsed block file #23
-INFO - 1531516160: (DatabaseBuilder.cpp:268) parsed block file #26
-INFO - 1531516178: (DatabaseBuilder.cpp:268) parsed block file #27
-INFO - 1531516190: (DatabaseBuilder.cpp:268) parsed block file #29
-INFO - 1531516200: (DatabaseBuilder.cpp:268) parsed block file #34
-INFO - 1531516221: (DatabaseBuilder.cpp:268) parsed block file #38
-INFO - 1531516246: (DatabaseBuilder.cpp:268) parsed block file #42
-INFO - 1531516273: (DatabaseBuilder.cpp:268) parsed block file #46
-INFO - 1531516293: (DatabaseBuilder.cpp:268) parsed block file #50
-INFO - 1531516314: (DatabaseBuilder.cpp:268) parsed block file #54
-INFO - 1531516337: (DatabaseBuilder.cpp:268) parsed block file #58
-INFO - 1531516376: (DatabaseBuilder.cpp:268) parsed block file #62
-INFO - 1531516385: (DatabaseBuilder.cpp:268) parsed block file #66
-INFO - 1531516407: (DatabaseBuilder.cpp:268) parsed block file #70
-INFO - 1531516429: (DatabaseBuilder.cpp:268) parsed block file #74
Jump to: