Not sure a log was made... had to terminate the program (stop through WebGUI) to make it functional again. (as stated, it was in a loop)
Logs were subsequently made and the one that I saved from that period of time can be forwarded; as soon as I find a way to attach it.
I believe it was the report which told me the DB was corrupted after a couple of Dashboard alerts that Library scan had failed.
ONLY able to get Emby working again through a complete restoration of last backup. That was 10 days ago, however as of today,
I started another thread on the failure of Emby to update when "Identify information supplied...
and then, Libraries failed to scan and STILL will not.
What gives? Seems like Emby goes downhill as soon as a problem is encountered.
An inspection of the logs only shows a failure of ffdetect and ffmpeg due to /usr/lib/emby-server not existing
(in case that has anything to do with these issues)
It has never existed that I know of - emby installation (as with apps) is automated in unRAID through use of dockers.
So, where is an "attach" button for the reply so I can send you what I have?
Looks like its under More Reply Options, here.
BTW - No failure to scan Libraries or any kind of DB corruption was ever encountered
(in months amounting to years) until this "loop" bug.