Segment fault

[xenoxz]

After about a week of no problems i started getting 'Segment fault' errors and sabNZBd shuts down. I have no idea what causes it, the last action done by sabNZBd seems to be something different every time. There is no errorcode or any indication of what the problem is, it just says "Segment fault" on a separate line, and shuts down sabNZBd. I can't figure out what the heck this means. After starting up sabNZBd again it runs like before, no warnings or errors in the webinterface. And suddenly it stops again with the same 'Segment fault' message.

I tried uninstalling and installing again (all through the package manager in Ubuntu)


Anyone?

[shypike]

Most likely a problem in the Python interpreter.
Which Python release is installed?
Do you use SSL connections to the Usenet servers?
Which Ubuntu release do you use?

Segment faults are just about impossible to cause from within a Python program
(SABnzbd is written in Python), usually such errors are caused by problems
in either the interpreter or the (compiled) modules.
It is possible that some issue in the SABnzbd code may trigger a lurking
problem in the interpreter and/or modules.
Without detailed information and reproducable scenario's it's unlikely that
we will ever find the cause.

[xenoxz]

I don't know what version of Python, but its Ubuntu 9.04, so whatever comes with that.

Yeah I use SSL.

For the last six days it has happend about every 10 minutes. I have had to go back to windows and newsleecher the past week.


Update:
I use Giganews (europe) port 563, 5 x SSL connections.
According to Synaptic i have Python '2.5.4-1ubuntu4' and '2.6.2-0ubuntu1' installed.

Right now its been running for about 30 mins without any trouble. Yesterday it crashed 4-6 times in an hour =/


Any more info needed? Or is this a lost cause?

[sander]

As shypike says, it's hard to analyse problems like that.

I would start this way:
- run SABnzbd from a gnome-terminal so that you can see all output, also after a segmentation fault, and
- start SABnzbd with "python2.5 SABnzbd.py" to avoid possible python2.6 problems, and
- only use non-SSL connections
- try different NZBs
Then see whether the segmentation fault happens again. If so, look at the ouput in the gnome-terminal.

[xenoxz]

Ok I'll try that. This is a copypaste from just now, running the sabnzbdplus command (probably Python2.6 then?) with SSL.

[xenoxz]

Whoa... That resulted in a whole new error:

Fatal Python error: Inconsistent interned string state.
Aborted

copy/paste attached.


--- This was with the command "python2.5 sabnzbdplus" in the /usr/bin/ directory.
I couldn't find the SABnzbd.py file, but i guess this is the same thing?

Also, i forgot to turn off SSL, will try that too.

[sander]

Ok I'll try that. This is a copypaste from just now, running the sabnzbdplus command (probably Python2.6 then?) with SSL.

Ah, if you use "sabnzbdplus" from the 9.04 repositories, you're automatically using python2.5 already.

[sander]

Whoa... That resulted in a whole new error:

Fatal Python error: Inconsistent interned string state.
Aborted

copy/paste attached.


--- This was with the command "python2.5 sabnzbdplus" in the /usr/bin/ directory.
I couldn't find the SABnzbd.py file, but i guess this is the same thing?

Also, i forgot to turn off SSL, will try that too.

First turn off SSL, then test and report again.
As your using the repository version of SAB and not the downloadalbe version, you have sabnzbdplus and not SABnzbd.py. That's OK.

Googleing for "Fatal Python error: Inconsistent interned string state." in the meantime, I found this:

The only way it can happen is if some C code is doing a wild store,
corrupting memory it shouldn't be touching at all. C code may be in
core Python, or in any extension modules you use. Since reports of
this error remain so exceedingly rare, it's probably not in core
Python. Are you using any extensions? You really don't supply much
info here.

Wld stores are a big deal -- they can cause anything to happen.
Python string objects happen to have a field that should contain only
one of 3 possible values. You're getting the message because the
field doesn't have one of those 3 values. That means some C code has
gone insane.

which confirms what shypike said.

[xenoxz]

So I've turned off SSL and it was ok through the night, but this morning I got another Segment Fault. Or well... It was my brother that noticed it, so he just restarted the service. Therefore I don't have a log for you =/

But since then its been running ok. So almost 24 hours with "just" one crash. Better than before at least. I'll try to get the log if it happens again tho.