Womble's disabled, still used (and throwing errors)?

I noticed over a long period (6+ months) that I’m never pulling anything in via Womble’s anway, so I disabled it.
Now I’m seeing this error in drone’s log files, emphasis mine:

14-9-18 05:10:01.6|Info|RssSyncService|Starting RSS Sync
14-9-18 05:10:03.1|Error|FetchFeedService|An error occurred while processing feed. http://nzbs.org/api?t=tvsearch&cat=5000&extended=1&apikey=

System.NullReferenceException: Object reference not set to an instance of an object
at NzbDrone.Common.Http.HttpClient.Execute (NzbDrone.Common.Http.HttpRequest request) [0x00000] in :0
at NzbDrone.Common.Http.HttpClient.Get (NzbDrone.Common.Http.HttpRequest request) [0x00000] in :0
at NzbDrone.Core.Indexers.FetchFeedService.Fetch (IIndexer indexer, IEnumerable`1 urls) [0x00000] in :0

14-9-18 05:10:05.0|Error|FetchFeedService|An error occurred while processing feed. http://newshost.co.za/rss/?sec=TV&fr=false

System.NullReferenceException: Object reference not set to an instance of an object
at NzbDrone.Common.Http.HttpClient.Execute (NzbDrone.Common.Http.HttpRequest request) [0x00000] in :0
at NzbDrone.Common.Http.HttpClient.Get (NzbDrone.Common.Http.HttpRequest request) [0x00000] in :0
at NzbDrone.Core.Indexers.FetchFeedService.Fetch (IIndexer indexer, IEnumerable`1 urls) [0x00000] in :0

14-9-18 05:10:05.3|Info|DownloadDecisionMaker|No reports found
14-9-18 05:10:05.7|Info|RssSyncService|RSS Sync Completed. Reports found: 0, Reports grabbed: 0

It’s interesting that nzbs.org also failed. Before/after this log, at the regular interval, RSS sync is working fine with no exceptions.

Yes, I’m sure that Womble’s is disabled :wink: but when RSS is working fine, it’s not reporting in the log (at least not at info level it seems) which url’s it’s loading, so I have no clue if it’s also trying to fetch the RSS from Wombles…

Unfortunately there isn’t enough information here to see what is going on, namely we need line numbers (mono running with the --debug switch), debug logs would be helpful as that would log the URLs.

Which version of mono and drone is also important.

Is the issue persisting?

I figured it wasn’t enough for you guys… but that’s all I have with regards to error messages. I’ll see if I can run drone for a prolonged time with mono --debug.
It’s very infrequent, so this might take a while. I’ll get you the drone/mono version also.