[Zope] Zope threads dying continuosly

[Tim Edwards]

Thanks for your replies, the original reason I asked is that we are having
stability issues with Zope. I have tried it without the demon process, but
that doesn't appear to help. I then reenabled the demon process and changed
the thread count to 500 (I've only just discovered all those options after
looking in z2.py!). This leads me to my next question:

Now the server stays up and running, but the demon manager seems to be
continually killing and restarting the processes.
I'm running it with the -D option as well and this is the error message line
it spits out as it restarts:
2003-11-21T13:13:11 ERROR(200) zdaemon Process 25703 terminated by signal
SIGKILL(9)

Any ideas of what could be causing this?

Thanks

Tim Edwards
-----Original Message-----
From: Dieter Maurer [mailto:dieter at handshake.de]
Sent: Friday, 21 November 2003 5:41 AM
To: Tim Edwards
Cc: 'zope at zope.org'
Subject: Re: [Zope] Why does Zope run multiple instances of z2.py by
default?


Tim Edwards wrote at 2003-11-20 17:54 +1100:
 > I was just wondering why Zope runs multiple threads of z2.py by default?
For
 > example in my ps listing I have:
 > 
 > zope     18183     1  0 10:25 ?        00:00:00
/home/zope/Zope/bin/python
 > /home/zope/Zope/z2.py -u zope -f - p -
 > zope     18184 18183  0 10:25 ?        00:00:10
/home/zope/Zope/bin/python
 > /home/zope/Zope/z2.py -u zope -f - p -

In standard setup (under Unix), you have a "daemon" and
the true Zope process (with several threads).

The daemon supervises the Zope process. If Zope should die unexpectedly,
the daemon logs a message and restarts Zope.

There is a "z2.py" option that causes the daemon not to start.

-- 
Dieter