large queue bailout

[evster666]

just experienced a memory bailout with a queue over 3000 entries.

wasnt a problem before doing latest ubuntu apt-get dist-upgrade.

anyone else experiencing the same problem that is:

/etc/init.d/sabnzbdplus restart fails, message: fail...
error log looks like this:

Code: Select all

fork() failed
fork() failed
fork() failed
fork() failed
fork() failed
fork() failed
fork() failed
fork() failed
fork() failed
fork() failed
fork() failed
fork() failed
fork() failed
fork() failed
fork() failed
fork() failed

starting sabnzbdplus via "sabnzbd" from a user bash works. but when it tries to check pars and/or tries to extract, we get some funny "out of memory" errors.

logging off of everything, login via a single ssh session, unmounting and stopping every daemon except ssh and then running /etc/init.d/sabnzbdplus restart seems to get the daemon started again.

[shypike]

3000 entries, unbelievable...
How much memory does your system have?

[evster666]

4gigs (64bit kernel)

worked well for the past 3 years, then after last apt-get dist-upgrade, boom

[shypike]

From which version to which version did you go?

[evster666]

linux kernel 3.5.0-25-generic to 3.5.0-26-generic

sab didnt upgrade, just the kernel and some other non sab packages.

[shypike]

OK, the honest answer: I have no idea.
We do test against current Ubuntu releases,
but not after each kernel upgrade.

I'm moving this to the Ubuntu/debian forum.

[jcfp]

Everything mentioned in the topic start is a symptom of a system that's low on memory, but based on just the info here one can't even tell if sab is causing that. Output from the likes of ps, top, htop, free (etc.) will give the topic starter some insight into that. The only certain thing is that on a memory strapped linux system, sab will be a prime target for the oom killer even before there's a lengthy queue in play.

[war59312]

I've seen this "error" today on my 8GB (4.4GB free) of RAM system. First time too.

Linux RobsUbuntuServer 3.5.0-26-generic #42-Ubuntu SMP Fri Mar 8 23:18:20 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

And queue was empty at the time.

Having double duplicating at the moment. It only errored out 1 time (edit: the 1 time was on boot up).