Support Forum

Weird, between 0.3.1RC1 and 0.3.1Final there were some changes that should prevent this particular problem.
I'll check it.

Which SABnzbd version do you use? Older ones are sensitive to where they start from. Try this: cd full-path-to-sabnzbd python SABnzbd.py "whatever options" If that doesn't work, I'm afraid that you need to add additional "print" statements in the Python code to find this problem....

The _yenc and celemtree messages mean that you did not install these Python modules. Also, it looks like you don't have Perl installed (required for email). The rest, I'm not sure. You could try the attached test script. It should produce some thing like this: !usr!bin!par2 !usr!bin!unrar !usr!bin!n...

What I see in the log is that SABnzbd does not try to download additional PAR2 files after the first verify failed. It does this when it estimates that there would not be enough par2 files left in the queue to repair. Mind you: the files are not lost, they have not been downloaded yet (by design). I...

Bob,

I don't have much time this weekend, but I am taking your complaint seriously.
At least this time, I may have some useful material on this elusive problem.
BTW: SABnzbd uses par2cmdline to do verification and repairs.

I doubt if the Final release (out now) will make a difference.

Not yet, I have my hands full with lots of other stuff too.
This slipped through. I'll stuff it in my nightly test queue.

Thanks for the info. I simply never gave it a thought before.
Until we introduced a "windowed" version of SABnzbd, I never had a problem with run-as-service.
I still don't with SABnzbd-console.exe.

I'll pick up your suggestion about signal handling anyway, thanks.

I'll check if there's a simple way to do this.
The names are generated by the internal Python logger.
sabnzbd.1.log etc would be best.

The ".log" extension is associated with Notepad by default.

The only thing your source has to do is use this line: I've tried a few XML utilities and they all balk at this incorrect line. I see no reason to support sloppy developers and standards-breakers. Besides, ignoring the tag means skipping the standard Python XML library and create our own parser. You...

First quick reaction, sounds like somebody doesn't know how to write an XML file. Go to the source, there's no excuse for delivering a NZB file that's non-conforming. Newzbin spec is clean and simple XML, there's no reason for people not to follow it. I may be wrong (and it's a Python/SABnzbd proble...

Someone else in the forum has an alternative way to start as service:

http://forums.sabnzbd.org/index.php?topic=284.0

If you cannot keep it running with anysrv, maybe this will work.

The only time I get a Signal 5 is when I run SABnzbd.exe as a service.
Not when I use SABnzbd-console.exe

Maybe I was not clear, you're supposed to use the other exe file, there are two starting with 0.3.1rc1.

And yes, I do use the method described in the Wiki.

Received your logs, but it's not enough. I need also sabnzbd.log (which is the most recent one) and please also the NZB.
Otherwise it's very difficult to diagnose.
Do you use the article_cache ? If so, what size is it?

Also, which Linux do you use?

The PAR2 file are supposed to vanish from the queue. As soon as basic PAR2 info is collected (the smallest of the VOLxx+yyy.par2 files is in), the other PAR2 files are removed from the queue. They re-enter the queue when the PAR2-verification fails and will get downloaded after all. After that PAR2 ...

Not sure if it makes the difference, but I start SABnzbd thorugh a batch file.
So the registry points to a CMD file, and that file starts the program.

My content of the CMD file:

start d:\bin\SABnzbd\SABnzbd-console --daemon -f d:\usernet\sabnzbd.ini

This way it works fine on my Server2003 box.