Topic: Broadcast process failed unexpectedly (Read 1341 times)
Hello Goatpig,
Great to have you here.
Maybe you can help me with my previous post.
Great to have you here.
Maybe you can help me with my previous post.
No CPFP in 0.95 wait for 0.96
I didn't imply I'll do CPFP for 0.96.
Thank you goatpig!
No CPFP in 0.95 wait for 0.96
Pick fee/byte option when sending, it will show you your nodes auto fee rate.
That clears ZC from your DB, not the Bitcoin network. Nothing short of CPFP can help you.
==================================================================================================
I want to delete my unconfirmed transactions from Blockchain.info?
Unconfirmed transaction means that your transaction is being broadcast through the network until some miner write it down into a block. If the unconfirmed transaction is not confirmed into the blockchain after some days, it is deleted from the network.
Nowadays, there is no easy way to delete your unconfirmed transaction. Unless you broadcast it again with a higher fee. In that case, the one that enters first into the blockchain (probably the one with higher fee) will automatically delete the other one from the unconfirmed pool (after a propagation delay).
===================================================================================================
That means I use same wallet to make a new transaction with enough fee to process, all unconfirmed transactions and double spending will be clear in the network. Am I right?
Thank you for your advice . CPFP (Child Pays for Parent), don't know how to perform with armory 095.1.
No CPFP in 0.95 wait for 0.96
Quote
What is the minimum fee can get the confirmation of transaction?
Pick fee/byte option when sending, it will show you your nodes auto fee rate.
Quote
I did clear all unconfirmed transaction in armory. Can I send the bitcoin normally?
That clears ZC from your DB, not the Bitcoin network. Nothing short of CPFP can help you.
==================================================================================================
I want to delete my unconfirmed transactions from Blockchain.info?
Unconfirmed transaction means that your transaction is being broadcast through the network until some miner write it down into a block. If the unconfirmed transaction is not confirmed into the blockchain after some days, it is deleted from the network.
Nowadays, there is no easy way to delete your unconfirmed transaction. Unless you broadcast it again with a higher fee. In that case, the one that enters first into the blockchain (probably the one with higher fee) will automatically delete the other one from the unconfirmed pool (after a propagation delay).
===================================================================================================
That means I use same wallet to make a new transaction with enough fee to process, all unconfirmed transactions and double spending will be clear in the network. Am I right?
Thank you for your advice . CPFP (Child Pays for Parent), don't know how to perform with armory 095.1.
No CPFP in 0.95
Quote
What is the minimum fee can get the confirmation of transaction?
Pick fee/byte option when sending, it will show you your nodes auto fee rate.
Quote
I did clear all unconfirmed transaction in armory. Can I send the bitcoin normally?
That clears ZC from your DB, not the Bitcoin network. Nothing short of CPFP can help you.
Thank you for your advice . CPFP (Child Pays for Parent), don't know how to perform with armory 095.1.
What is the minimum fee can get the confirmation of transaction?
Does those unconfirmed transactions ( https://blockchain.info/address/1KcvKB2zBdFPyMHMJUMjMAa182jPWiKseA ) need to clear?
I did clear all unconfirmed transaction in armory. Can I send the bitcoin normally?
What is the minimum fee can get the confirmation of transaction?
Does those unconfirmed transactions ( https://blockchain.info/address/1KcvKB2zBdFPyMHMJUMjMAa182jPWiKseA ) need to clear?
I did clear all unconfirmed transaction in armory. Can I send the bitcoin normally?
You need to perform a CPFP, which Armory does not support atm.
You need to perform a CPFP, which Armory does not support atm.
I also use both Bitcoin Core (v0.13.2) and Armory (v0.95.1)
I stuck at 0 confirmation.....and then double spending......
I sent bitcoin last week still pending...0 confirmation fee:0.0001btc. Then clear all unconfirmation also "rebuild and rescan" and sent some yesterday, then got double spending. No idea how to solve this!!!
I stuck at 0 confirmation.....and then double spending......
I sent bitcoin last week still pending...0 confirmation fee:0.0001btc. Then clear all unconfirmation also "rebuild and rescan" and sent some yesterday, then got double spending. No idea how to solve this!!!
Had the same issue initially, but restarted both Bitcoin Core (v0.13.2) and Armory (v0.95.1), and then transaction proceeded OK.
Had the same issue initially, but restarted both Bitcoin Core (v0.13.2) and Armory (v0.95.1), and then transaction proceeded OK.
Running 0.13.2
Which version of Core are you running?
Thanks for the help.
Short version: exported the raw hex transaction from Armory, sent via Bitcoin Core, transaction is confirmed and on the blockchain, so the broadcast failed for other (still unknown) reasons.
For anyone interested, here's how I exported the raw hex transaction. The starting point is that you already have the signed .tx file ready on your online computer. In Armory go to "Offline Transactions" > "Sign and/or Broadcast Transaction" then load the signed .tx file and choose "Copy Raw Tx (Hex)". The appropriate contents are copied to the clipboard (it's a long string of hexadecimal digits). Paste the clipboard contents into a text editor and save it, e.g., "raw_transaction.txt".
Close Armory and Bitcoin Core and start again on the command line (or anyhow just make sure you can access bitcoind on the command line):
In my case, the output of the last command was a valid transaction hash for a transaction that is now confirmed on the blockchain.
So my system is producing healthy signed transactions. I would guess the broadcast failure has something to do with how I've got Armory interacting with Bitcoin Core. I will continue to try to troubleshoot the broadcast failure, and report anything I learn. But I'm happy to know I can send through this method. Thanks again.
Short version: exported the raw hex transaction from Armory, sent via Bitcoin Core, transaction is confirmed and on the blockchain, so the broadcast failed for other (still unknown) reasons.
For anyone interested, here's how I exported the raw hex transaction. The starting point is that you already have the signed .tx file ready on your online computer. In Armory go to "Offline Transactions" > "Sign and/or Broadcast Transaction" then load the signed .tx file and choose "Copy Raw Tx (Hex)". The appropriate contents are copied to the clipboard (it's a long string of hexadecimal digits). Paste the clipboard contents into a text editor and save it, e.g., "raw_transaction.txt".
Close Armory and Bitcoin Core and start again on the command line (or anyhow just make sure you can access bitcoind on the command line):
Code:
bitcoind -daemon
RAW_TX=$(cat raw_transaction.txt)
bitcoin-cli sendrawtransaction $RAW_TX
So my system is producing healthy signed transactions. I would guess the broadcast failure has something to do with how I've got Armory interacting with Bitcoin Core. I will continue to try to troubleshoot the broadcast failure, and report anything I learn. But I'm happy to know I can send through this method. Thanks again.
Still the same "broadcast failed" after the rescan. I did the rescan only, so I will try the "rebuild and rescan" next and report back. Thank you.
Won't change anything.
In the broadcast dialog, you can copy the raw tx as hex. Grab that and try to broadcast it straight from Core, you'll get a error message giving you an idea as to why it's failing.
Still the same "broadcast failed" after the rescan. I did the rescan only, so I will try the "rebuild and rescan" next and report back. Thank you.
Do a rescan and try again.
Tried to send a test transaction (within the same offline wallet), since I have not done any transactions in some time. All went smoothly until the final broadcast stage, where I got the "Broadcast process failed unexpectedly" pop up. Based on other instances of this issue that I searched for, I'll mention
Thanks for any help. Here is the relevant bit of armorylog.txt (some stuff ###'d out or shortened with "..."):
and here's the relevant bit of dbLog.txt:
- the blockchain was definitely synced up to the latest block
- Bitcoin Core is 0.13.2, Armory is 0.95.1, OS is Debian stable
- offline signing machine is 32 bit and uses Armory 0.93.2 (seems to sign successfully)
- I've set Armory to not start bitcoind automatically; rather, I always start bitcoin-qt first, and then start Armory
- I've sent successfully sent transactions from this set up before, with Core 0.12.? and Armory 0.94.1 (probably), so I'm thinking maybe I didn't do the update process properly
Thanks for any help. Here is the relevant bit of armorylog.txt (some stuff ###'d out or shortened with "..."):
Code:
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1137 - C++ block utilities loaded successfully
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:651 - Executing popen: free -m
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:651 - Executing popen: ['cat', '/proc/cpuinfo']
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1247 -
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1248 -
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1249 -
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1250 - ************************************************************
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1251 - Invoked: ArmoryQt.py
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1252 - ************************************************************
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1253 - Loading Armory Engine:
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1254 - Armory Version : 0.95.1
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1255 - Armory Build: : None
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1256 - PyBtcWallet Version : 1.35
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1257 - Detected Operating system: Linux
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1258 - OS Variant : debian-8.7-
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1259 - User home-directory : /home/####
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1260 - Satoshi BTC directory : /home/####/.bitcoin/
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1261 - Armory home dir : /home/####/.armory/
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1262 - Detected System Specs :
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1263 - Total Available RAM : 15.59 GB
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1264 - CPU ID string : Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1265 - Number of CPU cores : 4 cores
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1266 - System is 64-bit : True
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1267 - Preferred Encoding : UTF-8
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1268 - Machine Arch : x86_64
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1269 - Available HDD (ARM) : 156 GB
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1270 - Available HDD (BTC) : 156 GB
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1271 -
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1272 - Network Name: Main Network
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1273 - Satoshi Port: 8333
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1274 - Do wlt check: True
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1275 - Named options/arguments to armoryengine.py:
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - thread_count : -1
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - rescan : False
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - ignoreAllZC : False
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - rescanBalance : False
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - disableModules : False
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - port : None
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - interport : 8223
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - skipStatsReport : False
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - forceWalletCheck: False
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - regtest : False
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - rebuild : False
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - nettimeout : 2
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - datadir : DEFAULT
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - clearMempool : False
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - offline : False
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - coverageOutputDir: None
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - armoryDBDir : DEFAULT
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - armorydb_port : 9001
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - satoshiPort : DEFAULT
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - useTorSettings : False
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - netlog : False
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - keypool : 100
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - coverageInclude : None
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - forceOnline : False
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - skipAnnounceCheck: False
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - redownload : False
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - armorydb_ip : 127.0.0.1
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - multisigFile : DEFAULT
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - ram_usage : -1
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - testAnnounceCode: False
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - mtdebug : False
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - logDisable : False
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - settingsPath : /home/####/.armory/ArmorySettings.txt
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - db_type : DB_FULL
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - doDebug : False
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - enableDetSign : True
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - disableConfPermis: False
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - testnet : False
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - rpcport : DEFAULT
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - satoshiHome : DEFAULT
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - satoshiRpcport : DEFAULT
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - logFile : /home/####/.armory/armorylog.txt
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1277 - verbosity : None
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1278 - Other arguments:
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1281 - ************************************************************
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:1684 - C++ block utilities loaded successfully
2017-01-15 12:14 (INFO) -- BDM.py:367 - Using the asynchronous/multi-threaded BlockDataManager.
2017-01-15 12:14 (INFO) -- BDM.py:368 - Blockchain operations will happen in the background.
2017-01-15 12:14 (INFO) -- BDM.py:369 - Devs: check TheBDM.getState() before asking for data.
2017-01-15 12:14 (INFO) -- BDM.py:370 - Registering addresses during rescans will queue them for
2017-01-15 12:14 (INFO) -- BDM.py:371 - inclusion after the current scan is completed.
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:3597 - Using settings file: /home/####/.armory/ArmorySettings.txt
2017-01-15 12:14 (INFO) -- ArmoryQt.py:2485 - loadWalletsAndSettings
2017-01-15 12:14 (INFO) -- ArmoryQt.py:2539 - Loading wallets...
2017-01-15 12:14 (INFO) -- ArmoryQt.py:2598 - Number of wallets read in: 2
2017-01-15 12:14 (INFO) -- ArmoryQt.py:2603 - Wallet (#########): "Primary Wallet (Watch) " (No Encryption)
2017-01-15 12:14 (INFO) -- ArmoryQt.py:2603 - Wallet (########): "Primary Wallet " (Encrypted)
2017-01-15 12:14 (INFO) -- ArmoryQt.py:2153 - Setting up networking...
2017-01-15 12:14 (INFO) -- ArmoryQt.py:1412 - setupUriRegistration
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:651 - Executing popen: gconftool-2 --get /desktop/gnome/url-handlers/bitcoin/command
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:651 - Executing popen: xdg-mime query default x-scheme-handler/bitcoin
2017-01-15 12:14 (INFO) -- ArmoryQt.py:546 - Usermode: Advanced
2017-01-15 12:14 (INFO) -- ArmoryQt.py:1708 - Changing usermode:
2017-01-15 12:14 (INFO) -- ArmoryQt.py:1709 - From: Advanced
2017-01-15 12:14 (INFO) -- ArmoryQt.py:1717 - To: Advanced
2017-01-15 12:14 (INFO) -- ArmoryQt.py:2217 - startBitcoindIfNecessary
2017-01-15 12:14 (INFO) -- ArmoryQt.py:2257 - setSatoshiPaths
2017-01-15 12:14 (INFO) -- SDM.py:382 - Reading bitcoin.conf file
2017-01-15 12:14 (INFO) -- SDM.py:756 - Creating proxy in SDM: host=127.0.0.1, port=8332
2017-01-15 12:14 (INFO) -- ArmoryQt.py:2257 - setSatoshiPaths
2017-01-15 12:14 (INFO) -- ArmoryUtils.py:651 - Executing popen: ['/home/####/Downloads/BitcoinArmory-0.95.1/ArmoryDB', '--db-type="DB_FULL"', '--spawnId="EdJHDmQJGqjy18yjw8q1ffoLhzUL4UCrtryoC3ESE9Ux"', '--satoshi-datadir="/home/####/.bitcoin/blocks"', '--datadir="/home/####/.armory/"', '--dbdir="/home/####/.armory/databases"']
2017-01-15 12:14 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 1
2017-01-15 12:14 (INFO) -- ArmoryQt.py:2289 - loadBlockchainIfNecessary
2017-01-15 12:14 (INFO) -- ArmoryQt.py:2307 - Setting netmode: 1
2017-01-15 12:14 (INFO) -- ArmoryQt.py:5645 - Dashboard switched to "Scanning" mode
2017-01-15 12:14 (INFO) -- ArmoryQt.py:5645 - Dashboard switched to "Scanning" mode
2017-01-15 12:15 (INFO) -- ArmoryQt.py:2886 - Current block number: 448333
2017-01-15 12:16 (INFO) -- TxFrames.py:1917 - Selected transaction file to load: /home/####/Documents/armory_########_.signed.tx
2017-01-15 12:16 (INFO) -- (PPRINT from ArmoryQt.py:3491)
01000000 019ed8c2 ...
00
2017-01-15 12:16 (INFO) -- (PPRINT from ArmoryQt.py:3492)
Transaction:
...
2017-01-15 12:16 (INFO) -- ArmoryQt.py:3496 - Sending Tx, ################################################################
2017-01-15 12:17 (INFO) -- ArmoryQt.py:6368 - BDM is safe for clean shutdown
2017-01-15 12:17 (INFO) -- SDM.py:588 - Called stopBitcoind
2017-01-15 12:17 (INFO) -- SDM.py:594 - ...but bitcoind is not running, to be able to stop
2017-01-15 12:17 (INFO) -- ArmoryQt.py:6386 - Attempting to close the main window!
Code:
Log file opened at 1484500468: /home/####/.armory/dbLog.txt
-INFO - 1484500468: (main.cpp:23) Running on 4 threads
-INFO - 1484500468: (main.cpp:24) Ram usage level: 4
-INFO - 1484500468: (BlockUtils.cpp:1338) blkfile dir: /home/####/.bitcoin/blocks
-INFO - 1484500468: (BlockUtils.cpp:1339) lmdb dir: /home/####/.armory/databases
-INFO - 1484500468: (lmdb_wrapper.cpp:388) Opening databases...
-INFO - 1484500469: (BlockUtils.cpp:1521) Executing: doInitialSyncOnLoad
-INFO - 1484500469: (DatabaseBuilder.cpp:169) Reading headers from db
-INFO - 1484500469: (BDM_Server.cpp:797) registered bdv: 0d7d4bf43f5c3f48e80d
-INFO - 1484500501: (DatabaseBuilder.cpp:208) Found 448326 headers in db
-INFO - 1484500502: (DatabaseBuilder.cpp:51) updating HEADERS db
-INFO - 1484500505: (DatabaseBuilder.cpp:477) Found next block after skipping 131062bytes
-INFO - 1484500505: (DatabaseBuilder.cpp:268) parsed block file #741
-DEBUG - 1484500505: (Blockchain.cpp:242) Organizing chain
-INFO - 1484500505: (DatabaseBuilder.cpp:56) updated HEADERS db in 0.920443s
-INFO - 1484500505: (DatabaseBuilder.cpp:106) scanning new blocks from #448326 to #448333
-INFO - 1484500505: (BlockchainScanner.cpp:650) scanned from height #448326 to #448333
-INFO - 1484500505: (DatabaseBuilder.cpp:156) scanned new blocks in 0.100229s
-INFO - 1484500505: (DatabaseBuilder.cpp:160) init db in 9.35692s
-INFO - 1484500505: (BlockUtils.cpp:1636) Enabling zero-conf tracking
-INFO - 1484500678: (BDM_Server.cpp:826) unregistered bdv: 0d7d4bf43f5c3f48e80d
-INFO - 1484500678: (BDM_Server.cpp:737) proceeding to shutdown
-ERROR - 1484500681: (BitcoinP2P.cpp:851) caught SocketError exception in processDataStackThread: POLLNVAL in readFromSocketThread
-INFO - 1484500687: (BitcoinP2P.cpp:804) Disconnected from Bitcoin node
-ERROR - 1484500687: (BDM_mainthread.cpp:257) caught exception in main thread: terminate
Jump to: