Hi @fschmeis ,
Apologies for the delay in getting back to you here, I just got a chance to review your case once more.
Looking over the logs, it is not clear why RoonServer stops working, and there is no real pattern to this behavior, logs appear to just abruptly end, let me give you some examples:
System log of crashes:
16.11.21-00:06:09 --- Running
16.11.21-00:26:02 --- Not responding
16.11.21-00:26:02 --- Error
16.11.21-00:26:04 --- Initializing
16.11.21-00:26:04 --- Started
16.11.21-00:26:07 --- Running
16.11.21-00:30:03 --- Error
16.11.21-00:30:05 --- Initializing
16.11.21-00:30:05 --- Started
16.11.21-00:30:08 --- Running
16.11.21-11:05:07 --- Error
16.11.21-11:05:09 --- Initializing
16.11.21-11:05:09 --- Started
16.11.21-00:26:02 — Error - Roon was updating metadata
16.11.21-00:30:03 — Error - Roon was trying to load storage locations
16.11.21-11:05:07 — Error - Roon was trying to perform a search
With no clear pattern as to what causes the crash, in similar cases like this, the issue has been caused by a database or a hardware issue with the Core.
Looking over the log, it appears that Roon is attempting to load 410448 tracks. Even if you do only have 35k tracks activated, the Roon database has 410k tracks in the database that it has information stored about. You can try to perform a clean up library function via Roon Settings → Library and that will remove any database entries for disabled storage locations (you’ll need to restore from a backup to get those changes back).
A Roon database restore should not take 1.5 hours to complete. This can be a further sign that the current hardware is not up to par for a database of this size.