Michael Best writes:

I have had Zope 2.0.1, Zope 2.1.6 and Zope 2.2.4 running on Solaris 2.6 and inexplicably, every so often (no definiate amount of time) the Zope dies. .... A typical entry from STUPID_LOG is: 2000-12-07T18:23:22 ERROR(200) zdaemon zdaemon: Thu Dec 7 11:23:22 2000: Aiieee! 17564 exited with error code: 11

Error code 11 means "Segmentation violation", i.e. a severe program error. You should get a core file (unless you have disabled it; you can use "limit", "limits" or "ulimit" (depending on your shell) to control core file generation). Use "<debugger> <zope>/bin/python core" to analyse the core. If you are lucky, you will get a hint where the problem lies. We have had a similar problem some month before. It turned out to be a memory corruption problem in the Oracle client library triggered by the DCOracle module. An upgrade of DCOracle worked around the memory corruption. Dieter