Zope process dies in minutes
I would really like to build a Zope+Plone intranet, but I'm having a great deal of difficulty getting Zope 2.7 to stay alive on Fedora Core 3. Most of my searching indicates that this is a memory issue, but I've seen it on two different boxes. The first has 768MB RAM and the second has 256MB, with an additional 4GB partition as swap space. I've seen a supposed fix for RH9 (http://mail.zope.org/pipermail/zope/2003-May/135544.html), but that involves a Zope start script, which I either don't have or can't find. Can anyone tell me how to keep Zope 2.7 running on FC3? Thanks in advance.
Nicholas Shewmaker wrote:
I would really like to build a Zope+Plone intranet, but I'm having a great deal of difficulty getting Zope 2.7 to stay alive on Fedora Core 3. Most of my searching indicates that this is a memory issue, but I've seen it on two different boxes. The first has 768MB RAM and the second has 256MB, with an additional 4GB partition as swap space.
Firstup, find out more about the problem. Look in event.log and see if htere is anything. Fiddle in zope.conf and drop the logging level to debug, maybe turn on detailed logging and get some info that way. Also, try seeing if you can provoke the problem using runzope instead of zopectl. You currently don't have enough info to even think of guessing what the problem is ;-) cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
It was a permissions issue. The user I had specified in the instance creation was unable to write to the instance home, and therefore couldn't create a lock file. The errors weren't apparent until I ran runzope. Thank you for your help.
participants (2)
-
Chris Withers -
Nicholas Shewmaker