Keroppi (OP)
Newbie
Offline
Activity: 10
Merit: 0
|
|
August 20, 2017, 03:31:10 AM Last edit: August 28, 2017, 08:53:48 PM by Keroppi |
|
Hi, Having some issues with Armory being "Connected" but doesn't get any new blocks once it first starts up, I need to restart Armory to get it to see the new blocks. Tried different client nodes, BitcoinABC, Bitcoin Unlimited Cash, specifying the data directory for Armory "C:\Program Files (x86)\Armory\ArmoryQt.exe" --satoshi-datadir="D:\AppData\Roaming\Bitcoin" but it still doesn't see any new blocks. Reindexed the BCH nodes and deleted the Armory database as well and disabled Windows Firewall. Running bitcoinqt first then opening Armory or letting Armory open bitcoind in the background doesn't update either. Deleted the database and ran ArmoryDB with --db-type=DB_BARE didn't work either. If I receive a transaction, I do see 0 confirms but it doesn't update unless I restart Armory. I can send transactions with no issues. Running Windows 10 Pro 64bit Armory 0.96.2 RC2 Here are the logs. Thanks. Armory Log 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1147 - C++ block utilities loaded successfully 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1264 - 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1265 - 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1266 - 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1267 - ************************************************************ 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1268 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe --satoshi-datadir=D:\AppData\Roaming\Bitcoin 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1269 - ************************************************************ 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1270 - Loading Armory Engine: 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1271 - Armory Version : 0.96.1.2 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1272 - Armory Build: : 8426412842 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1273 - PyBtcWallet Version : 1.35 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1274 - Detected Operating system: Windows 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1275 - OS Variant : 8-6.2.9200--Multiprocessor Free 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1276 - User home-directory : C:\Users\*****\AppData\Roaming 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1277 - Satoshi BTC directory : D:\AppData\Roaming\Bitcoin 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1278 - Armory home dir : C:\Users\*****\AppData\Roaming\Armory\ 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1279 - Detected System Specs : 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1280 - Total Available RAM : 5.92 GB 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1281 - CPU ID string : Intel64 Family 6 Model 23 Stepping 6, GenuineIntel 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1282 - Number of CPU cores : 2 cores 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1283 - System is 64-bit : True 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1284 - Preferred Encoding : cp1252 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1285 - Machine Arch : amd64 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1286 - Available HDD (ARM) : 7512 GB 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1287 - Available HDD (BTC) : 7512 GB 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1288 - 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1289 - Network Name: Main Network 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1290 - Satoshi Port: 8333 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1291 - Do wlt check: True 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1292 - Named options/arguments to armoryengine.py: 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - thread_count : -1 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - rescan : False 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - ignoreAllZC : False 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - rescanBalance : False 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - disableModules : False 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - port : None 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - interport : 8223 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - coverageOutputDir: None 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - forceWalletCheck: False 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - regtest : False 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - rebuild : False 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - nettimeout : 2 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - datadir : DEFAULT 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - clearMempool : False 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - offline : False 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - armoryDBDir : DEFAULT 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - armorydb_port : 9001 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - satoshiPort : DEFAULT 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - useTorSettings : False 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - netlog : False 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - keypool : 100 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - coverageInclude : None 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - forceOnline : False 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - redownload : False 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - rpcBindAddr : 127.0.0.1 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - armorydb_ip : 127.0.0.1 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - multisigFile : DEFAULT 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - ram_usage : -1 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - mtdebug : False 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - logDisable : False 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - settingsPath : C:\Users\*****\AppData\Roaming\Armory\ArmorySettings.txt 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - language : en 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - db_type : DB_FULL 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - doDebug : False 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - enableDetSign : True 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - disableConfPermis: False 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - testnet : False 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - rpcport : DEFAULT 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - satoshiHome : D:\AppData\Roaming\Bitcoin 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - satoshiRpcport : DEFAULT 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - logFile : C:\Users\*****\AppData\Roaming\Armory\ArmoryQt.exe.log.txt 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1294 - verbosity : None 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1295 - Other arguments: 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1298 - ************************************************************ 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:1701 - C++ block utilities loaded successfully 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:3562 - Using settings file: C:\Users\*****\AppData\Roaming\Armory\ArmorySettings.txt 2017-08-19 21:00:10 (ERROR) -- ArmoryUtils.pyc:3719 - Unsupported language specified. Defaulting to English (en) 2017-08-19 21:00:10 (INFO) -- ArmoryUtils.pyc:3722 - Using Language: en 2017-08-19 21:00:10 (INFO) -- BDM.pyc:355 - Using the asynchronous/multi-threaded BlockDataManager. 2017-08-19 21:00:10 (INFO) -- BDM.pyc:356 - Blockchain operations will happen in the background. 2017-08-19 21:00:10 (INFO) -- BDM.pyc:357 - Devs: check TheBDM.getState() before asking for data. 2017-08-19 21:00:10 (INFO) -- BDM.pyc:358 - Registering addresses during rescans will queue them for 2017-08-19 21:00:10 (INFO) -- BDM.pyc:359 - inclusion after the current scan is completed. 2017-08-19 21:00:11 (INFO) -- ArmoryUtils.pyc:3562 - Using settings file: C:\Users\*****\AppData\Roaming\Armory\ArmorySettings.txt 2017-08-19 21:00:11 (INFO) -- ArmoryQt.py:2054 - loadWalletsAndSettings 2017-08-19 21:00:11 (INFO) -- ArmoryQt.py:2114 - Loading wallets... 2017-08-19 21:00:12 (INFO) -- ArmoryQt.py:2179 - Number of wallets read in: 6 2017-08-19 21:00:12 (INFO) -- ArmoryQt.py:2184 - ***** (W" (No Encryption) 2017-08-19 21:00:12 (INFO) -- ArmoryQt.py:2184 - ***** " (No Encryption) 2017-08-19 21:00:12 (INFO) -- ArmoryQt.py:2184 - ***** " (Encrypted) 2017-08-19 21:00:12 (INFO) -- ArmoryQt.py:2184 - ***** (No Encryption) 2017-08-19 21:00:12 (INFO) -- ArmoryQt.py:2184 - ***** " (Encrypted) 2017-08-19 21:00:12 (INFO) -- ArmoryQt.py:2184 - ***** (No Encryption) 2017-08-19 21:00:12 (INFO) -- ArmoryQt.py:2189 - Loading Multisig Lockboxes 2017-08-19 21:00:12 (INFO) -- ArmoryQt.py:1756 - acquiring process mutex... 2017-08-19 21:00:13 (INFO) -- ArmoryQt.py:1395 - setupUriRegistration 2017-08-19 21:00:13 (INFO) -- ArmoryQt.py:1463 - Armory already registered for current user. Done! 2017-08-19 21:00:13 (INFO) -- ArmoryQt.py:566 - Usermode: Expert 2017-08-19 21:00:13 (INFO) -- ArmoryQt.py:1691 - Changing usermode: 2017-08-19 21:00:13 (INFO) -- ArmoryQt.py:1692 - From: Expert 2017-08-19 21:00:13 (INFO) -- ArmoryQt.py:1700 - To: Expert 2017-08-19 21:00:13 (INFO) -- ArmoryQt.py:1829 - startBitcoindIfNecessary 2017-08-19 21:00:16 (INFO) -- ArmoryQt.py:1865 - setSatoshiPaths 2017-08-19 21:00:16 (WARNING) -- SDM.pyc:396 - Spawning DB with command: ./ArmoryDB.exe --db-type="DB_FULL" --cookie --satoshi-datadir="D:\AppData\Roaming\Bitcoin\blocks" --datadir="C:\Users\*****\AppData\Roaming\Armory\" --dbdir="C:\Users\*****\AppData\Roaming\Armory\databases" 2017-08-19 21:00:16 (INFO) -- ArmoryUtils.pyc:672 - Executing popen: ['./ArmoryDB.exe', '--db-type="DB_FULL"', '--cookie', u'--satoshi-datadir="D:\\AppData\\Roaming\\Bitcoin\\blocks"', '--datadir="C:\\Users\\*****\\AppData\\Roaming\\Armory\\"', u'--dbdir="C:\\Users\\*****\\AppData\\Roaming\\Armory\\databases"'] 2017-08-19 21:00:18 (INFO) -- ArmoryQt.py:1817 - Connecting on port 51158 2017-08-19 21:00:18 (INFO) -- ArmoryQt.py:1917 - Setting netmode: 1 2017-08-19 21:00:18 (INFO) -- ArmoryQt.py:1899 - loadBlockchainIfNecessary 2017-08-19 21:00:18 (INFO) -- ArmoryQt.py:1917 - Setting netmode: 1 2017-08-19 21:00:18 (INFO) -- ArmoryQt.py:4654 - Dashboard switched to "Scanning" mode 2017-08-19 21:00:18 (INFO) -- ArmoryQt.py:4654 - Dashboard switched to "Scanning" mode 2017-08-19 21:00:18 (INFO) -- ArmoryQt.py:709 - MinimizeOnOpen is True 2017-08-19 21:00:18 (INFO) -- ArmoryQt.py:4654 - Dashboard switched to "Scanning" mode 2017-08-19 21:00:19 (INFO) -- ArmoryQt.py:4654 - Dashboard switched to "Scanning" mode 2017-08-19 21:00:20 (INFO) -- ArmoryQt.py:4654 - Dashboard switched to "Scanning" mode 2017-08-19 21:00:20 (INFO) -- ArmoryQt.py:4654 - Dashboard switched to "Scanning" mode 2017-08-19 21:00:21 (INFO) -- ArmoryQt.py:4654 - Dashboard switched to "Scanning" mode 2017-08-19 21:00:21 (INFO) -- ArmoryQt.py:4654 - Dashboard switched to "Scanning" mode 2017-08-19 21:00:22 (INFO) -- ArmoryQt.py:4654 - Dashboard switched to "Scanning" mode 2017-08-19 21:00:22 (INFO) -- ArmoryQt.py:4654 - Dashboard switched to "Scanning" mode 2017-08-19 21:00:22 (INFO) -- ArmoryQt.py:4654 - Dashboard switched to "Scanning" mode 2017-08-19 21:00:27 (INFO) -- ArmoryQt.py:4654 - Dashboard switched to "Scanning" mode 2017-08-19 21:00:28 (INFO) -- ArmoryQt.py:4654 - Dashboard switched to "Scanning" mode 2017-08-19 21:00:28 (INFO) -- ArmoryQt.py:4654 - Dashboard switched to "Scanning" mode 2017-08-19 21:00:28 (INFO) -- ArmoryQt.py:4654 - Dashboard switched to "Scanning" mode 2017-08-19 21:00:29 (INFO) -- ArmoryQt.py:4654 - Dashboard switched to "Scanning" mode 2017-08-19 21:00:29 (INFO) -- ArmoryQt.py:4654 - Dashboard switched to "Scanning" mode 2017-08-19 21:00:29 (INFO) -- ArmoryQt.py:4654 - Dashboard switched to "Scanning" mode 2017-08-19 21:00:29 (INFO) -- ArmoryQt.py:4654 - Dashboard switched to "Scanning" mode 2017-08-19 21:15:21 (INFO) -- ArmoryQt.py:5431 - BDM is safe for clean shutdown 2017-08-19 21:15:21 (INFO) -- SDM.pyc:459 - Called stopBitcoind 2017-08-19 21:15:21 (INFO) -- SDM.pyc:465 - ...but bitcoind is not running, to be able to stop 2017-08-19 21:15:21 (INFO) -- ArmoryQt.py:5444 - Attempting to close the main window!
dbLog -INFO - 21:00:17.000: (..\main.cpp:32) Running on 2 threads -INFO - 21:00:17.000: (..\main.cpp:33) Ram usage level: 4 -INFO - 21:00:17.000: (..\BlockUtils.cpp:915) blkfile dir: D:\AppData\Roaming\Bitcoin\blocks -INFO - 21:00:17.000: (..\BlockUtils.cpp:916) lmdb dir: C:\Users\*****\AppData\Roaming\Armory\databases -INFO - 21:00:17.000: (..\lmdb_wrapper.cpp:388) Opening databases... -INFO - 21:00:17.031: (..\nodeRPC.cpp:57) RPC connection established -INFO - 21:00:17.031: (..\nodeRPC.cpp:346) Node is ready -INFO - 21:00:17.031: (..\BlockUtils.cpp:1108) Executing: doInitialSyncOnLoad -INFO - 21:00:17.031: (c:\users\goat\code\armory3\cppforswig\BDM_Server.h:263) Listening on port 51158 -INFO - 21:00:17.047: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node -INFO - 21:00:18.641: (..\DatabaseBuilder.cpp:199) Reading headers from db -INFO - 21:00:18.110: (..\BDM_Server.cpp:1114) registered bdv: 6e26f35eb2bf990f2a19 -INFO - 21:00:22.500: (..\DatabaseBuilder.cpp:238) Found 479794 headers in db -INFO - 21:00:27.391: (..\DatabaseBuilder.cpp:64) Rewinding 100 blocks -INFO - 21:00:27.391: (..\DatabaseBuilder.cpp:71) updating HEADERS db -INFO - 21:00:27.469: (..\DatabaseBuilder.cpp:493) Found next block after skipping 183765bytes -INFO - 21:00:28.672: (..\DatabaseBuilder.cpp:493) Found next block after skipping 932725bytes -INFO - 21:00:28.750: (..\DatabaseBuilder.cpp:281) parsed block file #955 -INFO - 21:00:28.360: (..\DatabaseBuilder.cpp:281) parsed block file #956 -INFO - 21:00:28.453: (..\Blockchain.cpp:248) Organizing chain -INFO - 21:00:29.641: (..\Blockchain.cpp:370) Organized chain in 0s -INFO - 21:00:29.656: (..\DatabaseBuilder.cpp:76) updated HEADERS db in 1s -INFO - 21:00:29.656: (..\lmdb_wrapper.cpp:388) Opening databases... -INFO - 21:00:29.750: (..\DatabaseBuilder.cpp:134) scanning new blocks from #479794 to #479801 -INFO - 21:00:29.875: (..\BlockchainScanner.cpp:852) scanned from block #479794 to #479801 -INFO - 21:00:29.906: (..\lmdb_wrapper.cpp:388) Opening databases... -INFO - 21:00:29.906: (..\DatabaseBuilder.cpp:186) scanned new blocks in 0s -INFO - 21:00:29.906: (..\DatabaseBuilder.cpp:190) init db in 11s -INFO - 21:00:29.906: (..\BDM_supportClasses.cpp:1870) Enabling zero-conf tracking -WARN - 21:01:40.047: (..\BDM_supportClasses.cpp:1923) running 5 zc parser threads -WARN - 21:03:09.203: (..\BDM_supportClasses.cpp:1923) running 10 zc parser threads -INFO - 21:15:21.938: (..\BDM_Server.cpp:1143) unregistered bdv: 6e26f35eb2bf990f2a19 -INFO - 21:15:21.938: (..\BDM_Server.cpp:1054) proceeding to shutdown -ERROR - 21:15:21.938: (..\BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: POLLNVAL in readFromSocketThread -INFO - 21:15:21.953: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node -ERROR - 21:15:21.953: (..\BDM_mainthread.cpp:294) caught exception in main thread: terminate
|
|
|
|
goatpig
Moderator
Legendary
Offline
Activity: 3738
Merit: 1360
Armory Developer
|
|
August 20, 2017, 10:12:11 AM |
|
What folder is your node writing blocks to? If you are pointing Armory to a different folder than your node, it won't detect news blocks.
If you are using Bcash against a recent copy of the Bitcoin chain, it dwarves the Bcash chain in difficulty therefor Armory won't see the Bcash blocks until another month or 2.
|
|
|
|
Keroppi (OP)
Newbie
Offline
Activity: 10
Merit: 0
|
|
August 20, 2017, 02:48:28 PM |
|
Hi goatpig,
The bitcoin node is writing to the following directory,
D:\AppData\Roaming\Bitcoin which I've set in Armory under Bitcoin Home Dir and also tried setting it in the Armory shortcut "C:\Program Files (x86)\Armory\ArmoryQt.exe" --satoshi-datadir="D:\AppData\Roaming\Bitcoin"
I copied the blockchain before the fork and then ran Bitcoin Unlimited Cash to get it all up to date, so does this mean I just need to wait a month or so until Armory starts seeing new blocks?
Thanks.
|
|
|
|
goatpig
Moderator
Legendary
Offline
Activity: 3738
Merit: 1360
Armory Developer
|
|
August 20, 2017, 08:55:02 PM |
|
Hi goatpig,
The bitcoin node is writing to the following directory,
D:\AppData\Roaming\Bitcoin which I've set in Armory under Bitcoin Home Dir and also tried setting it in the Armory shortcut "C:\Program Files (x86)\Armory\ArmoryQt.exe" --satoshi-datadir="D:\AppData\Roaming\Bitcoin"
I copied the blockchain before the fork and then ran Bitcoin Unlimited Cash to get it all up to date, so does this mean I just need to wait a month or so until Armory starts seeing new blocks?
Thanks.
DB is seeing the right folder: -INFO - 21:00:17.000: (..\BlockUtils.cpp:915) blkfile dir: D:\AppData\Roaming\Bitcoin\blocks I suggest you wipe your DB and start from scratch. Also delete your logs before that and post the fresh logs.
|
|
|
|
|
goatpig
Moderator
Legendary
Offline
Activity: 3738
Merit: 1360
Armory Developer
|
|
August 21, 2017, 01:26:07 AM |
|
Are you running the client with no wallets loaded?
|
|
|
|
Keroppi (OP)
Newbie
Offline
Activity: 10
Merit: 0
|
|
August 21, 2017, 02:31:03 AM |
|
Yes, didn't move my wallets back yet after I deleted the Armory folder. Want me to add the wallets back and post the log files?
|
|
|
|
goatpig
Moderator
Legendary
Offline
Activity: 3738
Merit: 1360
Armory Developer
|
|
August 21, 2017, 11:26:47 AM |
|
Yes, didn't move my wallets back yet after I deleted the Armory folder. Want me to add the wallets back and post the log files?
Have a wallet in there, if even just a dummy you just created, and try again.
|
|
|
|
|
HCP
Legendary
Offline
Activity: 2086
Merit: 4318
<insert witty quote here>
|
|
August 22, 2017, 12:06:22 AM |
|
Now it's using " C:\Users\*****\AppData\Roaming\Bitcoin\blocks" as your satoshi-datadir... it would appear that your "Bitcoin Home Dir" is not set correctly in Armory... What's interesting is that it found blocks on C: Is that where the BitcoinUnlimitedCash blocks were stored?
|
|
|
|
Keroppi (OP)
Newbie
Offline
Activity: 10
Merit: 0
|
|
August 22, 2017, 01:02:58 AM |
|
Hi,
I have the blocks stored on a D: drive using symbolic links with the C:\Users\*****\AppData\Roaming\Bitcoin pointing to D:\AppData\Roaming\Bitcoin
Tried not using symbolic links with Bitcoin and Armory by specifying the path to D:\AppData\Roaming\Bitcoin and D:\AppData\Roaming\Armory but it still doesn't work.
Also tried using an external drive to store the Bitcoin chain and Armory database files but same issues persists.
|
|
|
|
goatpig
Moderator
Legendary
Offline
Activity: 3738
Merit: 1360
Armory Developer
|
|
August 22, 2017, 10:34:21 AM |
|
|
|
|
|
Keroppi (OP)
Newbie
Offline
Activity: 10
Merit: 0
|
|
August 22, 2017, 12:10:29 PM |
|
Hi goatpig,
I've done the following,
Set the target in the Bitcoin Armory shortcut to this, "C:\Program Files (x86)\Armory\ArmoryQt.exe" --satoshi-datadir="D:\AppData\Roaming\Bitcoin\blocks" --dbdir="D:\AppData\Roaming\Armory\databases"
Made a armoryqt.conf and armorydb.conf file and put it in D:\AppData\Roaming\Armory with the following args satoshi-datadir="D:\AppData\Roaming\Bitcoin\blocks" dbdir="D:\AppData\Roaming\Armory\databases"
Is that all that is needed for custom paths?
|
|
|
|
goatpig
Moderator
Legendary
Offline
Activity: 3738
Merit: 1360
Armory Developer
|
|
August 22, 2017, 12:32:13 PM |
|
It's an either or thing kinda, you either use the shortcut cli option or the .conf. The cli option overrides the .confs. At any rate, this pathing is very odd, did you create that folder manually?
|
|
|
|
Keroppi (OP)
Newbie
Offline
Activity: 10
Merit: 0
|
|
August 22, 2017, 08:21:32 PM |
|
It's an either or thing kinda, you either use the shortcut cli option or the .conf. The cli option overrides the .confs. At any rate, this pathing is very odd, did you create that folder manually? Yes I did, should I try to put Armory and Bitcoin into the D: root directory?
|
|
|
|
goatpig
Moderator
Legendary
Offline
Activity: 3738
Merit: 1360
Armory Developer
|
|
August 22, 2017, 08:46:43 PM |
|
Yes I did, should I try to put Armory and Bitcoin into the D: root directory?
No, that's irrelevant, just double checking.
|
|
|
|
mstenz
Newbie
Offline
Activity: 6
Merit: 0
|
|
August 28, 2017, 09:44:34 AM |
|
I think I have exactly similar issues, but i am "new" to all this and don't know from where to get the logs. I moved because disk running mostly full all the bitcoind-data to Path "Z:\Documents\Bitcoin-Data\Bitcoin". I have also configured this in Armory in Bitcoin homedir. But it always showed "Node offline". I have updated Armory to 0.96.1.beta and also bitcoin core to 0.14.2 but nothing better. Then I have started bitcoin core manually (without running Armoray and it took weeks to sync the blocks) After all done i opened Armory again and it was Connected, but after 1 day it went to "Node offline" again (also restart Armory does not help). I don't have BCC application on same PC.
How can I fix this issues please?
thx. rgds.
|
|
|
|
Keroppi (OP)
Newbie
Offline
Activity: 10
Merit: 0
|
|
August 28, 2017, 08:51:42 PM |
|
I deleted and downloaded the Bitcoin blockchain again and now everything seems to work, Armory is connected and seeing new blocks.
|
|
|
|
Keroppi (OP)
Newbie
Offline
Activity: 10
Merit: 0
|
|
August 28, 2017, 08:58:55 PM |
|
I think I have exactly similar issues, but i am "new" to all this and don't know from where to get the logs. I moved because disk running mostly full all the bitcoind-data to Path "Z:\Documents\Bitcoin-Data\Bitcoin". I have also configured this in Armory in Bitcoin homedir. But it always showed "Node offline". I have updated Armory to 0.96.1.beta and also bitcoin core to 0.14.2 but nothing better. Then I have started bitcoin core manually (without running Armoray and it took weeks to sync the blocks) After all done i opened Armory again and it was Connected, but after 1 day it went to "Node offline" again (also restart Armory does not help). I don't have BCC application on same PC.
How can I fix this issues please?
thx. rgds.
Your logs are located here, C:\Users\xxxx\AppData\Roaming\Armory
|
|
|
|
mstenz
Newbie
Offline
Activity: 6
Merit: 0
|
|
August 29, 2017, 08:00:24 AM Last edit: August 29, 2017, 08:23:14 AM by mstenz |
|
Thank you. I see this error:
-INFO - 18:26:39.718: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node -ERROR - 18:26:40.828: (..\BitcoinP2P.cpp:1037) caught StopBlockingLoop in processDataStackThread -INFO - 18:26:40.828: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node
How can I fix it?
|
|
|
|
|