I'd like to thank everyone for the suggestions, we do have a C/Python inhouse product that is attached to this Zope. With the suggestions that were mentioned I should be able to confirm if that is the source of the problem fairly shortly. It is currently my number one culprit. I will have to get our developer to look at the code for that soon. -Mike Tres Seaver wrote:
Michael Best <mbest@emergence.com> wrote:
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.
Any ideas?
---------- 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 is almost certainly a SEGFAULT, which would typically mean a pointer bug in a "C" extension. Can you arrange to get a core file created, and use xdb/gdb to figure out what code was running when the bug juice squirted?
At a higher level, what add-on products are you using with Zope?
Tres.
-- Michael Best Systems Administrator ph 780-413-6397 x230 Emergence By Design fax 780-433-7548 #200, 11209 Jasper Avenue toll 866-860-2666 Edmonton, Alberta, T5K 0L5