Quote
Results is a string saying it's missing inputs ?!?
Means the tx is signing for outputs that do not exist on the chain your node is running on.
Topic: tx broadcast timed out (Read 1859 times)
Means the tx is signing for outputs that do not exist on the chain your node is running on.
Start bitcoinqt with -disablewallet and use the second GUI tab
I have the same issue with 0.96.4 and core 0.16.1 ... I've opened a separate issue here with all the logs and extra details. I'm using armoryd rather than the UI and run on regtest. Seems like
when it happens it corrupts the db (remove the databases folder and relaunching armorydb and armoryd --rebuild doesn't do the trick (gets to block 39 out of 289).
https://bitcointalksearch.org/topic/armorydpy-sendasciitx-times-out-when-trying-to-broadcast-fully-signed-tx-5026167 for my issue.
Also, tried to avoid the problem by not using sendasciitx on armoryd, but rather get the hex for the tx and then broadcast with bitcoin-qt and / bitcoin-cli. Results is a string saying it's missing inputs ?!?
Start bitcoinqt with -disablewallet and use the second GUI tab
I've got the same problem. How do I broadcast the raw transaction from core?
This is your raw tx
Broadcast it straight from your node and see what error message you get.
Code:
01000000 039a8715 5cdf6913 56d1e77a 8fe4e5fe 8f1418e4 4b8d7f40 c0f82719
3c6f0e9d 5e000000 008a4730 44022060 916725d6 8048d35f 76abd0a1 91caaab7
b8040c1a b09ee0d0 7bb41391 99681302 202110d3 8860427b 2a3da7eb f585ee46
de3774bf 164aa09b c8b73136 3ec6b096 b4014104 c36e8d25 d6c7d7d9 6f5c8b0b
5927c003 2d58c9b8 0be903d0 a4bef1cb 1b16337f acb25199 c551383d 97a2ec75
3d0fcad8 be813d52 21547a70 e1258be9 a8088f43 ffffffff 5e8f1b68 ab43d314
a6a81246 f25177c8 08622c7d 0a125948 32f76cfa cc2a3a01 46000000 8b483045
0221008a 2e1eda2a a361a336 d816aff4 85c6aaf0 19066dbc 7d45ebd9 d06ab1e9
68066f02 2054e61c c5d1c7f9 8f16029d 397e1e8c ecba0833 625ff04b f28d3c01
1118c5d4 33014104 c36e8d25 d6c7d7d9 6f5c8b0b 5927c003 2d58c9b8 0be903d0
a4bef1cb 1b16337f acb25199 c551383d 97a2ec75 3d0fcad8 be813d52 21547a70
e1258be9 a8088f43 ffffffff b1069206 6b4ad3da 554b0c75 d57ff6f6 efde8272
f6498f97 856bb9a2 5f5c9d24 00000000 8a473044 022006c8 c36f498e a9b537a4
e3187018 d2996f60 01451087 ef65d86d b6fccc8a f6170220 7116b9e3 6be2bf1e
c991f85f b9a45068 6f9d39f4 7e433e08 7fd0e113 b5b9af44 014104c3 6e8d25d6
c7d7d96f 5c8b0b59 27c0032d 58c9b80b e903d0a4 bef1cb1b 16337fac b25199c5
51383d97 a2ec753d 0fcad8be 813d5221 547a70e1 258be9a8 088f43ff ffffff02
206fb001 00000000 1976a914 53c8f014 2c614cc4 d4f550a1 c3a21e1e 2a326a8a
88acc028 6b010000 00001976 a914338e 21d3dea1 d23071de d30d6724 89210f1e
c50d88ac a51f0700
3c6f0e9d 5e000000 008a4730 44022060 916725d6 8048d35f 76abd0a1 91caaab7
b8040c1a b09ee0d0 7bb41391 99681302 202110d3 8860427b 2a3da7eb f585ee46
de3774bf 164aa09b c8b73136 3ec6b096 b4014104 c36e8d25 d6c7d7d9 6f5c8b0b
5927c003 2d58c9b8 0be903d0 a4bef1cb 1b16337f acb25199 c551383d 97a2ec75
3d0fcad8 be813d52 21547a70 e1258be9 a8088f43 ffffffff 5e8f1b68 ab43d314
a6a81246 f25177c8 08622c7d 0a125948 32f76cfa cc2a3a01 46000000 8b483045
0221008a 2e1eda2a a361a336 d816aff4 85c6aaf0 19066dbc 7d45ebd9 d06ab1e9
68066f02 2054e61c c5d1c7f9 8f16029d 397e1e8c ecba0833 625ff04b f28d3c01
1118c5d4 33014104 c36e8d25 d6c7d7d9 6f5c8b0b 5927c003 2d58c9b8 0be903d0
a4bef1cb 1b16337f acb25199 c551383d 97a2ec75 3d0fcad8 be813d52 21547a70
e1258be9 a8088f43 ffffffff b1069206 6b4ad3da 554b0c75 d57ff6f6 efde8272
f6498f97 856bb9a2 5f5c9d24 00000000 8a473044 022006c8 c36f498e a9b537a4
e3187018 d2996f60 01451087 ef65d86d b6fccc8a f6170220 7116b9e3 6be2bf1e
c991f85f b9a45068 6f9d39f4 7e433e08 7fd0e113 b5b9af44 014104c3 6e8d25d6
c7d7d96f 5c8b0b59 27c0032d 58c9b80b e903d0a4 bef1cb1b 16337fac b25199c5
51383d97 a2ec753d 0fcad8be 813d5221 547a70e1 258be9a8 088f43ff ffffff02
206fb001 00000000 1976a914 53c8f014 2c614cc4 d4f550a1 c3a21e1e 2a326a8a
88acc028 6b010000 00001976 a914338e 21d3dea1 d23071de d30d6724 89210f1e
c50d88ac a51f0700
Broadcast it straight from your node and see what error message you get.
Looks like your node rejected the tx.
Try to send it again with the latest builds then post your log files again.
Try to send it again with the latest builds then post your log files again.
I install it and rebuild the database but i have the same problem as befor
Hello,
i have the same problem i use Armory 0.96 Windows 2016 x64 and BitcoinCore 14.1 x64.
My BitcoinCore Installation is on a Networkdrive.
I can receive BTC but dosent can sent it with this error:
tx broadcast timed out
https://pastebin.com/1k0XxPjJ
best regards
i have the same problem i use Armory 0.96 Windows 2016 x64 and BitcoinCore 14.1 x64.
My BitcoinCore Installation is on a Networkdrive.
I can receive BTC but dosent can sent it with this error:
tx broadcast timed out
https://pastebin.com/1k0XxPjJ
best regards
Can I import the wallets into a more stable wallet application?
You can extract your private keys from Armory and import them into any wallet with an import feature.
Hello again :-(
The tx broadcast timed out message is back.
Armory: 0.96
Core: 0.14.1, 0.13.2
Can I import the wallets into a more stable wallet application?
The tx broadcast timed out message is back.
Armory: 0.96
Core: 0.14.1, 0.13.2
Can I import the wallets into a more stable wallet application?
You're gonna have to delete your Armory DB folder and rebuild it from scratch.
I did it.
After few "not responding" I was able to make a transfer.
Thank you very much!
I've also tried to broadcast it manually. And it resulted in this kind of transaction, which says it's a double spend:
https://blockchain.info/tx/6778c2fec5aa097793b710fe09365db2c8310924d01c336d38fa832ed1065a9a
https://blockchain.info/tx/6778c2fec5aa097793b710fe09365db2c8310924d01c336d38fa832ed1065a9a
Could you please help me?
I'm struggling with trying to make a single transaction for about 4 days already. I did multiple Rescans and Rebuilds of database and factory resets. Nothing helps.
I use bitcoin core v.0.13.2 and Armory 0.96-beta-a3d01aa722.
Here's my log file:
https://ufile.io/7p9ol
Sometimes I get a message about tx broadcast timed out. Sometimes Armory creates transaction but it's not appearing on blockchain.info.
I'm struggling with trying to make a single transaction for about 4 days already. I did multiple Rescans and Rebuilds of database and factory resets. Nothing helps.
I use bitcoin core v.0.13.2 and Armory 0.96-beta-a3d01aa722.
Here's my log file:
https://ufile.io/7p9ol
Sometimes I get a message about tx broadcast timed out. Sometimes Armory creates transaction but it's not appearing on blockchain.info.
You're gonna have to delete your Armory DB folder and rebuild it from scratch.
1) I have restarted the PC again.
2) Start the Armory app
3) Try to initiate a transfer
4) The same issue when I press Send nothing happens but in the logs I can see the bellow lines every time I pressed Send
2017-05-09 22:47 (INFO) -- TxFrames.pyc:689 - Change address behavior: NewAddr
2017-05-09 22:47 (ERROR) -- Traceback (most recent call last):
File "ui\TxFrames.pyc", line 805, in createTxAndBroadcast
File "ui\TxFrames.pyc", line 764, in validateInputsGetUSTX
File "armoryengine\Transaction.pyc", line 2284, in createFromTxOutSelection
File "armoryengine\Transaction.pyc", line 2193, in createFromPyTx
File "CppBlockUtils.pyc", line 2988, in getTxByHash
DbErrorMsg: >
2) Start the Armory app
3) Try to initiate a transfer
4) The same issue when I press Send nothing happens but in the logs I can see the bellow lines every time I pressed Send
2017-05-09 22:47 (INFO) -- TxFrames.pyc:689 - Change address behavior: NewAddr
2017-05-09 22:47 (ERROR) -- Traceback (most recent call last):
File "ui\TxFrames.pyc", line 805, in createTxAndBroadcast
File "ui\TxFrames.pyc", line 764, in validateInputsGetUSTX
File "armoryengine\Transaction.pyc", line 2284, in createFromTxOutSelection
File "armoryengine\Transaction.pyc", line 2193, in createFromPyTx
File "CppBlockUtils.pyc", line 2988, in getTxByHash
DbErrorMsg:
I have restarted PC many times.
There's a zombie DB process. Kill it and restart.
Post your armorylog.txt
I can't help you if you don't show me this one file, regardless of the issue.
Check your PM!
Jump to: