Hi All, We're having a few problems with our Zope server, it seems to be crashed but were not sure whether it is actually crashed or merely waiting (a long time) for a response from LDAP to authenticate our users, which may be causing it to hang. Is there any tool we can use to test to see if Zope has actally crashed? Jon
# --On 11. Juli 2006 14:20:48 +0100 Jonathan Bowlas <me@jonbowlas.com> wrote:
Hi All,
We're having a few problems with our Zope server, it seems to be crashed but were not sure whether it is actually crashed or merely waiting (a long time) for a response from LDAP to authenticate our users, which may be causing it to hang.
Since Zope is multi-threaded a thread might be blocked by a long-running request. However all worker threads should be able to respond to requests. -aj
Is there any tool we can use to test to see if Zope has actally crashed?
You might want to check out DeadlockDebugger which should give you more information, what your Zope is doing. And you can use Tools like Nagios to check wheter your Zope is answering. hth Maik
On Tue, Jul 11, 2006 at 02:20:48PM +0100, Jonathan Bowlas wrote:
We're having a few problems with our Zope server, it seems to be crashed but were not sure whether it is actually crashed or merely waiting (a long time) for a response from LDAP to authenticate our users, which may be causing it to hang.
Is there any tool we can use to test to see if Zope has actally crashed?
I'm assuming you're on *nix of some flavor. First thing to do is use ps to see if there are any zope-related python processes running. For example: $ ps wax | grep python | grep ope On my gentoo workstation, I'm running both zope and zeo currently, so I get: 9609 ? S 0:05 /usr/local/bin/python /home/pw/z29soft/lib/python/Zope2/Startup/run.py -C /home/pw/z29inst/etc/zope.conf 9610 ? S 0:01 /usr/local/bin/python /home/pw/z29soft/lib/python/ZEO/runzeo.py -C /home/pw/z29inst/etc/zeo.conf If there are no processes, zope is obviously not running at all :) If there are processes but zope is not responding, first thing I would do is check the end of the zope event log and request log. That would help narrow down the time at which problems started. http://zopewiki.org/Z2Log http://zopewiki.org/EventLog Then, try GDB to figure out what zope is doing. http://www.upfrontsystems.co.za/Members/jean/zope-notes/debug-spinning-zope And, to make life easier next time, install http://www.zope.org/Members/nuxeo/Products/DeadlockDebugger finally, another tool that can help diagnose apparent hangs is the trace log, formerly known as the "big M" log. http://zopewiki.org/TraceLog -- Paul Winkler http://www.slinkp.com
----- Original Message ----- From: "Paul Winkler" <pw_lists@slinkp.com> To: <zope@zope.org> Sent: Tuesday, July 11, 2006 10:11 AM Subject: Re: [Zope] Check Zope status
On Tue, Jul 11, 2006 at 02:20:48PM +0100, Jonathan Bowlas wrote:
We're having a few problems with our Zope server, it seems to be crashed but were not sure whether it is actually crashed or merely waiting (a long time) for a response from LDAP to authenticate our users, which may be causing it to hang.
You can also use ZopeProfiler/CallProfiler to see how much time you are spending in the various parts of the application. Jonathan
Many thanks for all the help, I'll check this lot out. Much appreciated. -----Original Message----- From: zope-bounces+me=jonbowlas.com@zope.org [mailto:zope-bounces+me=jonbowlas.com@zope.org] On Behalf Of Paul Winkler Sent: 11 July 2006 15:12 To: zope@zope.org Subject: Re: [Zope] Check Zope status On Tue, Jul 11, 2006 at 02:20:48PM +0100, Jonathan Bowlas wrote:
We're having a few problems with our Zope server, it seems to be crashed but were not sure whether it is actually crashed or merely waiting (a long time) for a response from LDAP to authenticate our users, which may be causing it to hang.
Is there any tool we can use to test to see if Zope has actally crashed?
I'm assuming you're on *nix of some flavor. First thing to do is use ps to see if there are any zope-related python processes running. For example: $ ps wax | grep python | grep ope On my gentoo workstation, I'm running both zope and zeo currently, so I get: 9609 ? S 0:05 /usr/local/bin/python /home/pw/z29soft/lib/python/Zope2/Startup/run.py -C /home/pw/z29inst/etc/zope.conf 9610 ? S 0:01 /usr/local/bin/python /home/pw/z29soft/lib/python/ZEO/runzeo.py -C /home/pw/z29inst/etc/zeo.conf If there are no processes, zope is obviously not running at all :) If there are processes but zope is not responding, first thing I would do is check the end of the zope event log and request log. That would help narrow down the time at which problems started. http://zopewiki.org/Z2Log http://zopewiki.org/EventLog Then, try GDB to figure out what zope is doing. http://www.upfrontsystems.co.za/Members/jean/zope-notes/debug-spinning-zope And, to make life easier next time, install http://www.zope.org/Members/nuxeo/Products/DeadlockDebugger finally, another tool that can help diagnose apparent hangs is the trace log, formerly known as the "big M" log. http://zopewiki.org/TraceLog -- Paul Winkler http://www.slinkp.com _______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
On Jul 11, 2006, at 9:20 AM, Jonathan Bowlas wrote:
Is there any tool we can use to test to see if Zope has actally crashed?
At our company, we wrote something that checks the trace.log file to check the status of the current zope requests. The trace.log file records when a new network connection is opened, when a thread starts processing a request, when a thread is done publishing, and when it has finished writing. The tool continuously re-reads the end of the file looking for new data records and turns those into SNMP data for the number of active requests, the number of queued requests, and the average response time.
participants (6)
-
Andreas Jung -
Andrew Langmead -
Jonathan -
Jonathan Bowlas -
Maik Ihde -
Paul Winkler