Up until yesterday, Sonarr had been running fine. No updates or changes have been made in a number of days. Beginning yesterday, while looking at the web interface and while monitoring my processes, I noticed that the RSS Sync task was running every 30 seconds (configured to run every 10 minutes) with the notification toasts stacking up (10 “RSS Sync service started” toasts were stacked).
I looked through the forums and tried the following:
Restarted Sonarr service
Restarted server
Deleted RSS sync task from sqlite DB
All looked fine when I went to bed and the RSS task wasn’t running continually. In the morning, Sonarr was not running with a message related to config file corruption. The config file was 0 bytes so I removed it and restarted Sonarr. I continued to have RSS sync tasks running every 30 seconds.
Next, I uninstalled/reinstalled Sonarr and restored to a backup taken a few days ago. Upon startup, Sonarr began running through the library refresh task and I could see it go through 4 shows, alphabetically, and get “stuck” on one then do the same stacking of tasks I was seeing with the RSS sync from earlier.
Is something preventing Sonarr from writing to it’s database?
Sonarr can only run 3 tasks concurrently, this looks more like a display problem than the jobs running concurrently, they may be getting stuck because Sonarr never sees a completed update for them, The trace logs don’t show multiple of the same tasks running at the same time.
Thanks for the reply! I don’t believe there is anything preventing Sonarr from writing to it’s database and I’ve confirmed the file permissions are correct. I believe you’re correct about the “stacking” of tasks being a display issue as I’ve done a bit more digging and found a few more details that I hope can help:
Sonarr service starts and DiskScanService begins. It makes it through a few shows before hitting “The Affair” and many lines of a stacktrace are written followed by some info about the Sonarr service entering a failed state, stopping then restarting the daemon.
Here’s a link to the syslog that contains the information. It shows this start/restart cycle 4 or 5 times before I killed Sonarr and saved the file.
If you enable ((debug logging)) Sonarr should log the filename that it was checking media info for when it failed, but updating libmediainfo would probably be useful.