FetchFeedService error with nzbgeek

Help & Support
1

Howdy,

I just noticed that I’ve been getting a ton of errors related to nzbgeek. I don’t recall ever seeing this before migrating over to Ubuntu, nor is it happening with any other indexer. Is this something I should inform nzbgeek about?

Thanks!

An error occurred while processing feed. https://censored.info/api?t=tvsearch&cat=5030,5040&extended=1&apikey=<removed>: unexpected end of file in an attribute value Line 2715, position 142. System.Xml.XmlException: unexpected end of file in an attribute value Line 2715, position 142. at Mono.Xml2.XmlTextReader.ReadAttributeValueTokens (Int32 dummyQuoteChar) [0x00000] in <filename unknown>:0 at Mono.Xml2.XmlTextReader.ReadAttributes (Boolean isXmlDecl) [0x00000] in <filename unknown>:0 at Mono.Xml2.XmlTextReader.ReadStartTag () [0x00000] in <filename unknown>:0 at Mono.Xml2.XmlTextReader.ReadContent () [0x00000] in <filename unknown>:0 at Mono.Xml2.XmlTextReader.Read () [0x00000] in <filename unknown>:0 at System.Xml.XmlTextReader.Read () [0x00000] in <filename unknown>:0 at Mono.Xml.XmlFilterReader.Read () [0x00000] in <filename unknown>:0 at Mono.Xml.XmlFilterReader.Read () [0x00000] in <filename unknown>:0 at System.Xml.XmlReader.ReadEndElement () [0x00000] in <filename unknown>:0 at System.Xml.Linq.XElement.LoadCore (System.Xml.XmlReader r, LoadOptions options) [0x00000] in <filename unknown>:0 at System.Xml.Linq.XNode.ReadFrom (System.Xml.XmlReader r, LoadOptions options) [0x00000] in <filename unknown>:0 at System.Xml.Linq.XContainer.ReadContentFrom (System.Xml.XmlReader reader, LoadOptions options) [0x00000] in <filename unknown>:0 at System.Xml.Linq.XElement.LoadCore (System.Xml.XmlReader r, LoadOptions options) [0x00000] in <filename unknown>:0 at System.Xml.Linq.XNode.ReadFrom (System.Xml.XmlReader r, LoadOptions options) [0x00000] in <filename unknown>:0 at System.Xml.Linq.XContainer.ReadContentFrom (System.Xml.XmlReader reader, LoadOptions options) [0x00000] in <filename unknown>:0 at System.Xml.Linq.XElement.LoadCore (System.Xml.XmlReader r, LoadOptions options) [0x00000] in <filename unknown>:0 at System.Xml.Linq.XNode.ReadFrom (System.Xml.XmlReader r, LoadOptions options) [0x00000] in <filename unknown>:0 at System.Xml.Linq.XContainer.ReadContentFrom (System.Xml.XmlReader reader, LoadOptions options) [0x00000] in <filename unknown>:0 at System.Xml.Linq.XElement.LoadCore (System.Xml.XmlReader r, LoadOptions options) [0x00000] in <filename unknown>:0 at System.Xml.Linq.XNode.ReadFrom (System.Xml.XmlReader r, LoadOptions options) [0x00000] in <filename unknown>:0 at System.Xml.Linq.XContainer.ReadContentFrom (System.Xml.XmlReader reader, LoadOptions options) [0x00000] in <filename unknown>:0 at System.Xml.Linq.XDocument.ReadContent (System.Xml.XmlReader reader, LoadOptions options) [0x00000] in <filename unknown>:0 at System.Xml.Linq.XDocument.LoadCore (System.Xml.XmlReader reader, LoadOptions options) [0x00000] in <filename unknown>:0 at System.Xml.Linq.XDocument.Load (System.IO.TextReader textReader, LoadOptions options) [0x00000] in <filename unknown>:0 at System.Xml.Linq.XDocument.Parse (System.String text, LoadOptions options) [0x00000] in <filename unknown>:0 at System.Xml.Linq.XDocument.Parse (System.String text) [0x00000] in <filename unknown>:0 at NzbDrone.Core.Indexers.Newznab.NewznabPreProcessor.Process (System.String source, System.String url) [0x00000] in <filename unknown>:0 at NzbDrone.Core.Indexers.Newznab.NewznabParser.PreProcess (System.String source, System.String url) [0x00000] in <filename unknown>:0 at NzbDrone.Core.Indexers.RssParserBase.Process (System.String xml, System.String url) [0x00000] in <filename unknown>:0 at NzbDrone.Core.Indexers.Newznab.NewznabParser.Process (System.String xml, System.String url) [0x00000] in <filename unknown>:0 at NzbDrone.Core.Indexers.FetchFeedService.Fetch (IIndexer indexer, IEnumerable1 urls) [0x00000] in :0 `

2

Probably a bad item in the RSS feed, likely just a timing thing. You can open the URL in your browser and find the offending item and report it to your indexer, or wait for it to pass, but it will also break searching.

3

You using a mono version less than 3.2 by chance? I’m experiencing the same problem, and I think it’s a bug in mono. I wrote a little test program, and I can reproduce the problem on my debian box that has mono 3.0.6. I cannot reproduce the problem on my mac with mono 3.2.4.

4

I take it back. I just built up a new media server machine with Ubuntu server. It has mono version 3.2.8. I am seeing the same issue. Here is the mono on my Mac that seems to be working fine:

Mono JIT compiler version 3.2.4 ((no/294f999 Fri Oct 25 20:18:12 EDT 2013)
Copyright © 2002-2012 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS: normal
SIGSEGV: altstack
Notification: kqueue
Architecture: x86
Disabled: none
Misc: softdebug
LLVM: yes(3.3svn-mono)
GC: sgen

Here is the mono on the new Ubuntu machine that is not working:

Mono JIT compiler version 3.2.8 (Debian 3.2.8+dfsg-4ubuntu1)
Copyright © 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS: __thread
SIGSEGV: altstack
Notifications: epoll
Architecture: amd64
Disabled: none
Misc: softdebug
LLVM: supported, not enabled.
GC: sgen

I still suspect this is a mono bug. Perhaps the way it’s built on linux?

5

I have now reproduced this on my Mac as well.

6

@ToBeFrank grab the URL drone used to hit nzbgeek (shown in debug logs) and pop it into your browser, if Chrome and/or FF fail to load it properly and cite an error with the XML then its the feed thats the issue.

7

It’s a bug in mono, but fortunately it can be worked around. I’ve got it fixed in my fork and will be submitting a pull request soon (letting it run for a while to verify it is indeed fixed).