Sonarr crashing and tasks stuck

[bcsteeve]

So… interesting stuff here.

3 days ago my sonarr STOPPED crashing. I never even noticed until now, because I hadn’t checked my “logs”. By “logs”, I mean that I set up a cron to start nzb every minute and if it wasn’t already running, write a timestamp to a log. As you can see from this partial, it stopped crashing 3 days ago.:

2015-05-29-02:51:01 nzbdrone start/running, process 30334
2015-05-29-07:33:01 nzbdrone start/running, process 5633
2015-05-29-14:18:01 nzbdrone start/running, process 17074
2015-05-29-20:16:01 nzbdrone start/running, process 27400
2015-05-30-02:15:01 nzbdrone start/running, process 5634
2015-05-30-04:20:01 nzbdrone start/running, process 8915
2015-05-30-04:37:01 nzbdrone start/running, process 9396
2015-05-30-07:29:01 nzbdrone start/running, process 13889
2015-05-30-09:03:01 nzbdrone start/running, process 17055
2015-05-30-09:04:01 nzbdrone start/running, process 17124
2015-05-30-11:32:01 nzbdrone start/running, process 21366
2015-05-30-11:35:01 nzbdrone start/running, process 21508
2015-05-30-23:22:01 nzbdrone start/running, process 10178
2015-05-30-23:54:01 nzbdrone start/running, process 11024
2015-05-31-06:54:01 nzbdrone start/running, process 22415
2015-05-31-07:42:01 nzbdrone start/running, process 24048
2015-05-31-07:43:01 nzbdrone start/running, process 24088
2015-05-31-08:15:01 nzbdrone start/running, process 25043
2015-05-31-11:53:01 nzbdrone start/running, process 31328
2015-05-31-13:43:01 nzbdrone start/running, process 1922
2015-05-31-14:15:01 nzbdrone start/running, process 3075
2015-05-31-14:16:01 nzbdrone start/running, process 3117
2015-05-31-16:14:01 nzbdrone start/running, process 6658

But what is REALLY interesting, is when I go to System -> Tasks, I see EVERY SINGLE TASK has “3 days ago” under “Last Execution”, even the ones set to run every minute.

Coincidence? Hardly.

I can manually run any task, but they won’t run on their schedule. Eg. 12 minutes ago I ran Check for Finished Download. Looking now, it says “1 minute” for Interval and “now” for Next Execution, but “12 minutes” for Last Execution.

So good news it isn’t crashing, but bad news it isn’t really doing anything now!

There were no updates to Sonarr (still shows May 21). I have updated my server several times over the past few days so one of them might have done something but I didn’t specifically do any fixes listed above.

[bcsteeve]

Hmm… so it seems the cronjob that starts sonarr every minute was causing the problem. I shut the cron job off and a minute later, all the tasks ran.

So that mystery solved, but it leaves the much larger one of why the crashes suddenly stopped 3 days ago. I’ve confirmed that my kernel has not changed.

[bcsteeve]

Haha… and 2 minutes later, it crashes. Sigh

[markus101]

This is the same issue as:

Scheduled Tasks not running

Some good news. Tnx to a memory dump a user provided us we've been put on the right trail. markus already committed a fix for the problem on develop, but we weren't sure yet if that was the cause. This was a typical Murphy scenario. Tnx to a tiny bug, if 3 specific things happened at the same time, Sonarr would end up with a stale cached command state, preventing that command from ever running again until the app got restarted. Once we figured out how those 3 things played a role, it became …

[cooler0918]

This seems to have fixed it for me