Page 1 of 1
Failed to Import
Posted: November 6th, 2008, 5:08 pm
by tazmanrc
I'm running version 0.4.4 and every time I try and download a file, using either a nzb file or the report id I get the message "Failed to import ** files from msgid_*****"
I have checked firewall/router settings and have even stopped the firewall in case this was stopping traffic.
Can anyone give me an idea as to why this is happening as I'm baffled.
Re: Failed to Import
Posted: November 6th, 2008, 5:22 pm
by switch
Do you have an example newzbin id? (just the id).
Is there any mention in the logging/connections page about "Skipping duplicate article" or "INCORRECT NZB: Duplicate part"
Re: Failed to Import
Posted: November 6th, 2008, 5:38 pm
by tazmanrc
Message id: 3249384
Full error
2008-11-06 22:36:47,671 WARNING [nzbstuff] Failed to import 41 files from msgid_3249384 Boston Legal - 5x07 - Mad Cows.nzb
Re: Failed to Import
Posted: November 6th, 2008, 5:49 pm
by switch
Ok, this is a newzbin error so you should probably complain to them. I remember them having some sort of database problem about 2 days ago which is when this file was posted.
Basically they are serving up empty nzb's. The nzb's contain the name of the files and such, but not the actual segments, which are needed to download files.
Re: Failed to Import
Posted: November 6th, 2008, 5:50 pm
by tazmanrc
Ahh haa that's great. Thanks for your help.
Re: Failed to Import
Posted: September 25th, 2009, 12:55 pm
by willpower101
switch wrote:
Ok, this is a newzbin error so you should probably complain to them. I remember them having some sort of database problem about 2 days ago which is when this file was posted.
Basically they are serving up empty nzb's. The nzb's contain the name of the files and such, but not the actual segments, which are needed to download files.
This is not a problem with newzbin, these nzb's download fine on newsleecher and i'm completely lost as to what the problem is. Any suggestions?
Re: Failed to Import
Posted: September 25th, 2009, 3:46 pm
by shypike
Just email one to
[email protected].
We'll have a look at it.