Hi all, first time poster to here, though I've been using Zope since about last March. Here's my issue: Zope runs fine. However, sometimes during a restart of the service (necessitated by either a Zope crash (much less common now), or a new Product installation) the service just hangs. The zdaemon/zdrun.py script runs, and it keeps trying to spawn child processes but these children never come up and eventually die. Now the really screwed up part: I have to uninstall Zope to get the service to come back up. This issue has happened since we installed our new Mandrake 9.2 server for our intranet (running Zope 2.7.0b1 proxied through Apache). Since this has started, I created a new RPM for Mandrake out of the 2.7.0b3 tar and installed it. Zope was up for 33 days until today when I restarted the service to recognize a new product. Is there a lock file being created somewhere that I don't know about? This issue usually seems to come up after Zope has been running a few days under full load as our Intranet server. It is very VERY strange to me that I have to uninstall Zope to get the service back up. Any help would be very appreciated.
James Cammarata wrote at 2004-1-28 15:26 -0600:
Here's my issue: Zope runs fine. However, sometimes during a restart of the service (necessitated by either a Zope crash (much less common now), or a new Product installation) the service just hangs. The zdaemon/zdrun.py script runs, and it keeps trying to spawn child processes but these children never come up and eventually die.
Use the "fg" action of the control script. It starts the program in the "foreground" (not daemonized). You can see the log messages (that otherwise are lost for Zope) and (usually) see the reason of startup failures. -- Dieter
participants (2)
-
Dieter Maurer -
James Cammarata