A couple of days ago Armory stopped working for me. Whenever the transaction history was about to be fully synchronized, ArmoryDB would exit.
The issue started happening when I was still letting Armory run bitcoind. I had Bitcoin Core 0.14.2 with Armory 0.96.2 installed.
Since then, to troubleshoot, I have changed the setup so that I'm running bitcoin-qt myself. I also upgraded to 0.15.0.1 and then down again to 0.15, after reading that the former causes other issues. None of that seemed to have any impact on the issue.
I have also started ArmoryDB standalone in a console to see if it prints anything when it exists. It doesn't.
The dbLog shows no identifyable errors and ends with `-INFO - 14:24:02.391: (..\BlockchainScanner.cpp:852) scanned from block #484062 to #484718`
The armoryLog shows no identifyable errors and ends with `2017-09-21 14:24:02 (INFO) -- ArmoryQt.py:4670 - Dashboard switched to "Scanning" mode`
armorycpplog shows 2 errors, presumably around the time ArmoryDB exits:
-ERROR - 14:24:12.063: (..\SocketObject.cpp:447) POLLERR error in readAndWrite
-ERROR - 14:24:12.078: (..\StringSockets.cpp:359) POLLERR error in readAndWrite