Bootstrap: Starting Sonarr - /opt/NzbDrone/NzbDrone.exe - Version 2. I just use the local IP of my server, I don't forward the port for sonarr. I have not messed with appdata because the docker itself seems to be working fine.
I am not getting any response from the webUI in sonarr.Įvery other docker of mine works fine (nzbget, CP, nzbhydra). As soon as I switched it to use the master branch instead of develop branch it completely mellowed out
SONARR SETUP FOR NEWGROUPS SERIES
I could limit the Docker's access to CPU and RAM per your suggestion, but would prefer to find the underlying cause.Īre you using the stable ( master ) or development ( develop ) branch? I know there was an issue with the development branch that caused me to have to revert back to master, it would get stuck in a loop of constantly running the refresh series task, it would never fully complete & I ended up with over 20 refresh series tasks running and it was draining my system resources. That said it's worked fine for months with zero issues, but now in the past few weeks this CPU and RAM thing has started. The key question is sonarr actually working for you? You can also limit its CPU resources ( ) for when something else requires the cpu time. But if you truly are worried about it then limit the amount of RAM that sonarr is capable of using ( )Īs far as the CPU usage, I've never really seen sonarr be a pig like that unless its actually scanning or actively searching or what not. Rather its all the cache, etc that the linux base is using ( ) and it will get released once something else requires the memory. Never really had the time to fully investigate, but I don't actually believe that sonarr is truly using that amount of memory. Log into the webgui for sonarr and check System>Tasks, see if there is anything running?
Not seeing this behaviour at all on my setup.
Attached is a screenshot from CA showing it at 37% CPU utilization and using 19GB RAM. No one else is seeing this? I've tried reinstalling the docker, both importing the backup and creating it all new from scratch. Any ideas how I can troubleshoot?Įdit: I just restarted the docker a few minutes ago and CA confirms that it's using 30% of the CPU Looking at the log doesn't seem to show anything happening at the time. I've noticed in the past few days that my unRAID box CPU utilization is stuck at around 33% and if I stop the Sonarr docker it goes to zero, then restarting the docker it behaves as normal. I've been using this Sonarr docker for months and it's worked well.