SABnzbd Forums

Replying to myself...

Okay here is the result of my test. I activated all the feeds and stoped SAB, the I restarted it with the console, and it actually worked... Then the download took place and as you said I lost track of what's going on. After the download completed, the Scheduler had to be restarted because of a crash. It actually happened 2 times after that and I suspect that it's because the rss parser receive an error from the server or a timeout and that makes it crash.

nzbs.org is a very very good site and it's success is its bigger problem, sometimes the server reply that the service in unavailable. The fact that we can't filter out the category the they send in the feed doesn't help that either, I have to make 5 request to the server for the "My NZBs" to be able to categorize them properly. That would be a GREAT ad-don to be able to filter not only the title of the rss feed, but also it's properties something like that

RSS Filter example: Music-Video

It would be nice if you tested without downloading.
Timeouts are not so likely.
If the scheduler would be choked, so would the task guardian.

I have been inspecting the code until my eyes got blurry.
At some places I added some extra paranoid code, which will be in 0.5.2Final.
I have no clue as to why the RSS task would crash.

There is nothing relevant in the console log either... It's in fact the same exact thing as the log file I posted earlier...

The Scheduler crash for no apparent reason.

I'm sorry to tell you, that I can't give you anything more to further debug and ask me if I know how hard it is to debug with that little informations, I'm a programmer myself.

MageMinds

It looks like the traceback is not triggered.
This would mean that python thinks it performed a normal shutdown, instead of crashing.
Maybe you could insert something that shows the reason for the shutdown in the source of the scheduler?
Or trigger the traceback upon shutdown?