tx broadcast timed out

[iradu]

Hello,

Since I've upgrade Armory to 0.96 I always got the error  tx broadcast timed out. I've tried to increase the fee but the same error occur. Can you help me with some advices?

Thank you very much!

[1715000296]

1715000296

[1715000296]

1715000296

[1715000296]

1715000296

[1715000296]

1715000296

[1715000296]

1715000296

[achow101]

What version of Bitcoin Core are you using? Can you please post the Armory log files?

[iradu]

The Bitcoin Core version is 0.14.1rss. Both of them on 64 bit.

Which logs do you want? Can I sent them only to you?

[streamholder]

Same here! Logs show nothing interesting, but if you tell which ones I'll gladly post them.

EDIT: This is most likely what's causing the issue. Testing the solution now.
EDIT2: I confirm that 0.96 still has the issue! Downgrading to Core 0.13.2 fixed it for now.

[iradu]

Thank you very much!

What is your Armory version?

[streamholder]

Thank you very much!

What is your Armory version?

As I mentioned, I'm using 0.96.

What confused me initially is that issue was thought to be present in 0.95.1 but not in 0.96; I've now verified this is in fact incorrect, the issue is present in both versions.
The only solution is to downgrade Bitcoin Core to 0.13.2. This will fix the problem presumably for both Armory 0.95.1 and 0.96. I can only vouch for 0.96 as it is the version I'm using now.

[iradu]

I've asked about the version because you said " I confirm that 0.96 still has the issue! Downgrading to Core 0.13.2 fixed it for now."  So event the issue is the Core 0.14 even the combination 0.96 with 0.14.

Anyway thank you very much for your answers.

Best regards,

[achow101]

As I mentioned, I'm using 0.96.

What confused me initially is that issue was thought to be present in 0.95.1 but not in 0.96; I've now verified this is in fact incorrect, the issue is present in both versions.
The only solution is to downgrade Bitcoin Core to 0.13.2. This will fix the problem presumably for both Armory 0.95.1 and 0.96. I can only vouch for 0.96 as it is the version I'm using now.

That is incorrect. The issue must lie elsewhere because many people have reported that 0.96 does in fact work with Bitcoin Core 0.14.0+. I have been running Armory with the patch that fixed that particular bug for several months now with builds of Bitcoin Core that has the code that causes the issue.

What you are experiencing are the same symptoms, not necessarily the same causes of that issue. Can you please post all of the armory log files. You can get them by going to File > Export Log File and it will put them all into one large text file. You can then copy and paste the contents of that file into a post here or onto a site like https://pastebin.com/ and post the link here. Those log files do not contain any sensitive information that can result in people stealing your private keys, but it does reveal some information about your computer and the transactions that you have sent.

[iradu]

I've uninstalled Core and Armory and removed the Core's folders. Installed them again and now I need to wait until the core will synchronize :-(.  I'll provide updates after.

Thank you very much !

[streamholder]

I've uninstalled Core and Armory and removed the Core's folders. Installed them again and now I need to wait until the core will synchronize :-(.  I'll provide updates after.

Thank you very much !

That was not necessary. If you still have the files in the recycle bin I strongly suggest you to restore them and then just install 0.13.2. It will work with the same blockchain downloaded by 0.14.1. There's really no need to waste the time and the bandwidth.

[iradu]

I've uninstalled Core and Armory and removed the Core's folders. Installed them again and now I need to wait until the core will synchronize :-(.  I'll provide updates after.

Thank you very much !

That was not necessary. If you still have the files in the recycle bin I strongly suggest you to restore them and then just install 0.13.2. It will work with the same blockchain downloaded by 0.14.1. There's really no need to waste the time and the bandwidth.

It's already at 101GB and I installed Core 0.14.1

[iradu]

Well,

I've tried to send some BTC, but I wasn't able. After I pressed send nothing happens and at some point windows said that the application stopped and I should close it.

Armory: 0.96
Core 0.14.1 and 0.13.2

[goatpig]

Post your armorylog.txt

[iradu]

Well, after a few reinstall armory and core, now I have another issue.  When I try to send some btc, I can select the address, the amount, the fee sometime is filled, sometime not, but when I press the Send button nothing happens.

[goatpig]

Post your armorylog.txt

I can't help you if you don't show me this one file, regardless of the issue.

[iradu]

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!

[goatpig]

There's a zombie DB process. Kill it and restart.

[iradu]

I have restarted PC many times.

[iradu]

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: <CppBlockUtils.DbErrorMsg; proxy of <Swig Object of type 'DbErrorMsg *' at 0x0000000009284A50> >

[goatpig]

You're gonna have to delete your Armory DB folder and rebuild it from scratch.