Usenet-crawler indexer not working

Thanks for this awesome piece of software – it makes my life so much simpler!

I’ve been using Sonarr for a couple of years now and used it in several different setups ranging from my desktop to now having settled on running it from within a jail on my FreeNAS server. I grab my episodes via usenet and have used Oznzb and usenet-crawler indexes with no issues up until recently.

Usenet-crawler was showing as not working in the logs, so I removed it. I can however go to their site and according to them everything is fine.

I wanted to check here to see if anyone else is reporting problems?

I am using the develop branch – Sonarr Ver. 2.0.0.3512 -develop. It updates itself regularly.

If I were to test the stable branch, how would I go about moving to the stable branch without compromising my setup?

You can’t go from develop to master without wiping out your DB because the DB for develop is ahead of master, you will be able to when the next release of master is out (whenever that is).

Not working with what errors? Not knowing how it was broken I’d say try it again because it appears to be online.

I concur – it appears usenet-crawler is online as I can download nzbs through a browser without issue. Here is what Sonarr is saying concerning the test failure:

unable to connect to indexer: Error: NameResolutionFailure: Error: NameResolutionFailure


System.Net.WebException: Error: NameResolutionFailure
  at System.Net.HttpWebRequest.EndGetResponse (IAsyncResult asyncResult) [0x00065] in /usr/wrkdirprefix/usr/ports/lang/mono/work/mono-3.10.0/mcs/class/System/System.Net/HttpWebRequest.cs:971 
  at System.Net.HttpWebRequest.GetResponse () [0x0000e] in /usr/wrkdirprefix/usr/ports/lang/mono/work/mono-3.10.0/mcs/class/System/System.Net/HttpWebRequest.cs:985 
  at NzbDrone.Common.Http.HttpClient.ExecuteWebRequest (NzbDrone.Common.Http.HttpRequest request, System.Net.HttpWebRequest webRequest) [0x00051] in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Common\Http\HttpClient.cs:230 

I want to note that from the command line within that jail I can lookup www.usenet-crawler.com with no problem.

Well, I fiddled around with it for a while and here is where I am.

I have successfully tested and added usenet-crawler again.

I noticed in the log that there was an error message concerning the port. I went into the FreeNAS gui and disabled the Sonarr plugin. After that, Sonarr is functional again. I guess when I let Sonarr update itself and install the develop branch it somehow made another instance o Sonarr within the jail, maybe?

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