Sonarr Scheduler Not Running

[tsnearly]

Sonarr version: 2.0.0.4949
Mono version: 5.0.1.1
OS: Mac OS X Version 10.11.6

Debug logs:
sonarr.txt
sonarr.trace.txt
sonarr.debug.txt

sonarr.txt Original (and cumulative) Before Purge/Restore
sonarr.trace.txt Before AppData Purge/Restore

Description of issue: Sonarr no longer connects to RSS feeds, scans drives for media, searches indexes, nor updates series information. Just now in an attempt to see if it was related to a corrupt database, I deleted the entire AppData directory (/Users/tiger/.config/Nzbdrone). I downloaded and ran the most current version. I attempted to add a download agent, but it would never connect, nor would it return an error message that the test was unsuccessful. I restored the data to a automatic backup set from several months ago when it was working. After restarting Sonarr, it still behaved similarly—that tasks were being queued but never executed in the background.

Here you can see that the tasks are being triggered, but they never seem to actually run in the background.

Even when you launch the Sonarr web interface, the notifications that normally display and then disappear now stay floating on top of whatever screen you are viewing.

If I go test any of my indexers, including those setup with default values like RARBG, no response is ever displayed on the screen. New indexers being created are never saved since the initial validation test never returns with a success/failure.

[markus101]

Could you post some trace and debug logs from the start up of Sonarr for a few minutes? The current logs capture the state after the tasks have already been queued and already appear to be stalled.

Have you been running mono 5.0.1.1 the whole time or was that recently updated?

[tsnearly]

@markus101:I don’t remember when I upgraded mono. However, when I looked at Time Machine entries for Library:Mono.framework, I see that the internal current pointer was modified 7/19/2017. But my sonarr installation has been dead since the middle of June. I just hadn’t had the time to focus on figuring out what broke it. It had worked so well for the longest time. And then wham.

This is the trace log from just now. I started sonarr, browsed the web interface (testing showRSS indexer and flipped to the tasks tab), then shut it down.
https://pastebin.com/cBMUQEZd

And here is the debug log, as well.
https://pastebin.com/1AkvpJyB

[markus101]

Thanks for the logs I see Sonarr making a number of requests, but never receiving a repsonse:

17-8-16 16:52:22.4|Trace|HttpClient|Req: [GET] http://thexem.de/map/allNames?seasonNumbers=True&origin=tvdb
17-8-16 16:52:22.6|Trace|HttpClient|Req: [GET] http://services.sonarr.tv/v1/update/master?version=2.0.0.4949&os=osx&runtimeVer=5.0.1.1
17-8-16 16:52:22.8|Trace|HttpClient|Req: [GET] http://skyhook.sonarr.tv/v1/tvdb/shows/en/268592

They’re not timing out, getting an error response or ever succeeding that I can see.
Are you able to open those URLs in your browser from the same machine running Sonarr?

[tsnearly]

I just validated all three of those specific URL’s you cited. They are worked without any hesitation. Below are the returned datasets.

Xross Entity Map
{“result”:“success”,“data”:[],“message”:""}

Sonarr Update Service
{“available”:false}

Sonarr Skyhook
Returned a huge amount of episode summary information for “The 100.”

[markus101]

I also noticed 17-8-16 16:52:22.0|Trace|HttpClient|Req: [POST] http://localhost:8084/login: username=admin&password=(removed) a local request that doesn’t appear to ever get a response.

I’m not sure what to make of this, it’s dying without any information that I can see.

@Taloth any thoughts on this one?

[Taloth]

I’d expect it to timeout eventually, but the logs aren’t long enough.

I’m kinda inclined to look at mono with suspicion, mostly because 5.x hasn’t be exactly kind lately.
Also wonder ask if OP has any kind of antivirus running.

[tsnearly]

So I was able to fix the issue. I was inspired with a point that @markus101 made the other day that the queue tasks appeared to be invoked, yet no response was ever being received. I happened to go into iTunes and realized it was never connecting to the Apple Store. Don’t ask me how, but I somehow forced iTunes to throw an error resulting in code 11222.

https://discussions.apple.com/thread/1831516?tstart=0

Apparently there’s a cludge (that obviously affects more than just iTunes) where if auto-proxy-discovery is turned on, and yet there is no proxy found it hoses communication. As soon as I modified that setting for my ethernet connection in networking and bounced iTunes, it immediately connected to the Apple Store (oddly, no requests ever showed up in Little Snitch for iTunes until that was fixed). I then started sonarr. It, too, immediately went straight to work refreshing series information and playing catchup for the past two months.

So, thankfully, it’s resolved.

[markus101]

Wow… I never would have thought of that. Awesome that it’s working again and hopefully we remember if we see this again.