SABnzbd Forums

On my centos5 server i've been noticing some problems with my SABnzbd (v 0.5.1 RC2 (Python Source)) when downloading NZBs from Newzbin.

When checking out the logs all i got was:

2010-04-12 18:12:17,913::INFO::[__init__:754] Restarting crashed newzbin
2010-04-12 18:12:50,910::INFO::[__init__:754] Restarting crashed newzbin

Is this a known issue or is it related to newzbin in some way?

Hard to tell, but it is related to newzbin.
One way to find out is running it from a terminal session so that all
console output is visible.
Then tee all output to a file and later check for "Traceback" in the file.
./SABnzbd.py | tee >file 2>&1

At the moment running it directly and for some reason it works and fetches the NZBs.

Will try it in my normal situation again and see what happens.

It's kinda strange to have it for over 24 hours first (noticed it late ) and now it works...

Oh well it seems to work again.

It could've been a newzbin issue indeed.

djclean wrote: It could've been a newzbin issue indeed.

Still not a good reason to crash.
At least the newzbin process can crash and be restarted without
harm to the rest of SABnzbd.

same problem here
2010-04-12 18:45:06,434::DEBUG::[bpsmeter:60] bps: 481725.671284
2010-04-12 18:45:12,434::DEBUG::[bpsmeter:60] bps: 161328.952628
2010-04-12 18:45:18,434::DEBUG::[bpsmeter:60] bps: 54028.7398151
2010-04-12 18:45:23,436::DEBUG::[bpsmeter:60] bps: 21709.3199556
2010-04-12 18:45:23,900::INFO::[__init__:756] Restarting crashed newzbin
2010-04-12 18:45:29,436::DEBUG::[bpsmeter:60] bps: 7270.40732824
2010-04-12 18:45:35,436::DEBUG::[bpsmeter:60] bps: 2434.84470387
2010-04-12 18:45:41,437::DEBUG::[bpsmeter:60] bps: 815.288693257
2010-04-12 18:45:47,437::DEBUG::[bpsmeter:60] bps: 273.038533782
2010-04-12 18:45:53,437::DEBUG::[bpsmeter:60] bps: 91.4400525194
2010-04-12 18:45:56,901::INFO::[__init__:756] Restarting crashed newzbin

the queue is stuck on fetching msgid

You'll need to tell more about the circumstances.
The newzbin part hasn't been changed for a long time and has always been very robust.
Now newzbin's is going to a rough time. It could be that they changed something
to which SABnzbd gives a bad reaction.
You can PM details to me.

seems to be working now droped one file which was causing the issue, from the queue. and restarted sab.

Please PM me the suspect. Specific report number?

pm sent

The report is no longer present on newzbin.
Cannot find any reason for it to crash, since that situation is covered.
I will improve the error message a bit for the next release.

Are you sure it's not a frozen report (like alot these days)

I can have a look if i know what report.