Topic: Armory Issue - Won't Broadcast (Read 1693 times)

Do me a favor.  Try broadcasting again, and then as soon as it fails, look at the end of the Bitcoin debug.log.  In Windows it would be C:\Users\\AppData\Roaming\Bitcoin\debug.log, in Linux it would be /home//.bitcoin/debug.log.  When Bitcoin core disconnects you, it always logs why -- usually you will see something like 'Inputs already spent" or "Invalid signature padding", etc.

No I did not realize that   I figured since Armory is free I'd try to get an answer outside of support.  You guys are great, thanks and I'll send a support ticket.

How much fees are you paying and how big is the transaction? You realize this would entirely easier if you created a support ticket and attached your log file.

https://bitcoinarmory.com:8443

I've just created a whole new offline transaction, signed and broadcast and I get the same thing.

Did you create the two transactions at the same time?  It's possible that the first transaction turned out to be a double spend of the second-- this happens because Armory doesn't keep track of what outputs have potentially already been spent when creating a new transaction, unless that transactions is broadcast already.  This would match your symptoms, too:  Bitcoin Core sees you broadcast a tx spending inputs that have already been spent, flags you as misbehaving and disconnects you.  You can be sure about it by looking the Bitcoin Core logs... it usually tells you why it disconnected.  Or simply create a new offline transaction, sign and broadcast.  As long as the previous one has been broadcast by the time you create the next, everything will be fine.
[/quote]

Thanks for your reply, no it was a completely different transaction, being sent from a different wallet, to 4 different wallets (I've set up a few different wallets to spread out coins and to play around).  The first transaction was the same but from different wallets. I set this one up an hour or so after the first successful test transaction.  

Everything looks good until I go to broadcast.  Signatures good, connection good, but once I hit the "broadcast" button, immediately the green "Connected 309XXX Blocks" goes red and says "Disconnected".  That's when I get the notification tray popups saying "Connection to BitcoinQT Lost, Armory can't send the transaction until you reconnect" and then it says "Connection to Bitcoin QT re-established".  Finally I get the pop up window telling me the transaction is invalid.  I should mention I'm using version 0.91.2.  Thanks for your help.

Did you create the two transactions at the same time?  It's possible that the first transaction turned out to be a double spend of the second-- this happens because Armory doesn't keep track of what outputs have potentially already been spent when creating a new transaction, unless that transactions is broadcast already.  This would match your symptoms, too:  Bitcoin Core sees you broadcast a tx spending inputs that have already been spent, flags you as misbehaving and disconnects you.  You can be sure about it by looking the Bitcoin Core logs... it usually tells you why it disconnected.  Or simply create a new offline transaction, sign and broadcast.  As long as the previous one has been broadcast by the time you create the next, everything will be fine.

Fairly new to Armory and I'm just testing things out sending a small amount between wallets just to learn.  I broadcast one transaction with success, but the second one keeps failing.

So I create the transaction in online armory and sign it on offline computer.  Load the signed transaction on the online and it says "All Signatures Valid!"  Armory shows "Connected 309XXX Blocks", but when go to broadcast I get a taskbar error message pop up saying something like "Connection to BitcoinQT Lost, Armory can't send the transaction until you reconnect" and then it says "Connection to Bitcoin QT re-established" and it does this a couple of times.  Finally I get a pop up window in Armory saying "Invalid Transaction - Transaction not accepted by the bitcoin network, due to a bug with Armory..."

I've restarted Armory a couple of times and tried broadcasting a number of times to no avail.  Again this is the second transaction I am trying, the first went off without a hitch, so I'm not sure what the issue could be.   Any thoughts would be much appreciated!