Sonarr V3 crashing on Mac

v3 Testing
#1

Sonarr version (exact version): 3.0.3.698
Mono version (if Sonarr is not running on Windows): 5.2.0.224
OS: Mac OS Yosemite
Debug logs: https://pastebin.com/eHq2TijA
Description of issue:

I upgraded Sonarr to V3 recently, and it seems to crash every day or every few days. I’ve attached the latest log after relaunching the app. It seems to run ok for a little while before crashing, and seems to launch ok when I go and launch the app again. I see there is some kind of Epic fail in the log caused by Mono but I’m not sure how to handle.
Thanks!

#2

To start upgrade mono, 5.20 is the recommended version. 5.2 is almost 2 years older than 5.20 and missing tons of fixes.

#3

Weird I must have thought I was downloading the right version when I grabbed it from the repo the other day. I’ll just grab the latest stable and try it since it says it works with 10.9 and above…

#4

I updated to the very latest mono and all seems to be running OK at the moment. Thanks!

#7

OK spoke too soon. I updated to the latest Sonarr (3.0.3.713) and now it’s crashing again (previous version seemed to be ok?)…
https://pastebin.com/xSJ2G66H

(Mono version is still at 6.8.0.105)

And now I see another Sonarr update. Updating to 3.0.3.717 now and will report back if it crashes…

When you install a new version, does that cause Sonarr to hit the indexer API a bunch of times? It looks like Sonarr is hitting my indexer so many times that my indexer is cutting me off (I have a limit of 1000 api hits a day).

Sonarr showed this task after updating:
RSS Sync Completed. Reports found: 1000, Reports grabbed: 2

#8

If you were on 3.0.3.712 then Sonarr was barely functional since no tasks were running.

No.

Getting 1000 reports from a single indexer would be 10 API calls (100 per page) + 2 for the grabs.

If you had one of the series that TVDB recently completely changed the episode numbering for then likely that’s what used them all.

(There are other series affected as well).

#9

My indexer has now banned my account for abuse. This seems to have started when I upgraded to V3 (I would get an error in Sonarr that my indexer couldn’t be reached, and then I would go check my indexer and see that for some reason my API calls were abnormal and going over my limit). Can you tell from my log if Sonarr has done a bunch of API calls to my indexer?

Log: https://pastebin.com/X7hvjeBn

#10

The logs only show 92 RSS Syncs and 1 search, so unless you have another instance running it’s not from Sonarr.

#11

OK then I’m thoroughly confused…still investigating…

#12

Have you talked to them? They’re pretty active on IRC and maybe their forums and can tell you why it was blocked.

#13

I sent them a message through the normal channel so waiting to hear back…

#14

Back to the issue at hand…here’s the log after I had to launch Sonarr again after a crash (just checked to tonight to see if it was running and it wasn’t):
https://pastebin.com/FNfSvq9k

#15

The log after won’t tell us why it failed.

Trace logs leading up to the crash, better if they’re standard output and error redirected to a file since the file logging won’t show errors from mono that lead to a crash.

#16

OK I have enabled trace logs in the settings and will wait to see if it crashes again…

#17

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.