Sonarr version (exact version): 160, 155, 154, 153 (linuxserver.io docker) Mono version (if Sonarr is not running on Windows): OS: Ubuntu server 18.04 Debug logs: Description of issue:
Sonarr will run normally for an indeterminate amount of time. Sometimes days, sometime hours. All of a sudden (almost always in the middle of a file transfer to the NAS), Sonarr interface will become completely unresponsive. Other than a 30-50% IOWAIT time, nothing is suspecy. Not sure what the IOWAIT is, the SSD boot drive and the NAS are both not bogged down and able to respond immediately.
When this docker dies it will take out most other Dockers on the system and require a reboot / image wipe. I’m usually left with a .PARTIAL file where it was trying to copy a file to the NAS. This also happens in Radarr.
Server: Dell i7 laptop with Ethernet
Nas: qnap 4 bay wired with Ethernet
Picture of my system at “idle” while lock up is present:
Not using dockers but i’ve heard this before not only for Sonarr or Radarr,
The issue seems to be something with having to less resources for the Docker container when moving/copying the file.
I’ve also read that someone using a Vmware image had a issue like this also.
especially when using multi dockers because every docker needs a certain amount of resources to keep running.
When running Sonarr or Radarr on the main machine the issue doesn’t happen when running in dockers or vmware it happend because of the limited resources it gets.
That certainly sounds possible. Do you have any ideas on how to go about troubleshooting it?
The strange part is that it doesn’t always happen. I can download and move 10 shows fine, but for some reason the next one might trigger this behaviour.
