Error messages, transactions not sending

[fumblefingers]

Hi All,

I'm using Armory 0.94.1, Bitcoin Core v 0.13.0, Win7 64 bit.

Used Armory to send two transaction in two days from the same wallet, no problem. Try to send a third, and I get the error message pop up that says:

"There was an error constructing your transaction.... more than once... two or more transactions."

I had to restore a second wallet from a paper backup, and was then able to send my third transaction.

All three transactions went through, and the recipients acknowledged that, yet those three transactions in the Armory Transaction window all show grayed out, with a zero in a gray box on the far left, instead of the check in the green box, if that  is helpful. What does that mean, anyway?

I tried a fourth transaction from both wallets a few minutes ago, and I get that error message again.

I also show the correct amount of coins in both wallets, so I got my change back.

[achow101]

log files please.

[fumblefingers]

I've done this before, but I don't remember where I post them.


Sorry. Help?

[fumblefingers]

http://pastebin.com/nTBajeh5

The whole file was too big for pastebin. I went back to just before 10-26, as that date was when I started sending the transactions in question.

[goatpig]

Need your Armory logs, not your Core logs.

[fumblefingers]

this is my armorylog.txt, not armoryccplog.txt.

Hope that's the right one.

http://pastebin.com/Ve4B8RH6

Again, I started it from 10-25, all the pertinent  transacations began starting 10-26 and 10-28

[goatpig]

Code:

2016-10-30 22:54 (INFO) -- ArmoryQt.py:3121 - Current block number: 432617
...
2016-10-30 23:07 (INFO) -- Networking.pyc:159 -    StartHeight: 436677

Your db is some 4k blocks lagging behind your node. I suggest you rebuild & rescan.

[fumblefingers]

That  worked thank you.

What is it about the Armory program that causes it to stop adding blocks?

I saw somewhere that you have a v0.95 Armory version out. Is it ready for prime time?

[goatpig]

What is it about the Armory program that causes it to stop adding blocks?

Armory reads block data straight from disk. Since Core 0.10, that data is no written sequentially anymore, and there can be large gap in between consecutive elements headers of the chain, preventing Armory from detecting additions to the longest chain. 0.95 is better at dealing with this particular issue.

I saw somewhere that you have a v0.95 Armory version out. Is it ready for prime time?

You should wait for 0.95.1, which will come with a set of minor fixes. This is scheduled for sometimes this week, still working on one last bug report.

[fumblefingers]

I laud your dedication to this project.

I discovered and bought into Peercoin a while back, thought it had great potential. Then I watched it wither as the main developer seemed to have lost interest.