Why does opendct keep crashing? logs attached

[btrcp2000]

OpenDCT Docker keeps vanishing on me. Can someone take a look at these logs, which are from the appdata folder and copy/pasted from the log link on the docker page? These are taken from before I restarted it manually. Its apparently been down all day, but i never find out until we noticed a recording was missed or channels won't tune

[btrcp2000]

bump

[EnterNoEscape]

I don't have much experience with the OpenDCT docker container, but it looks like at the very least OpenDCT isn't starting up to the point where it's writing logs. Only the service wrapper is writing a log and it's reporting that the JVM isn't responding one minute after it's started. Unfortunately that's not much of a starting point.

I assume you have restarted your server at this point to be sure you don't have any interesting memory issues?

[btrcp2000]

It's working fine though right up until it's not. Watching GoldCup final on it right now. I have not restarted the server for a few weeks since unraid upgraded itself. I'll try that tonight.

[btrcp2000]

Rebooted the server from scratch a week and a half ago, still seeing these random OpenDCT silent crashes. WHat logs can I provide to help diagnose? Opendct before and after crash, container log from Docker page, etc? Something else?

[EnterNoEscape]

Originally Posted by btrcp2000

Rebooted the server from scratch a week and a half ago, still seeing these random OpenDCT silent crashes. WHat logs can I provide to help diagnose? Opendct before and after crash, container log from Docker page, etc? Something else?

You posted the one that would be the most helpful to me as a developer which is the service wrapper that shows OpenDCT unable to re-launch. Outside of that, I can't tell why it crashed (or even if that's what really happened). I supposed the dmesg logs from the server might well explain what's happening since it could be the server running out of memory and OpenDCT just happens to be the process getting killed.