In one of my servers, Zope suddenly dies. The Zope processes are gone from the "ps aux" process table and no clue whatsoever is left in any log, including Z2.log My question is, has onyone included Zope (the "start" zope procedure, that is) as an entry in the /etc/inittab in order for the process to reinitiate (respawn) automatically in case it dies. I wm wondering if this is a good idea or not in relation to Zope.....? Of course, the ideal situation would be to solve the crashing factors / issues rather than "patching" the crashing with the inittab respawning. Any comments are welcome, thanks in advance. Felipe Barousse
"Felipe E. Barousse" wrote:
In one of my servers, Zope suddenly dies. The Zope processes are gone from the "ps aux" process table and no clue whatsoever is left in any log, including Z2.log
My question is, has onyone included Zope (the "start" zope procedure, that is) as an entry in the /etc/inittab in order for the process to reinitiate (respawn) automatically in case it dies.
I wm wondering if this is a good idea or not in relation to Zope.....?
Of course, the ideal situation would be to solve the crashing factors / issues rather than "patching" the crashing with the inittab respawning.
Any comments are welcome, thanks in advance.
Since you are on Unix, why not just use "-Z var/Z2.pid "? Works well for me. Bill
Since you are on Unix, why not just use "-Z var/Z2.pid "?
Could explain this a bit further. I had never heard of this and when I went into z2.py I got this.. -Z path Unix only! This option is ignored on windows. If this option is specified, a separate managemnt process will be created that restarts Zope after a shutdown (or crash). The path must point to a pid file that the process will record its process id in. The path may be relative, in which case it will be relative to the Zope location. To prevent use of a separate management process, provide an empty string: -Z '' How does it work? What does it do? Thanks, J
participants (3)
-
Bill Anderson -
Felipe E. Barousse -
J. Atwood