SABnzbd Forums

Hello,

is there any chance that sabnzbd(0.3.1) could create a segmentation fault, or is it more likely a hardware problem, e.g. bad RAM:

last kernel messages in the syslog, like:
SABnzbd.py[3639]: segfault at 00002aaac182c618 rip 00000000004329c7 rsp 0000000042002a00 error 4
SABnzbd.py[3597]: segfault at 0000000000000030 rip 00000000004329e3 rsp 00000000418017a0 error 4
SABnzbd.py[6987]: segfault at 00002aaaaac58c00 rip 0000000000432df4 rsp 0000000041801830 error 6

> the different line numbers are looking to me like RAM failure or so. Cannot be, that the program is changing itself, so?

tia

SABnzbd itself cannot crash with such an error. Python code normally does not really crash, but shows readable error messages.
However, it is possible that for some reason the Python interpreter itself (or one of its libraries) crashes in this way.
Is there anything to be seen in the SABnzbd.log file (located in ~/.sabnzbd/logs) ?

to clarify things, I couldn't check the SABnzbd.log b/c the server was down the next day and the following week.

BUT I switched the RAM modules afterwards and now we're running without a hiccup since then.

Great help shypike, exactly what I needed to hear back then, to get my ass up to replace some faulty hardware!

--> Thank you