Topic: TXN -mempool-conflict (Read 330 times)
To be honest, I load it maybe once a month or so... Just to let it sync up. I tend to use my other wallets more.
Hi, i deleted the mempool.dat with bitcoin and armory not running(i think it was running when i tried doing it in an earlier thread) and when i loaded armory up the btc had been transferred to my intended destination...many thanks for all your help. I only really use btc about 4-6 times a year now, i used to use it more often and had no problems, seems i get trouble with it quite a lot recently, how often would you suggest i fire up Armory to keep it more reliable?
Wherever your Bitcoin Core data directory is... refer: https://en.bitcoin.it/wiki/Data_directory
You should find a file called "mempool.dat". Before you delete it, you need to make sure that Bitcoin Core (and/or bitcoind) are NOT running.
You should find a file called "mempool.dat". Before you delete it, you need to make sure that Bitcoin Core (and/or bitcoind) are NOT running.
Hi, thanks for the quick response, i have not deleted anything in the bitcoincore program, only in armory, could you give me the correct path i will need to do this please?
Ok... looking at your logs, the problem seems to be Bitcoin Core not wanting to send your transaction:
Then, you get the TXN-mempool-conflict error:
Anyway... I was able to simply broadcast the transaction and it has now confirmed: https://www.blockchain.com/en/btc/tx/45dc1e34b834ed5a8c27f525623c9961847d60347180019815cad0b20ca4d978
Given that the transaction was able to be broadcast, then this points to your Bitcoin Core having a conflicting transaction in it's local mempool for some reason... but you said you'd deleted that??!?
Quote
2018-07-16 06:52:01 (INFO) -- ArmoryQt.py:3124 - Sending Tx, 78d9a40cb2d0ca159801807134607d8461993c6225f5278c5aed34b8341edc45
2018-07-16 06:52:01 (INFO) -- ArmoryQt.py:3138 - Failed to broadcast Tx through P2P
2018-07-16 06:52:01 (ERROR) -- ArmoryQt.py:3159 - Transaction was not accepted by the Satoshi client
2018-07-16 06:52:01 (INFO) -- ArmoryQt.py:3138 - Failed to broadcast Tx through P2P
2018-07-16 06:52:01 (ERROR) -- ArmoryQt.py:3159 - Transaction was not accepted by the Satoshi client
Then, you get the TXN-mempool-conflict error:
Quote
2018-07-16 06:52:01 (ERROR) -- ArmoryQt.py:3164 - Failure message: txn-mempool-conflict
Given the timestamps... I think it's part of the same error.Anyway... I was able to simply broadcast the transaction and it has now confirmed: https://www.blockchain.com/en/btc/tx/45dc1e34b834ed5a8c27f525623c9961847d60347180019815cad0b20ca4d978
Given that the transaction was able to be broadcast, then this points to your Bitcoin Core having a conflicting transaction in it's local mempool for some reason... but you said you'd deleted that??!?
Hi, just to give you as much info as i can....i have also been clearing any unconfirmed and been generous with the fee, still get the 18.TXN mempool conflict error message
Hi, don't know if this is relevant, but i just fired up bitcoincore on it's own and the balance says 0.00, my btc's are showing up in my armory account? Just mentioning this as i was told in an earlier post that i could send a 'raw transaction?' via bitcoincore, but i guess that won't be possible if I have nothing in my bitcoincore wallet?
Hi, i think i followed your instructions correctly and Armory seems back to normal, thankyou. Tried to send btc but got the 'TXN-mempool-conflict' error message again and it won't send? Here is the log https://pastebin.com/hkq08gVj
1) Delete the content of this folder: C:\Users\Luke\AppData\Roaming\Armory\databases
2) Start BitcoinQt, leave it running
3) Delete your logs (armorylog.txt and dbLog.txt)
4) From the command line, browse to your Armory install folder (C:\Program Files (x86)\Armory\) and run "ArmoryDB.exe"
5) Start ArmoryQt the usual way, let it catch up, report here. If it fails, post the fresh logs.
2) Start BitcoinQt, leave it running
3) Delete your logs (armorylog.txt and dbLog.txt)
4) From the command line, browse to your Armory install folder (C:\Program Files (x86)\Armory\) and run "ArmoryDB.exe"
5) Start ArmoryQt the usual way, let it catch up, report here. If it fails, post the fresh logs.
Hi, core has caught up and my wallet balance is 0.00 and there are no records of any transactions in the past? I opened Armory and it won't load the GUI, it just has a load-up box which says 'Loading 100%', it does not go to updating blocks or anything, just stays on that loading-up box?
Wait till Core catches up, then start Armory.
Hi, got bitcoincore GUI up, it says it is 3 days behind. Progress is at 99.71% and it is progressing at 0.03% per hour, i have 2 nodes active...is this normal? My wallet is saying that there is 0.00 btc in there, is this right?
Start BitcoinQt, does it load properly?
Hi, you probaly won't believe this....how do i open the bitcoincore GUI? I click on bitcoincore to load it up and it just stays on the done loading screen? Can't seem to open bitcoincore so that i can send the raw transaction?
Hi, just loaded up bitcoincore and can't find the send raw data command, how do i execute it (also, should i be using the 32 or 64 bit version?
Help -> Debug Window -> ConsoleThe command format is:
Code:
sendrawtransaction RAW_TRANSACTION_HEX
It doesn't really matter if you use 32bit or 64bit... that's more of an Operating System thing (if you're using 64bit windows, you should use 64bit Bitcoin Core).
Hi,i see you highlighted my fee, is that way too much? Any ideas how much i am giving them, this all baffles me, and can i bring the fee down before i send this if it is too high?
Also to clarify, i can copy and paste that raw transaction at the top of your last post and send it directly from bitcoincore?
You can probably bring the fee down quite a bit... 70000 sats is quite a bit, ~USD$4... your transaction is only 224 bytes, so with the current network state, any more than 500 sats is probably unnecessary. Also to clarify, i can copy and paste that raw transaction at the top of your last post and send it directly from bitcoincore?
To change it, you'd need to redo the transaction in Armory and set a lower fee...
Hi, just loaded up bitcoincore and can't find the send raw data command, how do i execute it (also, should i be using the 32 or 64 bit version?
Hi,i see you highlighted my fee, is that way too much? Any ideas how much i am giving them, this all baffles me, and can i bring the fee down before i send this if it is too high?
Also to clarify, i can copy and paste that raw transaction at the top of your last post and send it directly from bitcoincore?
Also to clarify, i can copy and paste that raw transaction at the top of your last post and send it directly from bitcoincore?
Ok, so your "raw" transaction is this:
If you are happy with all of that data (ie. sending 10490483 satoshis or 0.10490483 from 17m2JVuSzyzFafWiiecJjGAW52HzRUCrk1 to 1LbsJkEfAwr2od324NLvDTFPqo7uATfuv3 with a 70000 sat fee!!?!
)...
I'd suggest confirming it all yourself using: https://live.blockcypher.com/btc/decodetx/ or https://coinb.in/#verify, you can then "push" that transaction to the network (using https://live.blockcypher.com/btc/pushtx/ or https://coinb.in/#broadcast)... or use the sendrawtransaction command with Bitcoin Core to send that raw data.
NOTE: this won't solve your issues with Armory/Bitcoin Core... but it will get your BTC sent if that is an urgent requirement.
Code:
0100000001bab68eb6c47543c8fc09e9440f4398bf67e4105e48c578feb0956e3454151722000000008b483045022100aa7228ded24c8344b016836aeba57e57f1ca7d3e08da47f30c1f5805fc5a38730220123b3f04cfb570f358ac2140aefdbc685535425e57eba83b6265d4f47a14253f0141043740f7db5616626e52a5df8b54ce4a66dcca603db54f861aeec42d3270f01c9da1c4b5787fd19ffe613c98b71cea552a4355b97006d96354111de9046b484705fdffffff017312a000000000001976a914d70286a0b68da0df83b7dbd86d02b0d90e93a76688ac241c0800
That will decode to this:Quote
{
"addresses": [
"17m2JVuSzyzFafWiiecJjGAW52HzRUCrk1",
"1LbsJkEfAwr2od324NLvDTFPqo7uATfuv3"
],
"block_height": -1,
"block_index": -1,
"confirmations": 0,
"double_spend": false,
"fees": 70000,
"hash": "967f8dce8ff6cd0cba70fee2843c4ddeb9e4ab193f66551606dd855ee983fc5c",
"inputs": [
{
"addresses": [
"17m2JVuSzyzFafWiiecJjGAW52HzRUCrk1"
],
"age": 530694,
"output_index": 0,
"output_value": 10560483,
"prev_hash": "22171554346e95b0fe78c5485e10e467bf98430f44e909fcc84375c4b68eb6ba",
"script": "483045022100aa7228ded24c8344b016836aeba57e57f1ca7d3e08da47f30c1f5805fc5a3873022 0123b3f04cfb570f358ac2140aefdbc685535425e57eba83b6265d4f47a14253f0141043740f7db 5616626e52a5df8b54ce4a66dcca603db54f861aeec42d3270f01c9da1c4b5787fd19ffe613c98b 71cea552a4355b97006d96354111de9046b484705",
"script_type": "pay-to-pubkey-hash",
"sequence": 4294967293
}
],
"lock_time": 531492,
"opt_in_rbf": true,
"outputs": [
{
"addresses": [
"1LbsJkEfAwr2od324NLvDTFPqo7uATfuv3"
],
"script": "76a914d70286a0b68da0df83b7dbd86d02b0d90e93a76688ac",
"script_type": "pay-to-pubkey-hash",
"value": 10490483
}
],
"preference": "high",
"received": "2018-07-15T02:53:17.037085381Z",
"relayed_by": "54.198.32.59",
"size": 224,
"total": 10490483,
"ver": 1,
"vin_sz": 1,
"vout_sz": 1
}
"addresses": [
"17m2JVuSzyzFafWiiecJjGAW52HzRUCrk1",
"1LbsJkEfAwr2od324NLvDTFPqo7uATfuv3"
],
"block_height": -1,
"block_index": -1,
"confirmations": 0,
"double_spend": false,
"fees": 70000,
"hash": "967f8dce8ff6cd0cba70fee2843c4ddeb9e4ab193f66551606dd855ee983fc5c",
"inputs": [
{
"addresses": [
"17m2JVuSzyzFafWiiecJjGAW52HzRUCrk1"
],
"age": 530694,
"output_index": 0,
"output_value": 10560483,
"prev_hash": "22171554346e95b0fe78c5485e10e467bf98430f44e909fcc84375c4b68eb6ba",
"script": "483045022100aa7228ded24c8344b016836aeba57e57f1ca7d3e08da47f30c1f5805fc5a3873022 0123b3f04cfb570f358ac2140aefdbc685535425e57eba83b6265d4f47a14253f0141043740f7db 5616626e52a5df8b54ce4a66dcca603db54f861aeec42d3270f01c9da1c4b5787fd19ffe613c98b 71cea552a4355b97006d96354111de9046b484705",
"script_type": "pay-to-pubkey-hash",
"sequence": 4294967293
}
],
"lock_time": 531492,
"opt_in_rbf": true,
"outputs": [
{
"addresses": [
"1LbsJkEfAwr2od324NLvDTFPqo7uATfuv3"
],
"script": "76a914d70286a0b68da0df83b7dbd86d02b0d90e93a76688ac",
"script_type": "pay-to-pubkey-hash",
"value": 10490483
}
],
"preference": "high",
"received": "2018-07-15T02:53:17.037085381Z",
"relayed_by": "54.198.32.59",
"size": 224,
"total": 10490483,
"ver": 1,
"vin_sz": 1,
"vout_sz": 1
}
If you are happy with all of that data (ie. sending 10490483 satoshis or 0.10490483 from 17m2JVuSzyzFafWiiecJjGAW52HzRUCrk1 to 1LbsJkEfAwr2od324NLvDTFPqo7uATfuv3 with a 70000 sat fee!!?!
)... I'd suggest confirming it all yourself using: https://live.blockcypher.com/btc/decodetx/ or https://coinb.in/#verify, you can then "push" that transaction to the network (using https://live.blockcypher.com/btc/pushtx/ or https://coinb.in/#broadcast)... or use the sendrawtransaction command with Bitcoin Core to send that raw data.
NOTE: this won't solve your issues with Armory/Bitcoin Core... but it will get your BTC sent if that is an urgent requirement.
Hi, i don't know how to broadcast raw transanction, armory won't load up online. I run bitcoincore in the background of armory, but have loaded bitcoincore up without armory being loaded a few times. Sorry, for not being much help
No, the ones in my post work fine... 
(although you can "edit" your previous post and just add a space between each link (ie. just before the http: part
As for the issue, there seems to be some issue with your "satoshi client" (ie. Bitcoin Core) broadcasting your transaction. Then, when you attempt to send again, you get the txn-mempool-conflict error as the transaction is already in your "local" mempool.
You might want to try broadcasting the raw transaction manually, and see what the error message displayed it... it might give you a better idea of what the issue is. Are you running Bitcoin Core GUI or are you just letting Armory run bitcond?
(although you can "edit" your previous post and just add a space between each link (ie. just before the http: part As for the issue, there seems to be some issue with your "satoshi client" (ie. Bitcoin Core) broadcasting your transaction. Then, when you attempt to send again, you get the txn-mempool-conflict error as the transaction is already in your "local" mempool.
You might want to try broadcasting the raw transaction manually, and see what the error message displayed it... it might give you a better idea of what the issue is. Are you running Bitcoin Core GUI or are you just letting Armory run bitcond?
Jump to: