SABnzbd Forums

i suspect the part we just did (where i edited the binary) was an incidental problem. even perhaps unrelated to the crash problem.

the service still crashes. and the log gives no reason why. i have noticed the pid file remains in

is it possible that something is sendiing the computer some sort of sleep signal and sabnzb is taking it as a signal? though i would suspect this to delete the pid file

edit - just crashed now with no site of pid. and 10gb seemingly wasted as on restart what was being downloaded is not downloading anymore. to rule out hardware being the cause, what should i check?

edit 2 - what really gets me f**king irritated is that data from 3 previous attempts of the same file are still on the hard drive. yet every crash means i have to startfrom scratch. that's just bullshit.

here is a log before sometime before the crash. and after that - http://pastebin.com/Pum7WZgg

I would do this:

- run memtest86 from the GRUB boot menu (assuming debian has that too. Otherwise download memtest86)
- run sabnzbd from the CLI (not as a service), so that you can see crash reports (there is nothing in your log)

it now seems to be behaving since friday afternoon (gmt +2). hasn't crashed.

i've also noticed far less crc errors and general nzb download failures. which makes me wonder whether sabnzb was reacting badly to failings on the part of my service providers?

i am speculatin here. but for a long while i haven't had clean downloads nor the service staying up for longer than 24h. i can't help but feel there is some link between the two.

please also excuse my frustrations from the other night.