Quote

That's an old stack. You should consider upgrading.

Yes. I know. I just came back without doing much with Bitcoin for at least one year and find my environment somehow broken although there was no blockchain fork as far as I know. First I'd like to find out what is wrong before considering any changes. Today I found out about the Armory company issue and that you took over the client maintenance. Thanks a lot for that! Let me know where to donate; I'll send something as soon as sending works again for me. Wink

I won't tell here what amount I have in my wallet (maybe just a few Satoshis, maybe millions), but you have to always assume that people fear of losing money (and there could be millions in the wallet). Therefore any change can potentially break things or make it unsafe. I didn't know that Armory was taken over and how trustworthy the new "organization" is and all that. Anyway, I'll probably upgrade soon. Forget this side topic.

Quote

I'm not sure what the issue is, but I know that it wouldn't happen in 0.95. At any rate, try manually setting a higher fee to spend, looks like the automated fee bump is failing.

You can't ever be sure that it wouldn't happen in 0.95 before finding the reason. I don't think it's fee-related, because adjusting the fees is working. The amount just doesn't get sent out. Anyway, I tried today again and also with setting a higher fee. it's a relatively small transaction (only one input address, two output addresses) with an amount 0.024579 and fee 0.0007 (more than enough from what I read) and it still failed without error message.

Quote

That's really for me to say. Post your logs.

You're right here of course. And I was also wrong saying that there is nothing; I looked at the wrong log (the cpp log). In the normal log you can see Armory crashing.
And when I was looking at the cpp log, there was not date/time info, so it was difficult to find out what was new, but I searched for "error" and couldn't find anything interesting.
Here's the log:
http://pastebin.com/raw/rH2mbmyZ
It contains both log and cpplog, but only the entries after Armory has started up.
I clicked a link somewhere else (Bitcoin payment link), therefore you see the entries "already open" and that stuff.
I censored the wallet name, my Windows user name in the directory names and the exact bitcoin: link that I clicked, as the same error also happens when I copy/paste the destination address manually into the send dialog.
So what sticks out is the crash:

Code:

2016-12-28 21:42 (INFO) -- TxFrames.pyc:720 - Change address behavior: NewAddr
2016-12-28 21:42 (ERROR) -- Traceback (most recent call last):
  File "ui\TxFrames.pyc", line 785, in createTxAndBroadcast
  File "ui\TxFrames.pyc", line 766, in validateInputsGetUSTX
  File "armoryengine\Transaction.pyc", line 2148, in createFromTxOutSelection
  File "armoryengine\Transaction.pyc", line 2058, in createFromPyTx
  File "CppBlockUtils.pyc", line 2014, in getTxByHash
RuntimeError

Any ideas what is causing this? Is there a way I can debug this code? I'm not familiar with Python, but I know C++ very well.
Where did it crash exactly? In CppBlockUtils.pyc/2014ff? Where can I find this old file? I can't find it in the etotheipi guthub repo.

http

Posts

Merits