When armory is closed there is no such process as ArmoryDB or alike opened. I understand what you think might be the problem here, but this would mean that Armory works smoothly after restarting the PC but that isn't the case.
Then I'm not sure why (according to your armorylog.txt debug log) that sometimes Armory is not spawning ArmoryDB... The only reason I can think why that happens is because it detects that ArmoryDB is already running.
I assume you clicked the "more details" button in Task Manager and that you've checked all the background tasks:
Still, as you say, a restart should fix that problem... so it's not likely that a zombie process is the issue here.
For my limited understanding, there must be a problem with Bitcoin Core and this is the reason why I can't get Armory online. While watching the processes carefully I recognized that BTC Core is not opened every time Armory is running. Keep in mind that BTC Core is not installed in the default path and I'm not sure if I have given Armory the correct guide to finding it.My "Bitcoin Install Dir" f.e. is "E:\Bitcoin\daemon" and the "Bitcoin Home dir" "E:\Bitcoin".
I think your "pathing" is fine... you can see in the debug output that it finds your bitcoind.exe ok:
2021-01-13 19:39:56 (INFO) -- ArmoryQt.py:1891 - Setting satoshi datadir = E:\Bitcoin
2021-01-13 19:39:56 (INFO) -- SDM.pyc:171 - Found bitcoind in the following places:
2021-01-13 19:39:56 (INFO) -- SDM.pyc:173 - E:\Bitcoin\daemon\bitcoind.exe
And ArmoryDB is finding your blocks OK:
-INFO -0 10:32:05.000: (e:\users\goat\code\armory3\cppforswig\blockutils.cpp:915) blkfile dir: E:\Bitcoin\blocks
This output is a little worrisome tho:
-INFO -0 13:37:27.188: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:134) scanning new blocks from #577594 to #577593
It seems you're missing ~90000 blocks??!?
The Bitcoin blockchain is currently at block #666366... so either your node is not fully synced, or it's actually using the "btc" folder instead of "bitcoin" and Armory
is looking in the wrong place, or there is some corrupt data stopping Armory from scanning the blocks properly.
Regarding the size of the blockchain there are 2 folder installed by default: - "Bitcoin" which includes folders like "blocks","chainstate","daemon", "database", "doc" and various files including bitcoin-qt.The other folder is called "btc" including "blocks","chainstate","Wallets" only but apparently the blockchain is safed into both folders.
It's possible that your Bitcoin Core
GUI setup has been configured to store the blocks in "btc\blocks"?
whereas, when Armory is spawning "bitcoind.exe" it is explicitly using the "Bitcoin\blocks" folder... If you run the Bitcoin Core GUI (aka BitcoinQt) and look in the "Window -> Information" screen... what are the values for "datadir" and "blocksdir"?
Either that, or it's an old datadir from a previous install?
What is the highest number blkXXXXX.dat file in the "
btc\blocks" directory?
What is the highest number blkXXXXX.dat file in the "
Bitcoin\blocks" directory?
This is what I've been able to extract from the Dblog :
https://pastebin.com/tbb8vbLF .I've got no idea why it is 1,2 GB but only shows data of the last run.
You mean the dbLog file is 1.2 gigs??!?
Something not right there... I'd try shutting Armory down and deleting both armorylog.txt and dbLog.txt... and then restart Armory. It'll help get rid of any old debug that isn't relevant anymore.