Dennis Godfrey wrote:
Any clues? Am I not starting it correctly? (I have always used the Control Panel up until today.)
I run zope/cmf/plone on a debian sarge box, too. And I had this very same problem: run either zopectrl or the /etc/init.d/zope start and then it died. To diagnose the problem, add "Debug: yes" in the /etc/zopectrl/zopectrlrc, then start the server. That gave me the diagnostics I needed. The problem in my case was that /var/lib/zope/instance/default/var needs to be user root and group zope, with the sticky bit set. drwxr-xr-t 2 root zope 232 2003-12-04 07:55 var From /usr/share/doc/zope/SETUID.txt: You must also make sure the var directory is owned by root, and that it has the sticky bit set. This is done by the command 'chmod o+t var' on most systems. When the sticky bit is set on a directory, anyone can write files, but nobody can delete others' files in order to rewrite them. This is necessary to keep others from overwriting the PID file, tricking root into killing processes when 'stop' is run. Once I changed the owner of var, and restarted zope, the server came right up. HTH. Kirk