Error: NewznabRssParser

Using sonarr on Windows 10U
Ver: 2.0.0.4429

Been getting a lot of these errors lately:

NewznabRssParser An error occurred while processing feed item from http://192.168.1.20:5075/api?t=tvsearch&cat=5000&extended=1&apikey=(removed)&offset=0&limit=100&tvdbid=293302&season=2: The string was not recognized as a valid DateTime. There is an unknown word starting at index 0. 12:13am
XmlExtentions Unable to parse None: The string was not recognized as a valid DateTime. There is an unknown word starting at index 0.

Using NZBHydra

Thanks,

One of the items in the feed has a bad date, you’d need to check the XML the feed is outputting to track it down.

I looked around and I couldn’t figure out how to do that. Help me out?

Take the URL from the log above, put it in your browser, at the API key back and check the feed.

Okay, so I got

TVDB ID: 293302, Season: 2, Title: Scream Queens

so, how do I fix the date?

It’s either a problem with the output from NZBHydra or the feed from the indexer (and NZBHydra is just passing it along). Bypassing NZBHydra would tell you where the issue lies (going straight to the indexer), also knowing what is being returned could help us if it’s something we can resolve.

Hey @markus101 - I’m starting to get these errors with all my tv shows:

An error occurred while processing feed item from http://192.168.1.20:5075/api?t=tvsearch&cat=5000&extended=1&apikey=(removed)&offset=0&limit=100&q=NBC%20Nightly%20News&season=2016&ep=12/15: The string was not recognized as a valid DateTime. There is an unknown word starting at index 0

System.FormatException: The string was not recognized as a valid DateTime. There is an unknown word starting at index 0.
at System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles styles)
at System.DateTime.Parse(String s, IFormatProvider provider, DateTimeStyles styles)
at NzbDrone.Core.Indexers.XElementExtensions.ParseDate(String dateString) in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Indexers\XElementExtensions.cs:line 54
at NzbDrone.Core.Indexers.RssParser.GetPublishDate(XElement item) in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Indexers\RssParser.cs:line 183
at NzbDrone.Core.Indexers.Newznab.NewznabRssParser.GetPublishDate(XElement item) in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Indexers\Newznab\NewznabRssParser.cs:line 99
at NzbDrone.Core.Indexers.RssParser.ProcessItem(XElement item, ReleaseInfo releaseInfo) in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Indexers\RssParser.cs:line 149
at NzbDrone.Core.Indexers.Newznab.NewznabRssParser.ProcessItem(XElement item, ReleaseInfo releaseInfo) in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Indexers\Newznab\NewznabRssParser.cs:line 50
at NzbDrone.Core.Indexers.RssParser.ProcessItem(XElement item) in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Indexers\RssParser.cs:line 138
at NzbDrone.Core.Indexers.RssParser.ParseResponse(IndexerResponse indexerResponse) in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Indexers\RssParser.cs:line 58

This is a problem with the feed that Sonarr is receiving, you’ll need to determine if it’s from the indexer or only NZBHydra and make a change accordingly.

I am also getting these errors using NZBHydra. Disabling Hydra in Sonarr and using the indexers directly appears to fix the issue so it must be something in Hydra.

Yup,

TheOtherP knows and is tracking, no fix yet.

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