Zope crashing (still)
After applying some CVS updates to PythonScripts as posted (last week I believe), I was hoping Zope wouldn't crash. However, after 4 days, it restarted with the following: ------ 2001-04-16T19:51:12 ERROR(200) zdaemon zdaemon: Mon Apr 16 15:51:12 2001: Aiieee! 888 exited with error code: 4 ------ Any clues? _______________________ Ron Bickers Logic Etc, Inc. rbickers@logicetc.com
Ron, No, sorry, nothing rings a bell here. :-( It would be helpful to establish some sort of pattern for these errors. It may be possible to do so using the debug log analyzer script that I probably referred to in the thread about the PythonScript fixes. If the bug is repeatable, we can fix it. ;-) Sorry there's no better news, - C ----- Original Message ----- From: "Ron Bickers" <rbickers@logicetc.com> To: <zope@zope.org> Sent: Monday, April 16, 2001 3:59 PM Subject: [Zope] Zope crashing (still)
After applying some CVS updates to PythonScripts as posted (last week I believe), I was hoping Zope wouldn't crash. However, after 4 days, it restarted with the following:
------ 2001-04-16T19:51:12 ERROR(200) zdaemon zdaemon: Mon Apr 16 15:51:12 2001: Aiieee! 888 exited with error code: 4 ------
Any clues?
_______________________
Ron Bickers Logic Etc, Inc. rbickers@logicetc.com
_______________________________________________ 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 )
Ron, Two things I stupidly forgot to mention in my message about the fix for PythonScripts: - they only happened in the context of the use of "print...", "return printed" - In order to "see" the fix, you need to make a small change to the Python Script body itself (add a space, perhaps), and re-save it. Otherwise the script will continue to cause a segfault. Just FYI... - C ----- Original Message ----- From: "Ron Bickers" <rbickers@logicetc.com> To: <zope@zope.org> Sent: Monday, April 16, 2001 3:59 PM Subject: [Zope] Zope crashing (still)
After applying some CVS updates to PythonScripts as posted (last week I believe), I was hoping Zope wouldn't crash. However, after 4 days, it restarted with the following:
------ 2001-04-16T19:51:12 ERROR(200) zdaemon zdaemon: Mon Apr 16 15:51:12 2001: Aiieee! 888 exited with error code: 4 ------
Any clues?
_______________________
Ron Bickers Logic Etc, Inc. rbickers@logicetc.com
_______________________________________________ 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 )
As I think back, the problem may have started when I decided to start using print in some test scripts. I'll do what you said and see how it goes. Thanks! _______________________ Ron Bickers Logic Etc, Inc. rbickers@logicetc.com
-----Original Message----- From: Chris McDonough [mailto:chrism@digicool.com] Sent: Thursday, April 19, 2001 12:10 PM To: Ron Bickers; zope@zope.org Subject: Re: [Zope] Zope crashing (still)
Ron,
Two things I stupidly forgot to mention in my message about the fix for PythonScripts:
- they only happened in the context of the use of "print...", "return printed"
- In order to "see" the fix, you need to make a small change to the Python Script body itself (add a space, perhaps), and re-save it. Otherwise the script will continue to cause a segfault.
Just FYI...
participants (2)
-
Chris McDonough -
Ron Bickers