We need more active people on chat! Click me!    Login or Register

Forum

Newsbin says "Bad XML"

Reply
By Message
host2626
on Feb 16, 2018
(18 Wks)
Hello,

I am using Newsbin Pro for my NZBing needs, 6.80B13. I haven't updated it in weeks. Suddenly, today, all of the .nzb files that I am getting from UC are rejected by Newsbin. Those from NZBPlanet are fine. NB does not keep more than a couple of days worth of processed NZBs, so I am not sure when I got the last not-rejected file from UC.

Turning on debugging mode in Newsbin showed the following: "DEBUG Bad XML Line:2Column: 0". Line 2 has this, in every rejected file:

<!doctype nzb public "-//newzbin//dtd nzb 1.1//en" "http://www.newzbin.com/dtd/nzb/nzb-1.1.dtd">

The file that are not rejected, from NZBPlanet, or UC in previous days have:

<!DOCTYPE nzb PUBLIC "-//newzBin//DTD NZB 1.1//EN" "http://www.newzbin.com/DTD/nzb/nzb-1.1.dtd">

Notice the difference in case. Since URLs are involved, I suppose that case is important.

I am not sure who is right and who is wrong, maybe Newsbin should not care. In any case, it seems that there has been a change in the format that the xml is generated by UC in and it is breaking at least one NZB program.
KK99KK
on Feb 16, 2018
(18 Wks)
Yup, looks like some new issue. I'm getting an NZB Parse error/ corrupted NZB file. Wishing all site issues will be fixed soon, but I'm trying to not get my hopes up...

Maybe it helps if more users create bug reports on the UC Gitlab page.

https://gitlab.usenet-crawler.com/OptimusPrime/usenet-crawler/issues
host2626
on Feb 18, 2018
(18 Wks)
For some reason I cannot see the posts I make in this thread or in the one that got made later about the same issue, let's try again.

It's been some days now without a fix. And Newsbin is broken in that it sees a file like that, does nothing, and simply moves it from the "watch" directory into its work directory, without an error message, as if it has been processed correctly. Since it may not be fixed soon (but then, what's the use of an indexer site if it produces unusable nzbs?), here is a temporary fix. You only need to change ONE line in the generated NZB file. Either take it from a working NZB from a working site, or copy this one, to replace line #2 with the <!doctype tag:

<!DOCTYPE nzb PUBLIC "-//newzBin//DTD NZB 1.0//EN" "http://www.nzbindex.com/nzb-1.0.dtd">

My NB
coderwolf
on Feb 18, 2018
(18 Wks)
not newsbin, but I am getting invalid NZB from sabnzbd for nzbs pulled from here.
Top

Add Reply

Upgrade to BFF required