Sonarr version (exact version): 4.0.0.748
Mono version (if Sonarr is not running on Windows): .NET: Yes (6.0.13)
OS: Linux (Docker Image from linuxserver.io)
Debug logs: Trace: https://hastebin.com/share/jexivuheqi.javascript
Debug: Hastebin
Description of issue:
Sonarr is running in a docker container. I noticed today that the container was at 100% CPU usage. Opening a terminal in the docker container and using top, I can see that curl is using 98%+ CPU. Killing CURL just causes it to start under a new PID (not unexpectedly, but figured it was worth a try). The container is running on a Synology NAS and it’s container manager shows: “curl -sL http://localhost:8989/ping”
This container has been running fine for a long time on the NAS, so I’m not sure what may have changed lately to cause this. I reviewed the debug log (and even a few minutes of trace log), but logs aren’t really showing anything, even when I kill the process.