Bitcoin Core -reindex did the trick (I think)
It is just finished.
Then started Armory (0.96.3) and it looks OK.
Balance correct, Armory also read my transaction I pushed on blockchain.info.
Right bottom corner: Connected (.... blocks)
Used configuration file armoryqt.conf instead of command line options
But I don't think that made the difference.
Thanks for the reply.
Topic: Armory keeps crashings since this morning (Read 267 times)
Run 0.96.4 RC1 (see the stickies) and try again. If that doesn't work, post logs on Pastebin and post the logs here.
In the bottom right corner it is 'Node offline (.... blocks)'
Sorry.
Sorry.
Hi,
Same problem here.
I want to broadcast a transaction from a watchonly wallet (signed on an offline computer).
Spent today fixing Armory
(Upgraded to) Armory 0.96.3 / Bitcoin Core 15.1
Tried update/reinstall Armory.
Deleted Armory datadir
Now started Bitcoin Core with -reindex option.
Maybe off topic: On the right bottom corner in Armory I see 'Offline' but on the Dashboard it is 'Online'.
This was no problem with previous transactions.
No luck so far.
Any suggestions?
Thanks for your help.
Same problem here.
I want to broadcast a transaction from a watchonly wallet (signed on an offline computer).
Spent today fixing Armory
(Upgraded to) Armory 0.96.3 / Bitcoin Core 15.1
Tried update/reinstall Armory.
Deleted Armory datadir
Now started Bitcoin Core with -reindex option.
Maybe off topic: On the right bottom corner in Armory I see 'Offline' but on the Dashboard it is 'Online'.
This was no problem with previous transactions.
No luck so far.
Any suggestions?
Thanks for your help.
Try with the testing builds.
Post all your logs using pastebin
Not resolved...
I exited, and restarted Armory, same problem as before, even with Admin option, several times, no way to get it to work...
Help please
Thank you
I exited, and restarted Armory, same problem as before, even with Admin option, several times, no way to get it to work...
Help please
Thank you
Hi
Armory 0.96 was totally fine this night, but since this morning, it keeps crashing at launch, after it has verified between 90% to 99% of the wallets consistency.
In the black DOS windows, last lines after crash :
-INFO - 1501070170: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO - 1501070170: (..\BDM_Server.cpp:1025) unregistered bdv: 77bd6da8201b664ab3c4
-ERROR - 1501070179: (..\SocketObject.cpp:285) POLLERR error in readFromSocketThread
-ERROR - 1501070179: (..\BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: POLLERR error in readFromSocketThread
-INFO - 1501070179: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node
And the error log :
https://ufile.io/jcx3n
Thank you for your help...
I don't understand, I did nothing special that could damage the install.
I tried to update the Blockchain with BTC Core before starting Armory, but nothing changes...
EDIT : very strange : just to try, I right click on the Armory icon on my desktop and choose Execute as Admin... it worked directly !
Don't understand.
Armory 0.96 was totally fine this night, but since this morning, it keeps crashing at launch, after it has verified between 90% to 99% of the wallets consistency.
In the black DOS windows, last lines after crash :
-INFO - 1501070170: (..\BitcoinP2P.cpp:947) Connected to Bitcoin node
-INFO - 1501070170: (..\BDM_Server.cpp:1025) unregistered bdv: 77bd6da8201b664ab3c4
-ERROR - 1501070179: (..\SocketObject.cpp:285) POLLERR error in readFromSocketThread
-ERROR - 1501070179: (..\BitcoinP2P.cpp:1027) caught SocketError exception in processDataStackThread: POLLERR error in readFromSocketThread
-INFO - 1501070179: (..\BitcoinP2P.cpp:969) Disconnected from Bitcoin node
And the error log :
https://ufile.io/jcx3n
Thank you for your help...
I don't understand, I did nothing special that could damage the install.
I tried to update the Blockchain with BTC Core before starting Armory, but nothing changes...
EDIT : very strange : just to try, I right click on the Armory icon on my desktop and choose Execute as Admin... it worked directly !
Don't understand.
Jump to: