Hi Zoppiste, Since 2 weeks I had dreams. The ZServer from Zope-2.0.1 was stable. zhttpserver was forgotten. But now I had bad experiences with zope. The ZServer crash four times this lastest two weeks and I did not find explanation :( My startup file contain the following lines. I never observed -Z option in action !! : #! /bin/sh reldir=`dirname $0` PYTHONHOME=`cd $reldir; pwd` export PYTHONHOME exec /opt/zope/Zope-2.0.1/bin/python \ $PYTHONHOME/z2.py \ -d '192.152.167.62' -Z 'var/Z2.pid' -D "$@" I catch only these following errors : 1/ "1999-11-10T13:39:57 PROBLEM(100) ZServer unhandled connect event" when I start ZServer with 2/ 1999-11-10T14:11:59 ERROR(200) ZServer uncaptured python exception, closing channel <zhttp_channel connected 192.152.167.199:4145 at 8595b08 channel#: 76 requests:1> (socket.error:(9, 'Bad file descriptor') [/opt/zope/Zope-2.0.1/ZServer/medusa/asynchat.py|initiate_send|211] [/opt/zope/Zope-2.0.1/ZServer/medusa/http_server.py|send|394] [/opt/zope/Zope-2.0.1/ZServer/medusa/asyncore.py|send|237]) 918 Did somebody bad experiences with this ZServer? My config is : Suse-6.2 + Intel686 + Zope-2.0.1 Bye, FR.
On Wed, 10 Nov 1999, Francois Chalaoux wrote:
Hi Zoppiste,
2/ 1999-11-10T14:11:59 ERROR(200) ZServer uncaptured python exception, closing channel <zhttp_channel connected 192.152.167.199:4145 at 8595b08 channel#: 76 requests:1> (socket.error:(9, 'Bad file descriptor') [/opt/zope/Zope-2.0.1/ZServer/medusa/asynchat.py|initiate_send|211] [/opt/zope/Zope-2.0.1/ZServer/medusa/http_server.py|send|394] [/opt/zope/Zope-2.0.1/ZServer/medusa/asyncore.py|send|237]) 918
Did somebody bad experiences with this ZServer?
I do get the above message occasionally but ZServer does not crash. It should just discard the offending channel. In any case if the -Z option does not work for you might like to try my Zsupervisor package. It works for me ok on Linux and has some add on features. Ican email it to you if you want. Pavlos
participants (2)
-
Francois Chalaoux -
Pavlos Christoforou