Page 1 of 1
NZB-files not being picked up
Posted: July 8th, 2008, 12:05 pm
by coolrunnings
Hi,
since I recently upgraded to SABnzbd 0.4.0 I won't be able to download anymore.
When I put nzb-files in the scan-directory SABnzbd won't pick them up.
Also, when I try to manually upload them through the frontend, it doesn't work either.
Code: Select all
Version: 0.4.0 Final
OS: Windows Server 2003 R2 Enterprise Edition SP2
Install-type: Windows Installer
Skin: Plush
Firewall Software: None
Are you using IPV6? no
Is the issue reproducible? no
I've tried to re-install, but that doesn't solve the problem.
Re: NZB-files not being picked up
Posted: July 8th, 2008, 5:34 pm
by switch
Is the "watched folder/blackhole" directory set in Config>Folders? Depending on which version you have upgraded from, it may not be set anymore.
If it is, please do the following
1) Close SABnzbd
2) Place an .nzb file in your blackhole
3) Open SABnzbd
4) Send
your logs to bugs at sabnzbd.org
Re: NZB-files not being picked up
Posted: July 8th, 2008, 11:36 pm
by coolrunnings
Log has been sent.
Re: NZB-files not being picked up
Posted: July 9th, 2008, 1:30 pm
by shypike
I suspect that the NZB file itself is corrupt.
We have seen that SABnzbd doesn't always handle bad NZB files gracefully.
Please email the NZB file also.
Re: NZB-files not being picked up
Posted: July 9th, 2008, 4:56 pm
by shypike
I received the NZB file.
It is indeed not quite correct, it contains many empty files.
So the chance of successful download would not be good.
However, SABnzbd should at least show which files are not empty.
It fails to do this, so we are filing this as an official bug.
And start working on it of course.
Meanwhile, if you are using nzbindex.nl, you may want to avoid this site.
It looks like a recent problem in their NZB files.
The bug in SABnzbd is quite old and only recently people have started
complaining about it.
NZB files should not contain files definitions with no arcticles in them.
Re: NZB-files not being picked up
Posted: July 9th, 2008, 5:05 pm
by switch
We have found the specific issue and have issued a fix that will be in the next version (0.4.1).