[Zope] zope 2.8.5 becomes unresponsive.
Sébastien VINOT
sebastien.vinot at logisphere.fr
Fri Apr 21 02:52:18 EDT 2006
> -----Message d'origine-----
> De : zope-bounces at zope.org [mailto:zope-bounces at zope.org] De
> la part de Paul Winkler
> Envoyé : jeudi 20 avril 2006 15:30
> À : zope at zope.org
> Objet : Re: [Zope] zope 2.8.5 becomes unresponsive.
>
>
> On Thu, Apr 20, 2006 at 05:58:29AM -0700, Erik Myllymaki wrote:
> > Environment is RHEL 3, Zope v2.8.5 (Python 2.3.5).
> >
> > Every couple of days the zope instance will become unresponsive and
> > require
> > a restart. ZMI is inaccessible at these times so I have to
> do run "service
> > my_zope_service restart" in the usual redhat way.
> >
> > There is nothing in the logs, and if I do "service y_zope_service
> > status" I
> > am told "program running; pid=22671"
> >
> > This is a service under very light load.
> >
> > I viewed the chanelog for v2.8.6 and didn't see any changes that
> > address
> > this, and for various reasons I do not want to move into
> the v2.9.x builds.
> >
> > Any guidance appreciated.
>
> google for two things:
> zope deadlock debugger
> "debug spinning zope"
>
> --
>
Hello,
I've read documentation about deadlock and apparently the CPU usage
should be high, isn't it ? Because in my case the CPU usage is falling
to 0.0 (while the python process is still alive).
Sebastien
More information about the Zope
mailing list