After 18-48hrs Sonarr cannot connect to downloaders

I have Sonarr installed on a FreeNAS server jail shared with couch potato: 192.168.0.133
nzbget and transmission are installed on a seperate jail: 192.168.0.139

Every day I have to switch these jails off and on again as each day I get home from work to find that Sonarr can no longer communicate with nzbget or transmission. When I test the connections to the downloaders within the Sonarr UI it says “Test was aborted due to an error: Unable to connect to NzbGet. Error: ConnectFailure (Connection refused).” Here are the log outputs from client: http://pastebin.com/rYhEkBAB

EDIT: additional log from a separate attempt, this time from ssh session: http://pastebin.com/XatNJG76

Couchpotato continues to be able to communicate with both NZBGet and Transmission when Sonarr is not. This tested within cp by intiating downloads, not just clicking the test button.

Rebooting the jails (sometimes multiple times required) typically resolves the problem but sometimes I have to reboot the entire FreeNAS in order to restore the connectivity and it works beautifully again for a day, sometimes two. This is obviously not right. I’ve actually reinstalled Sonarr onto this most recent jail after it happened before so it must be something in the way I have configured something?

Any help is much appreciated.

FreeNAS-9.3-STABLE-201512121950
Sonarr 2.0.0.3645
Transmission 2.84 (14307)
NZBGet 14.1

Which version of mono are you running?

Based on the error it looks like the connection is being terminated at the remote side, its not timing out, but being rejected, often caused by a firewall.

1 Like

Mono JIT compiler version 4.2.1 (Stable 4.2.1.124/39edf24 Sun Dec 20 05:03:56 UTC 2015)

Are you able to run an RSS sync when its failing to connect to the download clients?

The fact that CP can connect makes me think this is a problem in mono since its failing inside of mono, but if it can connect to external resources it might be a combination of the jail + mono.

Since restarting doesn’t work it also points me to mono or the jail acting up. Mono isn’t officially supported on FreeBSD, so if there is an issue there, solving it won’t be trivial.

Are you able to test with Sonarr in its own jail?

1 Like

Yes, all other external calls appear to work ok. The indexers all work fine still, it’s just the downloaders that aren’t working. I’ll create a new jail with Sonarr on its own and let you know in a couple of days if it happens again.

1 Like

So, I created a clean Jail, updated packages, install mono, mediainfo and sqlite3 was already latest. Installed sonarr, and still it cannot speak with nzbget or transmission. Perhaps it is that jail that I need to reinstall rather than this one… I’ll try that and see how I get on.

Interestingly an older version install of both Sonarr and Mono works fine even whilst the newer ones still are not working. I run the tests at the same time and the newer install is failing on both the sonarr installs.

Sonarr Version 2.0.0.2850 + Mono Version 3.10.0 (tarball Mon Jan 26 02:53:37 UTC 2015)

This combination is working fine, not sure if I can narrow down to where the issue is but I will try! It may also only last 18-48 hours so I will update over weekend.

It might be mono, I know in 4.2.1 there is still a bug they introduced in 4.0 (its been fixed for other platforms, but not FreeBSD).

Be curious how this works, but also worth testing just upgrading Sonarr, mono 3.10 is still usable.

1 Like

Yes, upgraded to latest version of Sonarr and it’s still working fine. I’m not very good at this stuff so I don’t know how to update mono gradually so see if it breaks on a certain version. I’m going to leave it at 3.10 for now and let it run for a few days. As the original issue stated the error only occured after at least 18 hours previously so fingers crossed.

1 Like

It has run on mono 3.1 and sonarr 2.0.0.3645 without a blip since my last post. I will see if I can duplicate the jail and upgrade mono and see if that breaks it. I’ll let you know (once I work out how to do that!).

Thanks for your help!

1 Like

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