THANKS!!!!
You guys sure know your stuff, that fixed it!!
Topic: Armory Stuck after Factory Reset (Read 819 times)
1) Yes
2) Yes
3) It does not matter how long after you start ArmoryQt as long as ArmoryDB was spawned first. ArmoryDB.exe is what you are looking for.
4) Open the command line prompt, browse to your Armory installation folder, run the following:
ArmoryDB.exe --ram-usage=1
2) Yes
3) It does not matter how long after you start ArmoryQt as long as ArmoryDB was spawned first. ArmoryDB.exe is what you are looking for.
4) Open the command line prompt, browse to your Armory installation folder, run the following:
ArmoryDB.exe --ram-usage=1
1) Delete /databases
2) Run ArmoryDB alone with --ram-usage=1
3) Start ArmoryQt
Get back to me if it fails.
2) Run ArmoryDB alone with --ram-usage=1
3) Start ArmoryQt
Get back to me if it fails.
1.) Just delete the folder?
2.) Start bitcoin core manually before step 2?
3.) Do I run armoryQT right after armoryDB (I assume that just an executable in the folder)
4.) How do I run it with ram usage 1?
1) Delete /databases
2) Run ArmoryDB alone with --ram-usage=1
3) Start ArmoryQt
Get back to me if it fails.
2) Run ArmoryDB alone with --ram-usage=1
3) Start ArmoryQt
Get back to me if it fails.
The cmd prompt is left open after armory crashes and the errors I can see are "POLLERR error in readfromsocketthread" these show up a couple times in between a ton of "parsed block file #xxx"
Here is the log file:
https://drive.google.com/open?id=0B_gKA8BKU4LGdVZUOE5FVmFmUms
Here is the log file:
https://drive.google.com/open?id=0B_gKA8BKU4LGdVZUOE5FVmFmUms
I'm confused, that is 4 days ago, I have tried running it plenty of times since then where it has crashed. If you look at the log file I posted it has dates as recently as today, but doesn't use that specific autoinit line of code??
Edit: Oh, I see you what you meant about the dates, referring to the previous poster. I will get that log posted.
Edit: Oh, I see you what you meant about the dates, referring to the previous poster. I will get that log posted.
That was the first suggestion which I have tried and still get the errors posted in the log above.
Bitcoind runs fine itself and is fully up to date before I start armory.
Bitcoind runs fine itself and is fully up to date before I start armory.
This is not what your log file suggests:
Code:
2016-11-17 12:26 (INFO) -- SDM.pyc:460 - Called startBitcoind
2016-11-17 12:26 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: ['C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=C:\\Users\\John\\AppData\\Roaming\\Bitcoin\\']
2016-11-17 12:26 (INFO) -- SDM.pyc:574 - PID of bitcoind: 29000
2016-11-17 12:26 (INFO) -- SDM.pyc:575 - PID of armory: 24552
2016-11-17 12:26 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: ['.\\guardian.exe', '24552', '29000']
2016-11-17 12:26 (INFO) -- SDM.pyc:756 - Creating proxy in SDM: host=127.0.0.1, port=8332
2016-11-17 12:26 (INFO) -- ArmoryQt.py:5542 - Dashboard switched to auto-InitSync
2016-11-17 12:26 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: ['C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=C:\\Users\\John\\AppData\\Roaming\\Bitcoin\\']
2016-11-17 12:26 (INFO) -- SDM.pyc:574 - PID of bitcoind: 29000
2016-11-17 12:26 (INFO) -- SDM.pyc:575 - PID of armory: 24552
2016-11-17 12:26 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: ['.\\guardian.exe', '24552', '29000']
2016-11-17 12:26 (INFO) -- SDM.pyc:756 - Creating proxy in SDM: host=127.0.0.1, port=8332
2016-11-17 12:26 (INFO) -- ArmoryQt.py:5542 - Dashboard switched to auto-InitSync
OP, Can you post the dblog.txt file?
That was the first suggestion which I have tried and still get the errors posted in the log above.
Bitcoind runs fine itself and is fully up to date before I start armory.
Bitcoind runs fine itself and is fully up to date before I start armory.
This is not what your log file suggests:
Code:
2016-11-17 12:26 (INFO) -- SDM.pyc:460 - Called startBitcoind
2016-11-17 12:26 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: ['C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=C:\\Users\\John\\AppData\\Roaming\\Bitcoin\\']
2016-11-17 12:26 (INFO) -- SDM.pyc:574 - PID of bitcoind: 29000
2016-11-17 12:26 (INFO) -- SDM.pyc:575 - PID of armory: 24552
2016-11-17 12:26 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: ['.\\guardian.exe', '24552', '29000']
2016-11-17 12:26 (INFO) -- SDM.pyc:756 - Creating proxy in SDM: host=127.0.0.1, port=8332
2016-11-17 12:26 (INFO) -- ArmoryQt.py:5542 - Dashboard switched to auto-InitSync
2016-11-17 12:26 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: ['C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=C:\\Users\\John\\AppData\\Roaming\\Bitcoin\\']
2016-11-17 12:26 (INFO) -- SDM.pyc:574 - PID of bitcoind: 29000
2016-11-17 12:26 (INFO) -- SDM.pyc:575 - PID of armory: 24552
2016-11-17 12:26 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: ['.\\guardian.exe', '24552', '29000']
2016-11-17 12:26 (INFO) -- SDM.pyc:756 - Creating proxy in SDM: host=127.0.0.1, port=8332
2016-11-17 12:26 (INFO) -- ArmoryQt.py:5542 - Dashboard switched to auto-InitSync
That was the first suggestion which I have tried and still get the errors posted in the log above.
Bitcoind runs fine itself and is fully up to date before I start armory.
Bitcoind runs fine itself and is fully up to date before I start armory.
Turn off auto bitcoind, run Core manually.
I tried it multiple times and it still crashes.
Here is a new log file.
https://drive.google.com/open?id=0B_gKA8BKU4LGZHNTSGlZVmQ3eWM
Here is a new log file.
https://drive.google.com/open?id=0B_gKA8BKU4LGZHNTSGlZVmQ3eWM
Try running Core manually. Make sure that it is fully synced. Then start Armory. If it complains about Core already running, uncheck the option for it to manage the bitcoind in the settings then restart Armory.
Log files please.
Check that ArmoryDB is running. If it is not, restart Armory.
Check that ArmoryDB is running. If it is not, restart Armory.
I upgraded to 0.13.1 and to 0.95.1, after that armory would freeze scanning the transaction history, I tried the rescan and rebuild same issue.
I finally decided to go all the way and reset to re-downloading the block chain. For the last 2 days the command prompt has been stuck on, "no history to scan"
What should I do?
I finally decided to go all the way and reset to re-downloading the block chain. For the last 2 days the command prompt has been stuck on, "no history to scan"
What should I do?
Jump to: