I have had zopes like that on different linux versions. Following
identified reasons on the different installations:
1. LDUF timeout(s) where -1
After upgrading LDUF where you could set timeouts and linux/zope
version the operation -1 timeout caused deadlock and no response from
zope for 5-15
Am 29.04.2006, 21:36 Uhr
tat Sasha Vincic [EMAIL PROTECTED] schraben:
I have had zopes like that on different linux versions. Following
identified reasons on the different installations:
1. LDUF timeout(s) where -1
[...]
2. LinguaPlone had a bug or something, Jodok found this and
I got a chance to try and debug with the the DeadlockDebugger, but it was
unresponsive...
Still nothing in the event log.
Any other ideas?
Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21 Apr 2006, at 07:52, Sébastien VINOT wrote:
I've read documentation about
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De
la part de Paul Winkler
Envoyé : jeudi 20 avril 2006 15:30
À : zope@zope.org
Objet : Re: [Zope] zope 2.8.5 becomes unresponsive.
On Thu, Apr 20, 2006 at 05:58:29AM -0700, Erik Myllymaki wrote
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21 Apr 2006, at 07:52, Sébastien VINOT wrote:
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).
No.
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