Use the Big M log in combination with the requestprofiler script as outlined in the Zope Developers Guide troubleshooting chapter. Holger Lehmann wrote:
Hi all,
we have noticed a very interesting phenomenon: Using Zope 2.3.0 without any add-ons to server static (!) HTML Pages works fine. Sometimes (e.g. late sunday nights) the Zope Master Process seems to restart all his children .... After Upgrading to a new (!) Zope 2.3.3 with the same job to do as above we noticed that the Zope Master Process seemed not to be able anymore to restart it's children but itself died.
Q: Why does this happen ? Q: Whay can 2.3.0 survive and 2.3.3 crashes ? Q: How can we work around it ?
Remark: We have to continue using 2.3.3 since we are developing a dynamic website based on products that do only work properly in 2.3.3 and not in 2.3.0 :-(
Thanks in advance, Holger
-- Chris McDonough Zope Corporation http://www.zope.org http://www.zope.com "Killing hundreds of birds with thousands of stones"