another Zope hanging..
Hi! I also now have some problems with a hanging zope. I got something like this in my stupid logfile: 2001-05-03T13:44:39 ERROR(200) ZServer uncaptured python exception, closing channel <select-trigger (pipe) at 81d64c8> (exceptions.OSError:[Errno 11] Die Ressource ist zur Zeit nicht verf?gbar [/opt/Zope-2.3.1-src/ZServer/medusa/asyncore.py|poll|83] [/opt/Zope-2.3.1-src/ZServer/medusa/asyncore.py|handle_read_event|335] [/opt/Zope-2.3.1-src/ZServer/medusa/select_trigger.py|handle_read|77] [/opt/Zope-2.3.1-src/ZServer/medusa/asyncore.py|recv|287] [/opt/Zope-2.3.1-src/ZServer/medusa/asyncore.py|recv|475]) Now my question is simply if I can catch this exception somewhere and get some traceback etc. Actually I am quite confused from the inner workings of medusa so I dunno where to start searching. Can anyone help? (I know about the -M logging but unfortunately this does not help that much..) cheers, Christian -- COM.lounge http://comlounge.net/ communication & design info@comlounge.net
What Python version are you using? ----- Original Message ----- From: "Christian Scholz" <cs@comlounge.net> To: <zope-dev@zope.org> Sent: Thursday, May 03, 2001 11:05 AM Subject: [Zope-dev] another Zope hanging..
Hi!
I also now have some problems with a hanging zope.
I got something like this in my stupid logfile:
2001-05-03T13:44:39 ERROR(200) ZServer uncaptured python exception, closing channel <select-trigger (pipe) at 81d64c8> (exceptions.OSError:[Errno 11] Die Ressource ist zur Zeit nicht verf?gbar [/opt/Zope-2.3.1-src/ZServer/medusa/asyncore.py|poll|83] [/opt/Zope-2.3.1-src/ZServer/medusa/asyncore.py|handle_read_event|335] [/opt/Zope-2.3.1-src/ZServer/medusa/select_trigger.py|handle_read|77] [/opt/Zope-2.3.1-src/ZServer/medusa/asyncore.py|recv|287] [/opt/Zope-2.3.1-src/ZServer/medusa/asyncore.py|recv|475])
Now my question is simply if I can catch this exception somewhere and get some traceback etc. Actually I am quite confused from the inner workings of medusa so I dunno where to start searching.
Can anyone help?
(I know about the -M logging but unfortunately this does not help that much..)
cheers, Christian
-- COM.lounge http://comlounge.net/ communication & design info@comlounge.net
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Hi!
What Python version are you using?
That's 1.5.2 MySQLDA is MySQL-python-0.3.3.tar.gz and ZMySQLDA-2.0.4.tar.gz (if this makes any problems..) Zope is 2.3.1 as suerly have noticed.. :) cheers, christian
----- Original Message ----- From: "Christian Scholz" <cs@comlounge.net> To: <zope-dev@zope.org> Sent: Thursday, May 03, 2001 11:05 AM Subject: [Zope-dev] another Zope hanging..
Hi!
I also now have some problems with a hanging zope.
I got something like this in my stupid logfile:
2001-05-03T13:44:39 ERROR(200) ZServer uncaptured python exception, closing channel <select-trigger (pipe) at 81d64c8> (exceptions.OSError:[Errno 11] Die Ressource ist zur Zeit nicht verf?gbar [/opt/Zope-2.3.1-src/ZServer/medusa/asyncore.py|poll|83] [/opt/Zope-2.3.1-src/ZServer/medusa/asyncore.py|handle_read_event|335] [/opt/Zope-2.3.1-src/ZServer/medusa/select_trigger.py|handle_read|77] [/opt/Zope-2.3.1-src/ZServer/medusa/asyncore.py|recv|287] [/opt/Zope-2.3.1-src/ZServer/medusa/asyncore.py|recv|475])
Now my question is simply if I can catch this exception somewhere and get some traceback etc. Actually I am quite confused from the inner workings of medusa so I dunno where to start searching.
Can anyone help?
(I know about the -M logging but unfortunately this does not help that much..)
cheers, Christian
-- COM.lounge http://comlounge.net/ communication & design info@comlounge.net
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
-- COM.lounge http://comlounge.net/ communication & design info@comlounge.net
Alright... so you're getting an OSError 11, and you're using Zope 2.3.1. errno 11 is "temporarily unavailable" which means about as much as "foobar feeblefar" as far as I'm concerned ;-). Though you've said the -M log isn't helpful here, I think it is. If this is happening when a certain method is hit, or at a certain time of day, or when a certain number of connections are reached, etc., the -M log in combination with requestprofiler can help determine this. Otherwise it's a guessing game. - C ----- Original Message ----- From: "Christian Scholz" <cs@comlounge.net> To: "Chris McDonough" <chrism@digicool.com> Cc: <zope-dev@zope.org>; "Christian Scholz" <cs@comlounge.net> Sent: Thursday, May 03, 2001 11:22 AM Subject: Re: [Zope-dev] another Zope hanging..
Hi!
What Python version are you using?
That's 1.5.2
MySQLDA is MySQL-python-0.3.3.tar.gz and ZMySQLDA-2.0.4.tar.gz
(if this makes any problems..)
Zope is 2.3.1 as suerly have noticed.. :)
cheers, christian
----- Original Message ----- From: "Christian Scholz" <cs@comlounge.net> To: <zope-dev@zope.org> Sent: Thursday, May 03, 2001 11:05 AM Subject: [Zope-dev] another Zope hanging..
Hi!
I also now have some problems with a hanging zope.
I got something like this in my stupid logfile:
2001-05-03T13:44:39 ERROR(200) ZServer uncaptured python exception, closing channel <select-trigger (pipe) at 81d64c8> (exceptions.OSError:[Errno 11] Die Ressource ist zur Zeit nicht verf?gbar [/opt/Zope-2.3.1-src/ZServer/medusa/asyncore.py|poll|83] [/opt/Zope-2.3.1-src/ZServer/medusa/asyncore.py|handle_read_event|335] [/opt/Zope-2.3.1-src/ZServer/medusa/select_trigger.py|handle_read|77] [/opt/Zope-2.3.1-src/ZServer/medusa/asyncore.py|recv|287] [/opt/Zope-2.3.1-src/ZServer/medusa/asyncore.py|recv|475])
Now my question is simply if I can catch this exception somewhere and get some traceback etc. Actually I am quite confused from the inner workings of medusa so I dunno where to start searching.
Can anyone help?
(I know about the -M logging but unfortunately this does not help that much..)
cheers, Christian
-- COM.lounge http://comlounge.net/ communication & design info@comlounge.net
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
-- COM.lounge http://comlounge.net/ communication & design info@comlounge.net
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Hi!
Alright... so you're getting an OSError 11, and you're using Zope 2.3.1.
errno 11 is "temporarily unavailable" which means about as much as "foobar feeblefar" as far as I'm concerned ;-).
great :)
Though you've said the -M log isn't helpful here, I think it is. If this is happening when a certain method is hit, or at a certain time of day, or when a certain number of connections are reached, etc., the -M log in combination with requestprofiler can help determine this. Otherwise it's a guessing game.
ok, just thought that maybe some exception can be caught.. I will try to use requestprofiler now, though I checked the -M log before and around that time there was no obvious problem.. (also it's not loaded at the moment and it's happening here and then, don't see a pattern there..) I will check (and maybe change the mysql adapter, as I recently had problems with it on a sun machine, too). thanks anyway :) Christian
Hi, most problems with hanging zope come from external RDBMS-access. You wont see anything useful in the logs because there are some objects published before the *sql-method is hanging. If you have a monitor program for your database, you see many blocks on tables or rows during this times. I expect it with DB-adapters not fully thread aware and - with to high timeout. In fact it seems we need timeoutsockets and asynchronous rdb-access. If one thread is hanging, in the scope of 120 instructions, zope has to wait before the global interpreter lock frees. So if its stuck in the call of a C library (database adaptors are most in C) it cannot continue until the call returns. Regards Tino Wildenhain --On Donnerstag, 3. Mai 2001 17:51 +0200 Christian Scholz <cs@comlounge.net> wrote:
Hi!
Alright... so you're getting an OSError 11, and you're using Zope 2.3.1.
errno 11 is "temporarily unavailable" which means about as much as "foobar feeblefar" as far as I'm concerned ;-).
great :)
Though you've said the -M log isn't helpful here, I think it is. If this is happening when a certain method is hit, or at a certain time of day, or when a certain number of connections are reached, etc., the -M log in combination with requestprofiler can help determine this. Otherwise it's a guessing game.
ok, just thought that maybe some exception can be caught.. I will try to use requestprofiler now, though I checked the -M log before and around that time there was no obvious problem.. (also it's not loaded at the moment and it's happening here and then, don't see a pattern there..)
I will check (and maybe change the mysql adapter, as I recently had problems with it on a sun machine, too).
thanks anyway :)
Christian
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Hi,
most problems with hanging zope come from external RDBMS-access.
Lots do, but lots don't...
You wont see anything useful in the logs because there are some objects published before the *sql-method is hanging.
If you see a request come into ZServer, and you see the request go into ZPublisher from ZServer, but ZPublisher never returns any data to ZServer, that's an indication that something is wrong. A SQL method hanging would look like this, it's the same thing as any other Zope component hanging. The "big-M" log is your friend, even in this case. As a matter of fact, it's *especially* your friend in this case because it will be patterned against one or a few methods, which is an easy problem to track down.
Hi!
most problems with hanging zope come from external RDBMS-access.
Lots do, but lots don't...
You wont see anything useful in the logs because there are some objects published before the *sql-method is hanging.
If you see a request come into ZServer, and you see the request go into ZPublisher from ZServer, but ZPublisher never returns any data to ZServer, that's an indication that something is wrong. A SQL method hanging would look like this, it's the same thing as any other Zope component hanging.
The "big-M" log is your friend, even in this case. As a matter of fact, it's *especially* your friend in this case because it will be patterned against one or a few methods, which is an easy problem to track down.
Well, my problem might be that in my case most sql statement are done inside some attribute provider of ZPatterns.. This is using ZSQL methods internally but actually those then won't show up I guess.. I've also seen that some more recent version of the mysql stuff is around and I am using this now.. The problem's also that I just have a few methods to invoke from the outside which do lots of things by calling other object. Thus I might not really see what's really causing the problem.. I hope though that my upgrade will show some benefit.. (strangely on my development server these problems did not arise.. might have to check for any differences between the two..) I will keep cheking the -M anyway (as it seems all I can do.. ;-) cheers, Christian -- COM.lounge http://comlounge.net/ communication & design info@comlounge.net
Well, my problem might be that in my case most sql statement are done inside some attribute provider of ZPatterns.. This is using ZSQL methods internally but actually those then won't show up I guess..
Even if you weren't using ZPatterns, the error probably wouldn't jump out and say "here I am!" So I don't think there's much difference between using ZPatterns and not using ZPatterns. The process of detecting when something hangs is just like any other troubleshooting process, it's a matter of exclusion. If you notice that the request named "foobargorf/fleafang" *always* hangs, you investigate what it does, and try to reproduce it. If it's incidental, so be it, and move on to the next theory.
I've also seen that some more recent version of the mysql stuff is around and I am using this now..
The problem's also that I just have a few methods to invoke from the
outside
which do lots of things by calling other object. Thus I might not really see what's really causing the problem.. I hope though that my upgrade will show some benefit..
The -M log perhaps won't show you the actual operation that's causing the hang, but it will show you the entry point into a routine which causes the hang. It's your job from there to track down the cause. This is just like debugging a program. You get an error somewhere, and you need to track it back to its root, which may be six levels up the call stack buried in some godforsaken regex. ;-)
Hi! Just FYI: The server still hangs once a day and another one is doing the same.. It even does this when simply accessing one page or image over and over again. More precisely I've started the server and did ab -n 100000 -c 10 http://foo.bar/we/pics/someimg.gif (ab being the apache benchmarking utility) and after a while I get the broken pipe error. I've also changed my python version to 2.0 and tested it with this but still the same effect. Also changing the server (and thus hardware and system) did not help it. I've also removed the mysqlda from the zope installation but also this did not help.. I will try now to create the smallest version of the site that still hangs.. Dunno if anybody has some idea, I actually have none.. I'll keep you informed.. -- christian PS: strangely it works on the development server but also here I am doing some tests with ab right now.. and this one is still 1.5.2 On Thu, May 03, 2001 at 02:16:30PM -0400, Chris McDonough wrote:
Well, my problem might be that in my case most sql statement are done inside some attribute provider of ZPatterns.. This is using ZSQL methods internally but actually those then won't show up I guess..
Even if you weren't using ZPatterns, the error probably wouldn't jump out and say "here I am!" So I don't think there's much difference between using ZPatterns and not using ZPatterns. The process of detecting when something hangs is just like any other troubleshooting process, it's a matter of exclusion. If you notice that the request named "foobargorf/fleafang" *always* hangs, you investigate what it does, and try to reproduce it. If it's incidental, so be it, and move on to the next theory.
I've also seen that some more recent version of the mysql stuff is around and I am using this now..
The problem's also that I just have a few methods to invoke from the
outside
which do lots of things by calling other object. Thus I might not really see what's really causing the problem.. I hope though that my upgrade will show some benefit..
The -M log perhaps won't show you the actual operation that's causing the hang, but it will show you the entry point into a routine which causes the hang. It's your job from there to track down the cause. This is just like debugging a program. You get an error somewhere, and you need to track it back to its root, which may be six levels up the call stack buried in some godforsaken regex. ;-)
-- COM.lounge http://comlounge.net/ communication & design info@comlounge.net
Is there any evidence of any sort of relationship between the broken pipe error and the hang? Do they happen at the same time? Or do they have no discernable relationship with one another? How about memory utilization? Is the process leaking memory? ----- Original Message ----- From: "Christian Scholz" <cs@comlounge.net> To: "Chris McDonough" <chrism@digicool.com> Cc: "Christian Scholz" <cs@comlounge.net>; "Tino Wildenhain" <tino@wildenhain.de>; <zope-dev@zope.org> Sent: Friday, May 18, 2001 10:13 AM Subject: Re: [Zope-dev] another Zope hanging..
Hi!
Just FYI: The server still hangs once a day and another one is doing the same.. It even does this when simply accessing one page or image over and over again. More precisely I've started the server and did
ab -n 100000 -c 10 http://foo.bar/we/pics/someimg.gif
(ab being the apache benchmarking utility)
and after a while I get the broken pipe error.
I've also changed my python version to 2.0 and tested it with this but still the same effect. Also changing the server (and thus hardware and system) did not help it. I've also removed the mysqlda from the zope installation but also this did not help.. I will try now to create the smallest version of the site that still hangs..
Dunno if anybody has some idea, I actually have none..
I'll keep you informed..
-- christian
PS: strangely it works on the development server but also here I am doing some tests with ab right now.. and this one is still 1.5.2
On Thu, May 03, 2001 at 02:16:30PM -0400, Chris McDonough wrote:
Well, my problem might be that in my case most sql statement are done inside some attribute provider of ZPatterns.. This is using ZSQL methods internally but actually those then won't show up I guess..
Even if you weren't using ZPatterns, the error probably wouldn't jump out and say "here I am!" So I don't think there's much difference between using ZPatterns and not using ZPatterns. The process of detecting when something hangs is just like any other troubleshooting process, it's a matter of exclusion. If you notice that the request named "foobargorf/fleafang" *always* hangs, you investigate what it does, and try to reproduce it. If it's incidental, so be it, and move on to the next theory.
I've also seen that some more recent version of the mysql stuff is
around
and I am using this now..
The problem's also that I just have a few methods to invoke from the outside which do lots of things by calling other object. Thus I might not really see what's really causing the problem.. I hope though that my upgrade will show some benefit..
The -M log perhaps won't show you the actual operation that's causing the hang, but it will show you the entry point into a routine which causes the hang. It's your job from there to track down the cause. This is just like debugging a program. You get an error somewhere, and you need to track it back to its root, which may be six levels up the call stack buried in some godforsaken regex. ;-)
-- COM.lounge http://comlounge.net/ communication & design info@comlounge.net
Hi!
Is there any evidence of any sort of relationship between the broken pipe error and the hang? Do they happen at the same time? Or do they have no discernable relationship with one another? How about memory utilization? Is the process leaking memory?
yes, they happen at the same time.. I've also stripped it down and removed evertyhing and put some test.gif up there.. Then running ab against it created again a broken pipe (quite soon). looking via top the memory utilization seems ok.. -- christian PS: with this test.gif it seems to hang very quickly.. PPS: ab tests on my development host are still running without problems.. strange..
----- Original Message ----- From: "Christian Scholz" <cs@comlounge.net> To: "Chris McDonough" <chrism@digicool.com> Cc: "Christian Scholz" <cs@comlounge.net>; "Tino Wildenhain" <tino@wildenhain.de>; <zope-dev@zope.org> Sent: Friday, May 18, 2001 10:13 AM Subject: Re: [Zope-dev] another Zope hanging..
Hi!
Just FYI: The server still hangs once a day and another one is doing the same.. It even does this when simply accessing one page or image over and over again. More precisely I've started the server and did
ab -n 100000 -c 10 http://foo.bar/we/pics/someimg.gif
(ab being the apache benchmarking utility)
and after a while I get the broken pipe error.
I've also changed my python version to 2.0 and tested it with this but still the same effect. Also changing the server (and thus hardware and system) did not help it. I've also removed the mysqlda from the zope installation but also this did not help.. I will try now to create the smallest version of the site that still hangs..
Dunno if anybody has some idea, I actually have none..
I'll keep you informed..
-- christian
PS: strangely it works on the development server but also here I am doing some tests with ab right now.. and this one is still 1.5.2
On Thu, May 03, 2001 at 02:16:30PM -0400, Chris McDonough wrote:
Well, my problem might be that in my case most sql statement are done inside some attribute provider of ZPatterns.. This is using ZSQL methods internally but actually those then won't show up I guess..
Even if you weren't using ZPatterns, the error probably wouldn't jump out and say "here I am!" So I don't think there's much difference between using ZPatterns and not using ZPatterns. The process of detecting when something hangs is just like any other troubleshooting process, it's a matter of exclusion. If you notice that the request named "foobargorf/fleafang" *always* hangs, you investigate what it does, and try to reproduce it. If it's incidental, so be it, and move on to the next theory.
I've also seen that some more recent version of the mysql stuff is
around
and I am using this now..
The problem's also that I just have a few methods to invoke from the outside which do lots of things by calling other object. Thus I might not really see what's really causing the problem.. I hope though that my upgrade will show some benefit..
The -M log perhaps won't show you the actual operation that's causing the hang, but it will show you the entry point into a routine which causes the hang. It's your job from there to track down the cause. This is just like debugging a program. You get an error somewhere, and you need to track it back to its root, which may be six levels up the call stack buried in some godforsaken regex. ;-)
-- COM.lounge http://comlounge.net/ communication & design info@comlounge.net
-- COM.lounge http://comlounge.net/ communication & design info@comlounge.net
Hi!
Is there any evidence of any sort of relationship between the broken pipe error and the hang? Do they happen at the same time? Or do they have no discernable relationship with one another? How about memory utilization? Is the process leaking memory?
yes, they happen at the same time..
Excellent! Now we just need to be able to repeat it here.... if you're able to repeat it well enough, and you're running Zope on Windows or Linux, and you're willing to do so, please archive your whole Zope dir and send it to me (if feasible, I don't want a 200MB Data.fs ;-) - C
Hi! Hm, another strange thing.. I've now tried to start Zope via the normal ./start script. (I've done it via some own script with INSTANCE_HOME set). What I've got was: bash-2.04# ./start ------ 2001-05-18T14:59:49 PANIC(300) z2 Startup exception Traceback (innermost last): File /opt/zopeneu/z2.py, line 566, in ? File <string>, line 1, in ? File /opt/zopeneu/lib/python/Zope/__init__.py, line 94, in ? File /opt/zopeneu/lib/python/ZODB/__init__.py, line 85, in ? ImportError: undefined symbol: PyObject_Init So what does this want to tell me? ;-) I've also done the following before that: - delete Data.fs in my instance home - create a new user - create a folder - put an image (test.gif) into that folder - started the test on that image => hang I've also removed any products I don't need which still have been installed.. -- christian On Fri, May 18, 2001 at 10:49:23AM -0400, Chris McDonough wrote:
Is there any evidence of any sort of relationship between the broken pipe error and the hang? Do they happen at the same time? Or do they have no discernable relationship with one another? How about memory utilization? Is the process leaking memory?
----- Original Message ----- From: "Christian Scholz" <cs@comlounge.net> To: "Chris McDonough" <chrism@digicool.com> Cc: "Christian Scholz" <cs@comlounge.net>; "Tino Wildenhain" <tino@wildenhain.de>; <zope-dev@zope.org> Sent: Friday, May 18, 2001 10:13 AM Subject: Re: [Zope-dev] another Zope hanging..
Hi!
Just FYI: The server still hangs once a day and another one is doing the same.. It even does this when simply accessing one page or image over and over again. More precisely I've started the server and did
ab -n 100000 -c 10 http://foo.bar/we/pics/someimg.gif
(ab being the apache benchmarking utility)
and after a while I get the broken pipe error.
I've also changed my python version to 2.0 and tested it with this but still the same effect. Also changing the server (and thus hardware and system) did not help it. I've also removed the mysqlda from the zope installation but also this did not help.. I will try now to create the smallest version of the site that still hangs..
Dunno if anybody has some idea, I actually have none..
I'll keep you informed..
-- christian
PS: strangely it works on the development server but also here I am doing some tests with ab right now.. and this one is still 1.5.2
On Thu, May 03, 2001 at 02:16:30PM -0400, Chris McDonough wrote:
Well, my problem might be that in my case most sql statement are done inside some attribute provider of ZPatterns.. This is using ZSQL methods internally but actually those then won't show up I guess..
Even if you weren't using ZPatterns, the error probably wouldn't jump out and say "here I am!" So I don't think there's much difference between using ZPatterns and not using ZPatterns. The process of detecting when something hangs is just like any other troubleshooting process, it's a matter of exclusion. If you notice that the request named "foobargorf/fleafang" *always* hangs, you investigate what it does, and try to reproduce it. If it's incidental, so be it, and move on to the next theory.
I've also seen that some more recent version of the mysql stuff is
around
and I am using this now..
The problem's also that I just have a few methods to invoke from the outside which do lots of things by calling other object. Thus I might not really see what's really causing the problem.. I hope though that my upgrade will show some benefit..
The -M log perhaps won't show you the actual operation that's causing the hang, but it will show you the entry point into a routine which causes the hang. It's your job from there to track down the cause. This is just like debugging a program. You get an error somewhere, and you need to track it back to its root, which may be six levels up the call stack buried in some godforsaken regex. ;-)
-- COM.lounge http://comlounge.net/ communication & design info@comlounge.net
-- COM.lounge http://comlounge.net/ communication & design info@comlounge.net
------ 2001-05-18T14:59:49 PANIC(300) z2 Startup exception Traceback (innermost last): File /opt/zopeneu/z2.py, line 566, in ? File <string>, line 1, in ? File /opt/zopeneu/lib/python/Zope/__init__.py, line 94, in ? File /opt/zopeneu/lib/python/ZODB/__init__.py, line 85, in ? ImportError: undefined symbol: PyObject_Init
So what does this want to tell me? ;-)
It's telling you that you're running a Zope compiled with Python 2.X under Python 1.5.2..
Hi! Another test without apache inbetween is still running now.. Could apache and it's proxypass be the problem? I am simply using ProxyPass and ProxyPassReverse in front of Zope in a simple virtual site environment.. Apache version is 1.3.19 Where is the bug then? In Zope or in Apache? I also have other servers running like that for ages without problems though it's another host and thus another apache version. cheers, Christian -- COM.lounge http://comlounge.net/ communication & design info@comlounge.net
Could be, this is a big clue... I'd encourage you to continue diagnosis and see if you can categorically determine that this doesn't happen with ZServer only. I will not be able to try to replicate your problem until next week.. ----- Original Message ----- From: "Christian Scholz" <cs@comlounge.net> To: "Chris McDonough" <chrism@digicool.com> Cc: "Christian Scholz" <cs@comlounge.net>; "Tino Wildenhain" <tino@wildenhain.de>; <zope-dev@zope.org> Sent: Friday, May 18, 2001 11:36 AM Subject: Re: [Zope-dev] another Zope hanging..
Hi!
Another test without apache inbetween is still running now.. Could apache and it's proxypass be the problem?
I am simply using ProxyPass and ProxyPassReverse in front of Zope in a simple virtual site environment..
Apache version is 1.3.19
Where is the bug then? In Zope or in Apache? I also have other servers running like that for ages without problems though it's another host and thus another apache version.
cheers, Christian
-- COM.lounge http://comlounge.net/ communication & design info@comlounge.net
just for general information: Apache was not the problem.. PCGI also shows the problem.. a Zope binary release did not help it too bad.. ;-) -- christian On Fri, May 18, 2001 at 05:36:47PM +0200, Christian Scholz wrote:
Hi!
Another test without apache inbetween is still running now.. Could apache and it's proxypass be the problem?
I am simply using ProxyPass and ProxyPassReverse in front of Zope in a simple virtual site environment..
Apache version is 1.3.19
Where is the bug then? In Zope or in Apache? I also have other servers running like that for ages without problems though it's another host and thus another apache version.
cheers, Christian
-- COM.lounge http://comlounge.net/ communication & design info@comlounge.net
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
-- COM.lounge http://comlounge.net/ communication & design info@comlounge.net
I've added a patch to Python 2.1 on sourceforge that helped me considerably when diagnosing multi-threaded Python lock ups. See http://sourceforge.net/tracker/index.php?func=detail&aid=421709&group_id=547... for the submitted patch. I created this to give me at least as much functionality as Java has to dump the stack trace of all Java threads and Java monitors. For an example of how I used it see http://lists.zope.org/pipermail/zodb-dev/2001-May/000703.html in the ZODB dev list. Hope this helps, John On Friday 18 May 2001 09:13, Christian Scholz wrote:
Hi!
Just FYI: The server still hangs once a day and another one is doing the same.. It even does this when simply accessing one page or image over and over again. More precisely I've started the server and did
ab -n 100000 -c 10 http://foo.bar/we/pics/someimg.gif
(ab being the apache benchmarking utility)
and after a while I get the broken pipe error.
I've also changed my python version to 2.0 and tested it with this but still the same effect. Also changing the server (and thus hardware and system) did not help it. I've also removed the mysqlda from the zope installation but also this did not help.. I will try now to create the smallest version of the site that still hangs..
Dunno if anybody has some idea, I actually have none..
I'll keep you informed..
-- christian
PS: strangely it works on the development server but also here I am doing some tests with ab right now.. and this one is still 1.5.2
On Thu, May 03, 2001 at 02:16:30PM -0400, Chris McDonough wrote:
Well, my problem might be that in my case most sql statement are done
inside
some attribute provider of ZPatterns.. This is using ZSQL methods
internally
but actually those then won't show up I guess..
Even if you weren't using ZPatterns, the error probably wouldn't jump out and say "here I am!" So I don't think there's much difference between using ZPatterns and not using ZPatterns. The process of detecting when something hangs is just like any other troubleshooting process, it's a matter of exclusion. If you notice that the request named "foobargorf/fleafang" *always* hangs, you investigate what it does, and try to reproduce it. If it's incidental, so be it, and move on to the next theory.
I've also seen that some more recent version of the mysql stuff is around and I am using this now..
The problem's also that I just have a few methods to invoke from the
outside
which do lots of things by calling other object. Thus I might not really
see
what's really causing the problem.. I hope though that my upgrade will
show some
benefit..
The -M log perhaps won't show you the actual operation that's causing the hang, but it will show you the entry point into a routine which causes the hang. It's your job from there to track down the cause. This is just like debugging a program. You get an error somewhere, and you need to track it back to its root, which may be six levels up the call stack buried in some godforsaken regex. ;-)
-- . . . . . . . . . . . . . . . . . . . . . . . . John D. Heintz | Senior Engineer 1016 La Posada Dr. | Suite 240 | Austin TX 78752 T 512.633.1198 | jheintz@isogen.com w w w . d a t a c h a n n e l . c o m
Maybe another general question: How are exceptions handled which appear in your own products and you don't catch them? Is there some except somewhere "on top" ? How does this look if you're using ZPatterns with your own attribute providers (as I do with my sql attribute provider). Are these all handled somehow? (usually I get some sort of traceback on the console/stupid log is something goes wrong there and I don't handle it myself.. hope it's in general..) cheers, Christian On Thu, May 03, 2001 at 11:23:54AM -0400, Chris McDonough wrote:
What Python version are you using?
----- Original Message ----- From: "Christian Scholz" <cs@comlounge.net> To: <zope-dev@zope.org> Sent: Thursday, May 03, 2001 11:05 AM Subject: [Zope-dev] another Zope hanging..
Hi!
I also now have some problems with a hanging zope.
I got something like this in my stupid logfile:
2001-05-03T13:44:39 ERROR(200) ZServer uncaptured python exception, closing channel <select-trigger (pipe) at 81d64c8> (exceptions.OSError:[Errno 11] Die Ressource ist zur Zeit nicht verf?gbar [/opt/Zope-2.3.1-src/ZServer/medusa/asyncore.py|poll|83] [/opt/Zope-2.3.1-src/ZServer/medusa/asyncore.py|handle_read_event|335] [/opt/Zope-2.3.1-src/ZServer/medusa/select_trigger.py|handle_read|77] [/opt/Zope-2.3.1-src/ZServer/medusa/asyncore.py|recv|287] [/opt/Zope-2.3.1-src/ZServer/medusa/asyncore.py|recv|475])
Now my question is simply if I can catch this exception somewhere and get some traceback etc. Actually I am quite confused from the inner workings of medusa so I dunno where to start searching.
Can anyone help?
(I know about the -M logging but unfortunately this does not help that much..)
cheers, Christian
-- COM.lounge http://comlounge.net/ communication & design info@comlounge.net
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
-- COM.lounge http://comlounge.net/ communication & design info@comlounge.net
Maybe another general question:
How are exceptions handled which appear in your own products and you don't
catch them?
Is there some except somewhere "on top" ?
Yes, in ZPublisher, there's an "exception hook". I don't know more about it than that.
How does this look if you're using ZPatterns with your own attribute
providers (as I do
with my sql attribute provider). Are these all handled somehow? (usually I get some sort of traceback on the console/stupid log is something goes wrong there and I don't handle it myself.. hope it's in general..)
No idea, sorry. I'd imagine they're handled by the same exception handler.
participants (4)
-
Chris McDonough -
cs＠comlounge.net -
John D. Heintz -
Tino Wildenhain