Kanoans

Thanks for the response, but damn, that makes it alot less useful to me if it's only checking if it needs to run ever 4 hours. that's less frequently than the built-in mover my system runs into issues if the cache drive is ever full, so I really need to run the mover frequently or atleast have it checking if it needs to run. Still works for now though

It seems like one of the recent updates removes the 'minutes' section for the scheduler? Now the most frequently I can set it for it is every 4 hours. But the actual schedule seems to still be running on my old schedule of every 2 minutes.

So I tried to update and to do disable c-states, neither worked. Going to be trying the 'safe mode' test next. If that does determine that the problem is a hardware issue though, how do I narrow it down? I added a few different components around the time this starterted (PSU, CPU, motherboard, and more ram). Outside of swapping out every component, which isn't really feasible, is there any way to narrow down what could be causing this?

Hello, I have been having this issue for about two months now (shortly after new years). The server will run fine for a certain amount of time [anywhere from 6 hours to 3 days, usually around a day or two], and then the Web UI can no longer be accessed. It just gives the errors "Err_Connection_Refused" or "DNS_PROBE_FINISHED_NXDOMAIN". Docker containers will continue running, but shortly afterwards they will start having issues. The big one being that they can't communicate with each other; ie, radarr will give an error saying all download clients are unavailable, even though the download client is still operation. If let to keep running, eventually the docker containers will start to just crash. I also seem to lose access to shares at the same time that the web ui becomes unreachable. Attempting to SSH into the server has worked, but very inconsistently. And once the docker containers start to develop issues, I can't SSH into it at all. The only way to fix this problem is to preform a hard reset of the server. This has caused some database corruptions in the docker containers, since they can't be safely shutdown. I turned on syslog, and can never seem to find anything that would point to the actual issue. I've run memtest for more than a day (memory tested clean several times). I have limited cpu/memory for all docker containers (That seemed to atleast stabilize it alittle bit, the disconnections went from every 6-12 to every day or two, but unsure if that was actually helped or just a coincidence) Recently, I set up radarr/sonarr to ping me when it has health issues. That's the only reliable way I've found to get a decent record of when a failure occurs. if both containers say that they can't access the download client, that means that shortly before, the web ui would have become unresponsive. the times over the last week: 2/22 - 10:56 pm 2/24 - 9:47 pm 2/27 - 1:49 pm 2/28 - 1:17 am This diagnostic is from when I rebooted my server this morning 9:20am. Please let me know if there is anything more I should have included, or any details that would be helpful that I left out. tower-diagnostics-20250228-0928.zip