Sonarr is freezing every 24 hours or so

Sonarr is freezing for me about once a day, normally early in the morning. I have to kill the process and re-run for it to fix. I’ve scanned the forums and I see similar complaints, but no fixes.

See here for the log from when I notice the crash. Note, it crashed at 04:31, I came home and saw it had crashed at 22:40. I only have the one saved log at present, if it happens again (which it is likely to do, tonight) I will add that log too.

I’m running on Windows 7, Sonarr is version 2.0.0.3154. It had previously been completely stable, it seems like the instability only started about 3-4 weeks ago. I forget exactly when, unfortunately. Been busy at work.

Thanks in advance.

1 Like

Trace logs would be a great start, this sounds like another issue I’ve been investigating, but haven’t yet found a cause, but we’re looking for more logs to see what might be causing it.

I think the log I posted is a Trace log? Or am I missing something?

No it is, just totally missed the link. Is the end of the log the crash?

I’ve been having trouble with this as well. Thankfully I already had trace logging turned on it seems.

Log appears to end at 2:05AM local time and absolutely nothing happens until I try to see whats going on at 23:56 the next night. Webpage doesn’t respond and the NZBDrone windows service wont restart.

Takes a whole server restart to get it back up again.

Seems to happen around once a day:

nzbdrone.4.txt
nzbdrone.3.txt

Yup, that’s the last log file (nzbdrone.log). I can post the .0, .1 etc from the next crash if you’d like. I checked this morning and it’s still running, but I suspect it will die within the next 24 hours. I’ll post the logs as soon as it does. It’s pretty infuriating!

I just pushed a change to develop that should assist in reducing if not eliminating this issue. It will be available in 2.0.0.2306 or higher if one or both of you could switch to it and test it out once its available that would be awesome.

Do you have any steps that might help me exacerbate the problem, so you can properly regress the bug? Otherwise I’ll leave my current build running til it crashes a couple more times, to collect the logs and get an idea of how long it takes.

There aren’t steps that can be used to reproduce it as 3 things had to happen at the same time or almost the same time.

  1. Any task was running and completed (successfully or not)
  2. The command cleanup task executed and cleared out a just finished task
  3. A DB lock occurred updating the last run of the first task that completed

If those things all happened within a fraction of a second things either stopped running or hung completely.

We’ve been able to reproduce it by intentionally breaking it, but there isn’t a way to manually trigger it.

I’m having the same issue here. Sonarr is locking up and I have to restart the process. Due to this, the program won’t grab anything until it’s been restarted. On a side note, I noticed that if I add a show and there are back episodes, I have to force Sonarr to go out and get them (even if the back episodes are monitored). Either having it do an auto season search or manual search fixes the issue.

Have you looked at the FAQ? https://github.com/Sonarr/Sonarr/wiki/FAQ#how-does-sonarr-find-episodes

One more question…If I am running the Windows version of Sonarr, how do I update the program manually such as when you release a fix for the software program? I went to the Github repository however it looks like nothing is compiled for Windows.

Thanks!

On Windows, sonarr will update automagically!

I think he means how do we install a version from the develop branch on Windows. I admit, I am also at a loss!

You do it like so: https://github.com/Sonarr/Sonarr/wiki/Release-Branches

We have just released this fix to master though, so you don’t need to do anything except wait for the update.

Ahh fantastically easy. Is the master update imminent?

Its already available.

Awesome…it looks like my PC has the update already. Thanks for the fast update, Markus!

Haven’t had any instability in the 3 weeks since the update; looks like it’s fixed. Thanks!