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 ---------- Summarized: Mon Dec 4 13:56:22 2000: 5527 exited with error code: 11 Mon Dec 4 16:40:13 2000: 10558 exited with error code: 11 Mon Dec 4 17:21:22 2000: 10806 exited with error code: 11 Mon Dec 4 18:08:26 2000: 10876 exited with error code: 11 Mon Dec 4 19:15:57 2000: 10927 exited with error code: 11 Mon Dec 4 19:57:14 2000: 11001 exited with error code: 11 Mon Dec 4 20:34:32 2000: 11034 exited with error code: 11 Mon Dec 4 22:30:00 2000: 11085 exited with error code: 11 Tue Dec 5 01:17:39 2000: 11193 exited with error code: 11 Tue Dec 5 04:07:23 2000: 11384 exited with error code: 11 Tue Dec 5 08:16:33 2000: 11613 exited with error code: 11 Tue Dec 5 11:22:32 2000: 11864 exited with error code: 11 Tue Dec 5 15:00:00 2000: 12375 exited with error code: 11 Tue Dec 5 19:17:21 2000: 12527 exited with error code: 11 Tue Dec 5 20:42:58 2000: 12927 exited with error code: 11 Tue Dec 5 21:37:00 2000: 13077 exited with error code: 11 Tue Dec 5 23:59:01 2000: 13152 exited with error code: 11 Wed Dec 6 12:01:03 2000: 14226 exited with error code: 11 Wed Dec 6 13:51:26 2000: 14277 exited with error code: 11 Wed Dec 6 14:39:57 2000: 14436 exited with error code: 11 Wed Dec 6 14:48:08 2000: 14561 exited with error code: 11 Wed Dec 6 18:02:12 2000: 14596 exited with error code: 11 Wed Dec 6 18:42:59 2000: 14844 exited with error code: 11 Wed Dec 6 22:53:53 2000: 14879 exited with error code: 11 Thu Dec 7 03:25:20 2000: 15187 exited with error code: 11 Thu Dec 7 06:59:31 2000: 15505 exited with error code: 11 Thu Dec 7 09:16:11 2000: 15786 exited with error code: 11 Thu Dec 7 10:06:05 2000: 17377 exited with error code: 11 Thu Dec 7 10:51:56 2000: 17462 exited with error code: 11 Thu Dec 7 11:23:22 2000: 17564 exited with error code: 11 -- 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
It might be interesting to turn on the -M option of z2.py and see if there is any pattern to the crash. This can happen for a number of reasons (e.g., a buggy Python extension, an infinite recursive loop, ....). -steve
"Michael" == Michael Best <mbest@emergence.com> writes:
Michael> I have had Zope 2.0.1, Zope 2.1.6 and Zope 2.2.4 running Michael> on Solaris 2.6 and inexplicably, every so often (no Michael> definiate amount of time) the Zope dies. Michael> Any ideas? Michael> ---------- A typical entry from STUPID_LOG is: Michael> 2000-12-07T18:23:22 ERROR(200) zdaemon zdaemon: Thu Dec 7 Michael> 11:23:22 2000: Aiieee! 17564 exited with error code: 11 Michael> ---------- Summarized: Michael> Mon Dec 4 13:56:22 2000: 5527 exited with error code: 11 Michael> Mon Dec 4 16:40:13 2000: 10558 exited with error code: 11 Michael> Mon Dec 4 17:21:22 2000: 10806 exited with error code: 11 Michael> Mon Dec 4 18:08:26 2000: 10876 exited with error code: 11 Michael> Mon Dec 4 19:15:57 2000: 10927 exited with error code: 11 Michael> Mon Dec 4 19:57:14 2000: 11001 exited with error code: 11 Michael> Mon Dec 4 20:34:32 2000: 11034 exited with error code: 11 Michael> Mon Dec 4 22:30:00 2000: 11085 exited with error code: 11 Michael> Tue Dec 5 01:17:39 2000: 11193 exited with error code: 11 Michael> Tue Dec 5 04:07:23 2000: 11384 exited with error code: 11 Michael> Tue Dec 5 08:16:33 2000: 11613 exited with error code: 11 Michael> Tue Dec 5 11:22:32 2000: 11864 exited with error code: 11 Michael> Tue Dec 5 15:00:00 2000: 12375 exited with error code: 11 Michael> Tue Dec 5 19:17:21 2000: 12527 exited with error code: 11 Michael> Tue Dec 5 20:42:58 2000: 12927 exited with error code: 11 Michael> Tue Dec 5 21:37:00 2000: 13077 exited with error code: 11 Michael> Tue Dec 5 23:59:01 2000: 13152 exited with error code: 11 Michael> Wed Dec 6 12:01:03 2000: 14226 exited with error code: 11 Michael> Wed Dec 6 13:51:26 2000: 14277 exited with error code: 11 Michael> Wed Dec 6 14:39:57 2000: 14436 exited with error code: 11 Michael> Wed Dec 6 14:48:08 2000: 14561 exited with error code: 11 Michael> Wed Dec 6 18:02:12 2000: 14596 exited with error code: 11 Michael> Wed Dec 6 18:42:59 2000: 14844 exited with error code: 11 Michael> Wed Dec 6 22:53:53 2000: 14879 exited with error code: 11 Michael> Thu Dec 7 03:25:20 2000: 15187 exited with error code: 11 Michael> Thu Dec 7 06:59:31 2000: 15505 exited with error code: 11 Michael> Thu Dec 7 09:16:11 2000: 15786 exited with error code: 11 Michael> Thu Dec 7 10:06:05 2000: 17377 exited with error code: 11 Michael> Thu Dec 7 10:51:56 2000: 17462 exited with error code: 11 Michael> Thu Dec 7 11:23:22 2000: 17564 exited with error code: 11 Michael> -- Michael Best Systems Administrator ph 780-413-6397 Michael> x230 Emergence By Design fax 780-433-7548 #200, 11209 Michael> Jasper Avenue toll 866-860-2666 Edmonton, Alberta, T5K Michael> 0L5 Michael> _______________________________________________ Zope Michael> maillist - Zope@zope.org Michael> http://lists.zope.org/mailman/listinfo/zope ** No cross Michael> posts or HTML encoding! ** (Related lists - Michael> http://lists.zope.org/mailman/listinfo/zope-announce Michael> http://lists.zope.org/mailman/listinfo/zope-dev )
Steve Spicklemire wrote:
It might be interesting to turn on the -M option of z2.py and see if there is any pattern to the crash. This can happen for a number of reasons (e.g., a buggy Python extension, an infinite recursive loop, ....).
I wrote a script recently which is able to track a segfault down to the last successful Python call. I used sys.settrace(). I've been considering adding such a thing as a z2.py command-line option with two levels: --trace-calls: log all method calls to a file. --trace-everything: log every Python instruction. To narrow down a segfault, you would first invoke with --trace-calls, and if that doesn't give you enough info, you would invoke with --trace-everything. To eliminate huge log files, the "Houston, I just forked off a kid" daemon could set up a socket to which the main Zope process sends the information. When the segfault occurs, the main process would copy the last 50 calls to the log file. Shane
"Michael" == Michael Best <mbest@emergence.com> writes:
Michael> I have had Zope 2.0.1, Zope 2.1.6 and Zope 2.2.4 running Michael> on Solaris 2.6 and inexplicably, every so often (no Michael> definiate amount of time) the Zope dies.
Michael> Any ideas?
Michael> ---------- A typical entry from STUPID_LOG is: Michael> 2000-12-07T18:23:22 ERROR(200) zdaemon zdaemon: Thu Dec 7 Michael> 11:23:22 2000: Aiieee! 17564 exited with error code: 11 Michael> ---------- Summarized:
Michael> Mon Dec 4 13:56:22 2000: 5527 exited with error code: 11 Michael> Mon Dec 4 16:40:13 2000: 10558 exited with error code: 11 Michael> Mon Dec 4 17:21:22 2000: 10806 exited with error code: 11 Michael> Mon Dec 4 18:08:26 2000: 10876 exited with error code: 11 Michael> Mon Dec 4 19:15:57 2000: 10927 exited with error code: 11 Michael> Mon Dec 4 19:57:14 2000: 11001 exited with error code: 11 Michael> Mon Dec 4 20:34:32 2000: 11034 exited with error code: 11 Michael> Mon Dec 4 22:30:00 2000: 11085 exited with error code: 11 Michael> Tue Dec 5 01:17:39 2000: 11193 exited with error code: 11 Michael> Tue Dec 5 04:07:23 2000: 11384 exited with error code: 11 Michael> Tue Dec 5 08:16:33 2000: 11613 exited with error code: 11 Michael> Tue Dec 5 11:22:32 2000: 11864 exited with error code: 11 Michael> Tue Dec 5 15:00:00 2000: 12375 exited with error code: 11 Michael> Tue Dec 5 19:17:21 2000: 12527 exited with error code: 11 Michael> Tue Dec 5 20:42:58 2000: 12927 exited with error code: 11 Michael> Tue Dec 5 21:37:00 2000: 13077 exited with error code: 11 Michael> Tue Dec 5 23:59:01 2000: 13152 exited with error code: 11 Michael> Wed Dec 6 12:01:03 2000: 14226 exited with error code: 11 Michael> Wed Dec 6 13:51:26 2000: 14277 exited with error code: 11 Michael> Wed Dec 6 14:39:57 2000: 14436 exited with error code: 11 Michael> Wed Dec 6 14:48:08 2000: 14561 exited with error code: 11 Michael> Wed Dec 6 18:02:12 2000: 14596 exited with error code: 11 Michael> Wed Dec 6 18:42:59 2000: 14844 exited with error code: 11 Michael> Wed Dec 6 22:53:53 2000: 14879 exited with error code: 11 Michael> Thu Dec 7 03:25:20 2000: 15187 exited with error code: 11 Michael> Thu Dec 7 06:59:31 2000: 15505 exited with error code: 11 Michael> Thu Dec 7 09:16:11 2000: 15786 exited with error code: 11 Michael> Thu Dec 7 10:06:05 2000: 17377 exited with error code: 11 Michael> Thu Dec 7 10:51:56 2000: 17462 exited with error code: 11 Michael> Thu Dec 7 11:23:22 2000: 17564 exited with error code: 11
Michael> -- Michael Best Systems Administrator ph 780-413-6397 Michael> x230 Emergence By Design fax 780-433-7548 #200, 11209 Michael> Jasper Avenue toll 866-860-2666 Edmonton, Alberta, T5K Michael> 0L5
Michael> _______________________________________________ Zope Michael> maillist - Zope@zope.org Michael> http://lists.zope.org/mailman/listinfo/zope ** No cross Michael> posts or HTML encoding! ** (Related lists - Michael> http://lists.zope.org/mailman/listinfo/zope-announce Michael> http://lists.zope.org/mailman/listinfo/zope-dev )
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
participants (3)
-
Michael Best -
Shane Hathaway -
Steve Spicklemire