I have a stuck transaction and tx broadcast timed out errors

[Kuriso]

Using version 0.95.1

Transactions have worked fine so far. Yesterday I sent some bitcoins and did not get a "fee too low" window so I wasn't thinking about the fee.  I never use this storage wallet.  My coins usually come from an exchange. As of this post, a little over 16 hours have passed and the transaction is still not confirmed.  I have tried to send a new transaction but now I keep getting a "tx broadcast timed out" window. I have tried different amounts of fees, as high as the most I've paid for sending a larger transaction but still the same error.

I have tried the "Clear Unconfirmed TX" option under the Help menu but it has done nothing for the transaction.  Is the unconfirmed transaction holding my other coins ransom?

dcc48bf25ef40e35e53592a6e2d07dac648697261b6324c58634b1d8c281de09 - The amount was for .418717

[1715283463]

1715283463

[1715283463]

1715283463

[achow101]

Your transaction is now confirmed. 0.96 will include RBF functionality so that it will be easier to replace transactions with one that pays a higher fee.

[Kuriso]

you can delete this.  I was jut pointed to https://www.viabtc.com/tools/txaccelerator/ which made the transaction work.  Now I do not have the tx broadcast timed out errors

[achow101]

Can you post your armorylog.txt and dbLog.txt files which contain the times when the the "tx broadcast time out" errors occurred? I am investigating the issue and need the log files to confirm my hypothesis.

[Kuriso]

Yes, I'll look at it this evening and post it for you.

[Kuriso]

I sent you a pm with links to the log files.

Another question...  Is there a way to close or minimize the ArmoryDB.exe command line window without stopping the process?  It opens with Armory and will not run in the background.

[achow101]

I sent you a pm with links to the log files.

Another question...  Is there a way to close or minimize the ArmoryDB.exe command line window without stopping the process?  It opens with Armory and will not run in the background.

I don't think so. You can only minimize it to the taskbar. IIRC this has been fixed for 0.96 as well.