Thanks for all your help. I have solved the problem with the Deadlock Debugger
which showed up threads locked by a call to Aspell. Re-installing Aspell was
the solution. I was very impressed with this product and all your assistance.
Thanks again
Garry
Have you tried looking at it with the deadlock debugger? That should
give you an idea of what its actually running (and if the deadlock
debugger is usually responsive even when zope isn't and if it isn't
that's also information).
Kevin
-Original Message-
From: [EMAIL PROTECTED]
Yes, couldn't agree more with kevin. DeadlockDebugger is crucial. It
won't change anything other than that you'll have information about
what really needs to change.
As an intermediate solution you can start to increase the number of
Zope threads from 4 to 6 or 8 and see if that kills the CPU of
I was same problems with new IBM hardware 2 yrs ago and etc at past. Wait,
please, your HW will be good after 2..3 months - it needs burning process.
It is known problem with very fresh silicon chips about diffusion of
non-homogenities - look at mfg date at asphalt squares. But my english is
: Thursday, July 03, 2008 9:19 AM
To: Garry Saddington
Cc: zope list user
Subject: Re: [Zope] zope stops responding
Yes, couldn't agree more with kevin. DeadlockDebugger is crucial. It
won't change anything other than that you'll have information about what
really needs to change.
As an intermediate
Hi, I does not agree with You, because my servers runs with 20..150 threads,
because lower number of threads makes for somebody infinity waiting and Zope
under load responding very slow (with external database access). After
increasing threads, response under load is more quickly and more
Samuel Bieri wrote at 2005-5-8 22:44 +0200:
...
Try to run Zope inside a debugger.
I managed to compile GNU debug 6.1.1 on the hp-ux box. When I run zope
inside gdb I get the following:
(gdb) run
snip
2005-05-08T22:29:59 INFO(0) Zope Ready to handle requests
[New thread 2 (system thread
Samuel Bieri [EMAIL PROTECTED] wrote:
When I click on a tal-object (Page Template) to edit it, then zope
stops responding. No error is logged, nothing. I even cannot stop zope
anymore with zopectl stop or control-c if started with runzope. It
seems that zope silently crashes...
You may
Samuel Bieri wrote at 2005-5-7 23:45 +0200:
...
When I click on a tal-object (Page Template) to edit it, then zope
stops responding. No error is logged, nothing. I even cannot stop zope
anymore with zopectl stop or control-c if started with runzope. It
seems that zope silently crashes...
Thank you a lot Florent for the hint !
The DeadlockDebugger seems to install and run correctly:
event.log:
snip
2005-05-08T19:55:20 INFO(0) ZServer HTTP server started at Sun May 8
19:55:20 2005
Hostname: zuse.
Port: 8080
--
2005-05-08T19:55:20 INFO(0) ZServer FTP server
Dieter Maurer wrote:
Samuel Bieri wrote at 2005-5-7 23:45 +0200:
...
When I click on a tal-object (Page Template) to edit it, then zope
stops responding. No error is logged, nothing. I even cannot stop zope
anymore with zopectl stop or control-c if started with runzope. It
seems that zope
On Sun, 8 May 2005, Samuel Bieri wrote:
I managed to compile GNU debug 6.1.1 on the hp-ux box.
I hope it wasn't too much trouble. You could have gotten it from here:
http://www.hp.com/go/wdb
--- here I klick on a tal-obect in zope. Zope freezes. Then I kill
zope.
Program received signal SIGQUIT,
On May 7, 2005, at 23:45 , Samuel Bieri wrote:
Dear list-members
I am desperately trying to get our zope application run on hpux,
and any help is greatly appreciated. I have the following problem:
I know this isn't really helpful, but when it comes to exotic
operating systems like HP-UX you
13 matches
Mail list logo
