OK, a while back I sent a mail to this list about my zope install crashing a few times a week. This time I have more info. Zope 2.5.1, running on Slackware. I run zope like this; ./start > zope.out 2>&1 & So now I can see the errors... The last errors I get before it dies are here; 2002-09-05T00:55:30 ERROR(200) ZServer uncaptured python exception, closing channel <ZServer.HTTPServer.zhttp_channel connected 209.170.209.7:1931 at 0x8cd27c4channel#: 885 requests:> (socket.error:(113, 'No route to host') [/usr/local/zope/ZServer/medusa/asynchat.py|handle_read|82] [/usr/local/zope/ZServer/medusa/http_server.py|recv|420] [/usr/local/zope/ZServer/medusa/asyncore.py|recv|357]) ------ 2002-09-05T00:56:36 ERROR(200) ZServer uncaptured python exception, closing channel <ZServer.HTTPServer.zhttp_channel connected 209.170.209.7:1930 at 0x8f89404channel#: 884 requests:> (socket.error:(113, 'No route to host') [/usr/local/zope/ZServer/medusa/asynchat.py|handle_read|82] [/usr/local/zope/ZServer/medusa/http_server.py|recv|420] [/usr/local/zope/ZServer/medusa/asyncore.py|recv|357]) Any ideas? Oh and Shana Tova. dj - Dan Jacobs - 07956 246 659
Dan Jacobs wrote:
OK, a while back I sent a mail to this list about my zope install crashing a few times a week. This time I have more info.
Zope 2.5.1, running on Slackware.
What version of python are you using? It best be 2.1.3 or you'll be berated for not RTFM'ing, and not reading the FAQ'ing mailing list archives ;-) cheers, Chris
OK, a while back I sent a mail to this list about my zope install crashing a few times a week. This time I have more info.
Zope 2.5.1, running on Slackware.
What version of python are you using?
It best be 2.1.3 or you'll be berated for not RTFM'ing, and not reading the FAQ'ing mailing list archives ;-)
Well... I am using a zope binary distrib which comes with 2.1.3 however I do also have 2.1.2 installed on the same box. Could this be the problem? dj
(socket.error:(113, 'No route to host') -> seems like an os, not a zope prob: check route -n to see whether you have a default gateway config´d; zope seems to need one, so could be that zope expects to find a dns server in a different subnet where it can´t find a route to?! just guessing, oliver
OK, a while back I sent a mail to this list about my zope install crashing a few times a week. This time I have more info.
Zope 2.5.1, running on Slackware.
I run zope like this;
./start > zope.out 2>&1 &
So now I can see the errors...
The last errors I get before it dies are here;
2002-09-05T00:55:30 ERROR(200) ZServer uncaptured python exception, closing channel <ZServer.HTTPServer.zhttp_channel connected 209.170.209.7:1931 at 0x8cd27c4channel#: 885 requests:> (socket.error:(113, 'No route to host') [/usr/local/zope/ZServer/medusa/asynchat.py|handle_read|82] [/usr/local/zope/ZServer/medusa/http_server.py|recv|420] [/usr/local/zope/ZServer/medusa/asyncore.py|recv|357]) ------ 2002-09-05T00:56:36 ERROR(200) ZServer uncaptured python exception, closing channel <ZServer.HTTPServer.zhttp_channel connected 209.170.209.7:1930 at 0x8f89404channel#: 884 requests:> (socket.error:(113, 'No route to host') [/usr/local/zope/ZServer/medusa/asynchat.py|handle_read|82] [/usr/local/zope/ZServer/medusa/http_server.py|recv|420] [/usr/local/zope/ZServer/medusa/asyncore.py|recv|357])
Any ideas?
Oh and Shana Tova.
dj
- Dan Jacobs - 07956 246 659
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
_____ To understand recursion, we first have to understand recursion.
Dan Jacobs writes:
OK, a while back I sent a mail to this list about my zope install crashing a few times a week. This time I have more info. ... 2002-09-05T00:56:36 ERROR(200) ZServer uncaptured python exception, closing channel <ZServer.HTTPServer.zhttp_channel connected 209.170.209.7:1930 at 0x8f89404channel#: 884 requests:> (socket.error:(113, 'No route to host') [/usr/local/zope/ZServer/medusa/asynchat.py|handle_read|82] [/usr/local/zope/ZServer/medusa/http_server.py|recv|420] [/usr/local/zope/ZServer/medusa/asyncore.py|recv|357]) This is a low level "medusa/asyncore" error message. It wants to read from a connection and gets a "No route to host" exception. This indicates some strange thing with your routing. Strange about this, is that the "recv" is affected. I would expect such an error rather for a "send" not a "recv".
However, it should not cause Zope to crash. Do you get any other message? Do you get a core file (is often disabled in standard Linux installations; enable it --> "ulimit"). Dieter
participants (4)
-
Chris Withers -
Dan Jacobs -
Dieter Maurer -
Oliver Skiebe