Delete the content of this folder:
C:\Users\Cx\AppData\Roaming\Armory\databases
Topic: Armory 0.95.1 is out (Read 12949 times)
Hi
I updated my software to the 95.1 and now I get the following error:
-ERROR - 1500150674: (..\lmdb_wrapper.cpp:433) DB version mismatch. Use another dbdir!
Armory never seems to go "online" either?
My Bitcoin core is updated as well.
Any idea why I am getting this error?
logging in C:\Users\Cx\AppData\Roaming\Armory\dbLog.txt
-INFO - 1500150674: (..\main.cpp:23) Running on 4 threads
-INFO - 1500150674: (..\main.cpp:24) Ram usage level: 4
-INFO - 1500150674: (..\BlockUtils.cpp:1338) blkfile dir: C:\Users\Cx\AppData
\Roaming\Bitcoin\blocks
-INFO - 1500150674: (..\BlockUtils.cpp:1339) lmdb dir: C:\Users\Cx\AppData\Ro
aming\Armory\databases
-INFO - 1500150674: (..\lmdb_wrapper.cpp:388) Opening databases...
-ERROR - 1500150674: (..\lmdb_wrapper.cpp:433) DB version mismatch. Use another
dbdir!
I updated my software to the 95.1 and now I get the following error:
-ERROR - 1500150674: (..\lmdb_wrapper.cpp:433) DB version mismatch. Use another dbdir!
Armory never seems to go "online" either?
My Bitcoin core is updated as well.
Any idea why I am getting this error?
logging in C:\Users\Cx\AppData\Roaming\Armory\dbLog.txt
-INFO - 1500150674: (..\main.cpp:23) Running on 4 threads
-INFO - 1500150674: (..\main.cpp:24) Ram usage level: 4
-INFO - 1500150674: (..\BlockUtils.cpp:1338) blkfile dir: C:\Users\Cx\AppData
\Roaming\Bitcoin\blocks
-INFO - 1500150674: (..\BlockUtils.cpp:1339) lmdb dir: C:\Users\Cx\AppData\Ro
aming\Armory\databases
-INFO - 1500150674: (..\lmdb_wrapper.cpp:388) Opening databases...
-ERROR - 1500150674: (..\lmdb_wrapper.cpp:433) DB version mismatch. Use another
dbdir!
ok, thanks for the help goatpig!
Hi Goatpig,
I finally have some time to work on this (last post was 3-26).
I tried to launch Armory again this morning.
I tried your suggestion for the bitcoin.conf, but it still errors out.
Here's the part of Armorylog.txt where the (ERROR) begins, then it loops over and over.
2017-04-09 07:00 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: [u'C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=D:\\Users\\USERNAME\\BitCoin-Blockchain']
2017-04-09 07:00 (INFO) -- SDM.pyc:574 - PID of bitcoind: 8284
2017-04-09 07:00 (INFO) -- SDM.pyc:575 - PID of armory: 4464
2017-04-09 07:00 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: ['.\\guardian.exe', '4464', '8284']
2017-04-09 07:00 (INFO) -- SDM.pyc:756 - Creating proxy in SDM: host=127.0.0.1, port=8332
2017-04-09 07:00 (INFO) -- ArmoryQt.py:5542 - Dashboard switched to auto-InitSync
2017-04-09 07:00 (WARNING) -- SDM.pyc:679 - Overriding not-available state. This should happen 0-5 times
2017-04-09 07:00 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
Let me know if you need more of the log file or any of the DBLog file.
Thanks!
I finally have some time to work on this (last post was 3-26).
I tried to launch Armory again this morning.
I tried your suggestion for the bitcoin.conf, but it still errors out.
Here's the part of Armorylog.txt where the (ERROR) begins, then it loops over and over.
2017-04-09 07:00 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: [u'C:\\Program Files\\Bitcoin\\daemon\\bitcoind.exe', u'-datadir=D:\\Users\\USERNAME\\BitCoin-Blockchain']
2017-04-09 07:00 (INFO) -- SDM.pyc:574 - PID of bitcoind: 8284
2017-04-09 07:00 (INFO) -- SDM.pyc:575 - PID of armory: 4464
2017-04-09 07:00 (INFO) -- ArmoryUtils.pyc:651 - Executing popen: ['.\\guardian.exe', '4464', '8284']
2017-04-09 07:00 (INFO) -- SDM.pyc:756 - Creating proxy in SDM: host=127.0.0.1, port=8332
2017-04-09 07:00 (INFO) -- ArmoryQt.py:5542 - Dashboard switched to auto-InitSync
2017-04-09 07:00 (WARNING) -- SDM.pyc:679 - Overriding not-available state. This should happen 0-5 times
2017-04-09 07:00 (ERROR) -- SDM.pyc:791 - ValueError in bkgd req top blk
Traceback (most recent call last):
File "SDM.pyc", line 765, in __backgroundRequestTopBlock
File "bitcoinrpc_jsonrpc\authproxy.pyc", line 105, in __call__
File "json\__init__.pyc", line 351, in loads
File "json\decoder.pyc", line 366, in decode
File "json\decoder.pyc", line 384, in raw_decode
ValueError: No JSON object could be decoded
Let me know if you need more of the log file or any of the DBLog file.
Thanks!
1) The first few errors are just Qt4 warnings, these are all false positives
2) This:
This means a checksum failed and could not be fixed. I'm not sure what you did to get there. If this is the results of your wallets loading, you should run them through the recovery tool. If you are getting this from restoring a wallet, make sure the wallet ID matches what's on the paper backup.
2) This:
Quote
(WARNING) ArmoryUtils.py:2416 - ***Checksum error! Attempting to fix...
(WARNING) ArmoryUtils.py:2437 - ***Checksum error! Incorrect byte in checksum!
(WARNING) ArmoryUtils.py:2437 - ***Checksum error! Incorrect byte in checksum!
This means a checksum failed and could not be fixed. I'm not sure what you did to get there. If this is the results of your wallets loading, you should run them through the recovery tool. If you are getting this from restoring a wallet, make sure the wallet ID matches what's on the paper backup.
Thanks. The recovery tool ? Is this something in the advanced user ?
1) The first few errors are just Qt4 warnings, these are all false positives
2) This:
This means a checksum failed and could not be fixed. I'm not sure what you did to get there. If this is the results of your wallets loading, you should run them through the recovery tool. If you are getting this from restoring a wallet, make sure the wallet ID matches what's on the paper backup.
2) This:
Quote
(WARNING) ArmoryUtils.py:2416 - ***Checksum error! Attempting to fix...
(WARNING) ArmoryUtils.py:2437 - ***Checksum error! Incorrect byte in checksum!
(WARNING) ArmoryUtils.py:2437 - ***Checksum error! Incorrect byte in checksum!
This means a checksum failed and could not be fixed. I'm not sure what you did to get there. If this is the results of your wallets loading, you should run them through the recovery tool. If you are getting this from restoring a wallet, make sure the wallet ID matches what's on the paper backup.
2.7
Thanks, that's the one I've got.
Now restoring and checking online a wallet I get:
/usr/lib/armory/armoryengine/Transaction.py:2760: SyntaxWarning: import * only allowed at module level
def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
(python2:2713): Gtk-CRITICAL **: IA__gtk_progress_configure: assertion 'value >= min && value <= max' failed
Also in another terminal screen:
/usr/lib/armory/armoryengine/Transaction.py:2760: SyntaxWarning: import * only allowed at module level
def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
(python2:2270): Gtk-WARNING **: Theme directory imported-Humanity/192 of theme Lubuntu has no size field
BDM is ready!
(WARNING) ArmoryUtils.py:2416 - ***Checksum error! Attempting to fix...
(WARNING) ArmoryUtils.py:2437 - ***Checksum error! Incorrect byte in checksum!
**
Any of these sound familiar, do I need to worry ?
Right now armory working still, scanning transaction history.
Thanks
2.7
Getting the Python Syntax Warning, running 0.95.1 on Lubuntu.
What version of Python is the one I should install, as I think some versions are not supported ?
Thanks
What version of Python is the one I should install, as I think some versions are not supported ?
Thanks
Find you bitcoin.conf, remove rpclogin and rpcpassword fields if you have any. Make sure it has a "server=1" entry, then try again. Otherwise, post your logs.
After inquiring about Armory 0.95.1 working with Core 0.14.0 (was told yes), I updated my full node a couple of weeks ago to Core 0.14.0, and Armory worked just fine with it.
Armory would launch, then the second Armory DB window would open (less than a minute later), and I could see all my cold wallet balances. I have no recent transactions.
Yesterday, I opened Armory for the first time in a couple of weeks, and now the wheel just spins forever. Reading through this forum for thoughts, I deleted the contents of the Armory database directory (after making a backup copy), but the files never rebuilt (so I put them back).
Any ideas why this has suddenly stopped working? I haven't made any changes to Core since the initial change a couple of weeks ago. Any way forward to debug (Win 7 x64)?
Any help is greatly appreciated.
OtisG
Armory would launch, then the second Armory DB window would open (less than a minute later), and I could see all my cold wallet balances. I have no recent transactions.
Yesterday, I opened Armory for the first time in a couple of weeks, and now the wheel just spins forever. Reading through this forum for thoughts, I deleted the contents of the Armory database directory (after making a backup copy), but the files never rebuilt (so I put them back).
Any ideas why this has suddenly stopped working? I haven't made any changes to Core since the initial change a couple of weeks ago. Any way forward to debug (Win 7 x64)?
Any help is greatly appreciated.
OtisG
Thanks achow101, but although the armoryDB.exe window shows "Connected to Bitcoin node" and the Armory shows 458619 (which is the latest according to blockchain.info) the error occurs.
Seems I have to try the "broadcast raw signed tx"...sounds complicated, seems I have to read a bit for it
Seems I have to try the "broadcast raw signed tx"...sounds complicated, seems I have to read a bit for it
I click sign offline then sign it and copy the raw transaction, then I pushtx on blockchain.info
One can use this link to even pick who they want to mine it (e.g. if one wants to avoid that bitcoin unlimited $@!%&^* )
http://www.preferredminer.com/
"Instead of broadcasting to the regular mempool, paste a valid raw signed Bitcoin transaction here to be mined by your preferred miner(s)."
Thanks achow101, but although the armoryDB.exe window shows "Connected to Bitcoin node" and the Armory shows 458619 (which is the latest according to blockchain.info) the error occurs.
Seems I have to try the "broadcast raw signed tx"...sounds complicated, seems I have to read a bit for it
Seems I have to try the "broadcast raw signed tx"...sounds complicated, seems I have to read a bit for it
I click sign offline then sign it and copy the raw transaction, then I pushtx on blockchain.info
Thanks achow101, but although the armoryDB.exe window shows "Connected to Bitcoin node" and the Armory shows 458619 (which is the latest according to blockchain.info) the error occurs.
Seems I have to try the "broadcast raw signed tx"...sounds complicated, seems I have to read a bit for it
Seems I have to try the "broadcast raw signed tx"...sounds complicated, seems I have to read a bit for it
I click sign offline then sign it and copy the raw transaction, then I pushtx on blockchain.info
Thanks achow101, but although the armoryDB.exe window shows "Connected to Bitcoin node" and the Armory shows 458619 (which is the latest according to blockchain.info) the error occurs.
Seems I have to try the "broadcast raw signed tx"...sounds complicated, seems I have to read a bit for it
Seems I have to try the "broadcast raw signed tx"...sounds complicated, seems I have to read a bit for it
My armory shows "Connected (458598)" in the bottom right corner, but as of right now we are already at Block 458617. It seems that it does not sync for some reason what might be the reason for my problem above.
Any ideas?
Any ideas?
Restart Armory. Watch the ArmoryDB window (a command prompt window that will have some output) that appears and your current block count in the bottom right hand corner of Armory. When you want to send, make sure that the block count is up to date and that there is no error in the ArmoryDB window that says anything like "Disconnected from Bitcoin node". If you do see that error, or the ArmoryDB window has disappeared, restart Armory, check those again, then send. Repeat until you are able to send.
The bug that is causing this issue has been fixed for 0.96. The 0.96 testing builds will be out soon, after goatpig finishes implementing RBF for 0.96.
The bug that is causing this issue has been fixed for 0.96. The 0.96 testing builds will be out soon, after goatpig finishes implementing RBF for 0.96.
Known bug, fixed in 0.96. You'll have to broadcast the raw signed tx.
Hello,
after spending the last hours following that guide Armory started correctly and showed the correct BTC Amount.
Unfortunately now I do have the next problem: When trying to send Bitcoin to another address this window appears:
Furthermore this message (or trying to send BTC) leads to this line in the dbLog.txt:
Any idea how that can be solved?
Thank you!
Edit:
My armory shows "Connected (458598)" in the bottom right corner, but as of right now we are already at Block 458617. It seems that it does not sync for some reason what might be the reason for my problem above.
Any ideas?
after spending the last hours following that guide Armory started correctly and showed the correct BTC Amount.
Unfortunately now I do have the next problem: When trying to send Bitcoin to another address this window appears:
Furthermore this message (or trying to send BTC) leads to this line in the dbLog.txt:
Code:
-ERROR - 1490306869: (..\SocketObject.cpp:125) poll() error in writeToSocket: 10038
Any idea how that can be solved?
Thank you!
Edit:
My armory shows "Connected (458598)" in the bottom right corner, but as of right now we are already at Block 458617. It seems that it does not sync for some reason what might be the reason for my problem above.
Any ideas?
Jump to: