Hi Dave,
i must correct myself. I interpreteted the logrotate configuration
wrongly. The problem occurs everyday when logrotate is run. Although
there is a weekly option the command zopectl logrotate is called
every day. This hangs the zope process. I will add a zopectl
force-reload to get it
David Coe schrieb:
The more details you can provide, the more likely
someone will find the answer.
Are your log files not rotating correctly? If so, show
us, e.g. by running lsof.
More to the point, what is happening, or not happening,
when your users get those 'Temporarily Unavailable'
If you are able, see if you can run zope in debugging mode
(search for the article the Debugger is your Friend at
zope.org, and other places too).
Then show us what zope was doing when it stops responding.
If that's not possible, perhaps a list of all the zope products
installed, and any
Hi,
We just upgraded our production server from zope 2.5.1 to 2.6.4-1.6. Now
we see a lot of these messages. I think your fix to -1.1 did not help.
How can we fix this?
Christoph
--
Christoph Martin, EDV der
The more details you can provide, the more likely
someone will find the answer.
Are your log files not rotating correctly? If so, show
us, e.g. by running lsof.
More to the point, what is happening, or not happening,
when your users get those 'Temporarily Unavailable' messages?
We need
5 matches
Mail list logo
