[Zope] Inexplicably crashing Zope 2.7

Dieter Maurer dieter at handshake.de
Wed May 5 17:01:53 EDT 2004

Doug Winter wrote at 2004-5-5 11:57 +0100:
> ...
>At least once a day, and sometimes much more frequently, they fall over,
>sometimes one, sometimes both.

You Zope died, probably due to a SIGSEGV.

Change your "ulimit -c" setting to allow core files to be written.
You will then get core files for these situations.
GDB may be able to analyse them (unfortunately, either GDB
can not analyse core files for multi-threaded programs
or Linux writes them wrong; at least you should see the
death course and where it happened).

> ...
>After it has fallen over, I see:
>UID        PID  PPID  C STIME TTY          TIME CMD
> ...
>zope     28621     1  0 10:21 ?        00:00:00 /usr/bin/python2.3 /usr/local/zope2/lib/python/zdaemon/zdrun.py -S /usr/local/zope2/lib/python/Zope/Startup/zopeschema.xml -b 30 -d -f -s /usr/local/be/zopeinstance7.icpeurope.
>zope     28636     1  6 10:22 ?        00:05:26 /usr/bin/python2.3 /usr/local/zope2/lib/python/Zope/Startup/run.py -C /usr/local/be/zopeinstance7.icpeurope.net/config/zope.conf
>zope     28637     1  5 10:22 ?        00:05:12 /usr/bin/python2.3 /usr/local/zope2/lib/python/Zope/Startup/run.py -C /usr/local/be/zopeinstance7.icpeurope.net/config/zope.conf
>zope     28638     1  5 10:22 ?        00:04:54 /usr/bin/python2.3 /usr/local/zope2/lib/python/Zope/Startup/run.py -C /usr/local/be/zopeinstance7.icpeurope.net/config/zope.conf
>It looks like, in this case, PID 28631 has died, leaving orphan zope
>processes.  However, zdrun hasn't noticed this and restarted, presumably
>because these orphans have been left.
>Has anyone got any ideas what I can try to debug/fix this problem?

This is a Python bug. It is currently discussed in "zope-dev at zope.org"
(subject: "[Zope-dev] Segfault and Deadlock").
Search its archive for more information.

We have some chance that the bug will get fixed in the next
Python release (2.3.4).


More information about the Zope mailing list