[Zope] FCGI server uncaptured python exception ...
Albert Ting
alt@artisan.com
Wed, 26 Jun 2002 15:51:15 -0700
I was perusing some old email messages. Seems like FCGI-server needs a
similar patch? This is on solaris 2.8, running zope-2.5.1.
Also, is it possible to use both fcgi and proxy server at the same time?
I presume the answer is yes.
2002-06-26T18:05:49 ERROR(200) ZServer uncaptured python exception, closing channel <ZServer.FCGIServer.FCGIServer listening :8005 at 0xcae21c> (exceptions.TypeError:unpack non-sequence [/usr/local/Zope-2.5.1/ZServer/medusa/asyncore.py|poll|94] [/usr/local/Zope-2.5.1/ZServer/medusa/asyncore.py|handle_read_event|385] [/usr/local/Zope-2.5.1/ZServer/FCGIServer.py|handle_accept|636])
------
2002-06-26T18:05:49 PROBLEM(100) ZServer warning: server accept() threw EWOULDBLOCK
Philipp Giere writes:
> From: Philipp Giere <p.giere@hzd.hessen.de>
> To: Chris McDonough <chrism@zope.com>
> CC: zope <zope@zope.org>
> Subject: Re: [Zope] ZServer uncaptured python exception ...
> Date: Fri, 22 Mar 2002 10:23:08 +0100
>
> Hi Chris!
>
> The server is much more stable now.
> It seems that the HTTP and PCGI-Servers need a patch as well. In the
> error below the ZFTPServer disappeared, only the other two servers
> got the error:
>
> 2002-03-22T08:52:26 ERROR(200) ZServer uncaptured python exception,
> closing channel <ZServer.HTTPServer.zhttp_channel connected
> 194.31.184.118:4794 at 0xb2ed44 channel#: 48 requests:>
> (socket.error:(11, 'Resource temporarily unavailable')
> [/opt/Zope-2.5.0-src/ZServer/medusa/asynchat.py|handle_read|82]
> [/opt/Zope-2.5.0-src/ZServer/medusa/http_server.py|recv|423]
> [/opt/Zope-2.5.0-src/ZServer/medusa/asyncore.py|recv|357])
> ------
> 2002-03-22T08:52:26 ERROR(200) ZServer uncaptured python exception,
> closing channel <ZServer.PCGIServer.PCGIServer listening
> '/opt/Zope-2.5.0-src/var/pcgi.soc' at 0x9db364>
> (exceptions.TypeError:unpack non-sequence
> [/opt/Zope-2.5.0-src/ZServer/medusa/asyncore.py|poll|94]
> [/opt/Zope-2.5.0-src/ZServer/medusa/asyncore.py|handle_read_event|385]
> [/opt/Zope-2.5.0-src/ZServer/PCGIServer.py|handle_accept|308])
> ------
> 2002-03-22T08:52:26 PROBLEM(100) ZServer warning: server accept() threw
> EWOULDBLOCK
>
> Thank you!
>
> Philipp
>
>
> Chris McDonough schrieb:
> >
> > Phillipp,
> >
> > Please try applying the following patch and tell us if it makes the problem
> > go away.
> >
> > Thanks!!
> >
> > Index: FTPServer.py
> > ===================================================================
> > RCS file: /cvs-repository/Zope/ZServer/FTPServer.py,v
> > retrieving revision 1.21
> > diff -r1.21 FTPServer.py
> > 621c621,626
> > < conn, addr = self.accept()
> > ---
> > > try:
> > > conn, addr = self.accept()
> > > except TypeError:
> > > # unpack non-sequence as result of accept
> > > # returning None
> > > return
> >
> > ----- Original Message -----
> > From: "Philipp Giere" <p.giere@hzd.hessen.de>
> > To: <zope@zope.org>
> > Sent: Thursday, March 21, 2002 12:55 PM
> > Subject: [Zope] ZServer uncaptured python exception ...
> >
> > > Hi!
> > >
> > > I have big problems running my Zope-2.5.0-src under Solaris 2.7 with
> > > python 2.1.2 (configure --with-thread).
> > > The same problems occur even when I install the binary for
> > > solaris-sparc.
> > >
> > > The Zope Server dies with the following error:
> > >
> > > 2002-03-21T17:40:00 ERROR(200) ZServer uncaptured python exception,
> > > closing channel <ZServer.HTTPServer.zhttp_channel connected
> > > 194.31.184.118:4320 at 0xa7c99c channel#: 30 requests:>
> > > (socket.error:(11, 'Resource temporarily unavailable')
> > > [/opt/Zope-2.5.0-src/ZServer/medusa/asynchat.py|handle_read|82]
> > > [/opt/Zope-2.5.0-src/ZServer/medusa/http_server.py|recv|420]
> > > [/opt/Zope-2.5.0-src/ZServer/medusa/asyncore.py|recv|357])
> > > ------
> > > 2002-03-21T17:40:00 ERROR(200) ZServer uncaptured python exception,
> > > closing channel <ZServer.HTTPServer.zhttp_channel connected
> > > 194.31.184.118:4319 at 0xa7ca64 channel#: 29 requests:>
> > > (socket.error:(11, 'Resource temporarily unavailable')
> > > [/opt/Zope-2.5.0-src/ZServer/medusa/asynchat.py|handle_read|82]
> > > [/opt/Zope-2.5.0-src/ZServer/medusa/http_server.py|recv|420]
> > > [/opt/Zope-2.5.0-src/ZServer/medusa/asyncore.py|recv|357])
> > > ------
> > > 2002-03-21T17:40:00 ERROR(200) ZServer uncaptured python exception,
> > > closing channel <ZServer.FTPServer.FTPServer listening :8021 at
> > > 0xb0490c> (exceptions.TypeError:unpack non-sequence
> > > [/opt/Zope-2.5.0-src/ZServer/medusa/asyncore.py|poll|94]
> > > [/opt/Zope-2.5.0-src/ZServer/medusa/asyncore.py|handle_read_event|385]
> > > [/opt/Zope-2.5.0-src/ZServer/FTPServer.py|handle_accept|621])
> > > ------
> > > 2002-03-21T17:40:00 PROBLEM(100) ZServer warning: server accept() threw
> > > EWOULDBLOCK
> > >
> > > The Startscript:
> > >
> > > #! /bin/sh
> > >
> > LD_LIBRARY_PATH=/opt/oracle/8.1.7/lib:/usr/lib:/usr/openwin/lib:/opt/SUNWmot
> > if/l
> > >
> > ib:/opt/SUNWspro/lib:/opt/lib:/opt/gissw/ArcIMS3.1/aims31exe/lib:/opt/gissw/
> > ArcI
> > > MS3.1/aims31exe/bin:/opt/lib/python2.1
> > > ORACLE_BASE=/opt/oracle
> > > ORACLE_HOME=/opt/oracle/8.1.7
> > > ORACLE_SID=sun01
> > > NLS_LANG=GERMAN_GERMANY.WE8ISO8859P1
> > > ORA_NLS33=/opt/oracle/8.1.7/ocommon/nls/admin/data
> > > export ORACLE_BASE ORACLE_HOME ORACLE_SID NLS_LANG ORA_NLS33
> > > LD_LIBRARY_PATH
> > > reldir=`dirname $0`
> > > INST_HOME=`cd $reldir; pwd`
> > > echo ""
> > > echo ""
> > > echo "Starting Zope Server in $INST_HOME ..."
> > > echo ""
> > > echo ""
> > > export INST_HOME
> > > exec /opt/bin/python \
> > > $INST_HOME/z2.py \
> > > -D "$@"
> > >
> > >
> > > Somebody out there with an idea??
> > >
> > > Thank you!
> > > Philipp
> > >
> > > _______________________________________________
> > > 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 )
> > >
>
> --
> Philipp Giere, uib
> BSZ Umweltressort Hessen
> Tel.: +49 611 340 616
> Fax.: +49 611 340 663
>