Hi Gerrie, I would recommend upgrading to Zope 2.3.2. 2.3.0 had a PythonScript bug that could cause Zope to crash under certain circumstances. Gerrie Roos wrote:
I'm trying to gleen the reason for a sudden disappearance of my Zope process, the first Zope crash I've encountered. I've not run Zope with any special options, haven't specified log files and not altered the debugging level, just the vanilla start script (zope 2.3.0). The only log info I could find was in zope/etc/Z2.log. It only contained connection-related entries, no errors.
I also noticed some peculiar last entries. Here's one:
196.7.146.145: - - [24/May/2001:12:57:18 +0200] "GET /TrispenDB/version_control/Bugs/Interface/Manage/showBug?prID=423 HTTP/1.1" 200 5359 "http://oskar:8080/TrispenDB/version_control/Bugs/Interface/Browse" "Mozilla/4.0 (compatible; MSIE 5.01; Windows NT; TUCOWS)"
This request is not in accord with my zope directory structure. The request should have referred to TrispenDB/Bugs/Interface/Manage/show....blah...blah... since Bugs and version_control are on the same level.
I suppose it is possible to fabricate scenarios under which this improper request could have ocurred...but why did Zope die just right after? How/where can I look for more information?
_______________________________________________ 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 )