[Zope] - Zope dies under mysterious circumstances
Andy Dustman
adustman@comstar.net
Thu, 10 Dec 1998 15:21:22 -0500 (EST)
Thus far, I haven't been able to make Zope die, but it does die. I am
actually running it now using the supervise program which comes with
qmail's daemontools package (I get log rotation this way, as well). I know
it died because I checked the contol panel. Going back into the log at
about the time it happened, there are no obvious error messages or
tracebacks, but I do see this:
Publishing module Main
Serving HTTP on port 8080 ...
No core dumps that I can find. Python-1.5.1 (based on the Oli Andrich
SRPMS, so the official patches are there), RedHat 5.1.
Oh, btw, and I just realized I wasn't doing this either: When starting the
server (serve.sh), python should be invoked with -u for unbuffered stdout
and stderr I/O, unless this is being set somewhere within Zope (not sure
how you would do this, though). I have my own xHTTPServer-based app, and
logging works a lot better this way, particularly if you are writing to a
pipe (which I am). My actual startup is:
cd $ZOPEHOME
env - PATH=$PATH \
supervise $ZOPEHOME/var/run /usr/bin/python -u serve.py 2>&1 \
| cyclog $ZOPEHOME/var/log &
(supervise and cyclog are both in qmail's daemontools package.
www.qmail.org)
--
Andy Dustman You should always say "spam" and "eggs"
ComStar Communications Corp. instead of "foo" and "bar"
(706) 549-7689 | PGP KeyID=0xC72F3F1D in Python examples. (Mark Lutz)