[Zope] zope_msg.log Message

Kevin Littlejohn Kevin Littlejohn <darius@connect.com.au>
Tue, 21 Mar 2000 11:20:22 +1100


Just to add my two cents:  I've seen these as well, usually connected to
someone disconnecting from downloading a page mid-way, usually also
connected to zope going into a really tight 'select (0,1), select (0,1,2),
select (0,1,2,3), select(0,1,2,3,4), etc loop - until it runs out of fd's
it's allowed to open, crashes, and needs restarting.  Oh, and only when
running with FastCGI.

Redhat 6.1ish, glibc from rpm glibc-2.1.2-15, python 1.5.2 from rpm
python-1.5.2-7, apache from rpm apache-1.3.9-8.

My response so far has been to whack a while : ; do ... done loop around
the kickoff command in ./start, and run the whole lot under screen -dmS.
STUPID_LOG_FILE didn't produce anything that was immediately useful to me
:(

I've just upgraded to 2.1.6, and so far I haven't seen the problem, which
may or may not be a good sign ;)

KevinL

>>> Tres Seaver wrote
> Tony Rossignol wrote:
> > 
> > Tres Seaver wrote:
> > >
> > > Tony Rossignol <tonyr@ep.newtimes.com>
> > > >
> > > > Does anyone have any insite into what this error message might be?
> > > >
> > > > 2000-03-20T06:36:51 ERROR(200) ZServer uncaptured python exception,
> > > > closing channel <FCGIChannel connected 206.138.64.10:1819 at 10c1b2f0>
> > > >  (socket.error:(32, 'Broken pipe')
> > > > [/usr/local/Zope-2.1.4-NT-0.1.6/ZServer/medusa/asynchat.py|initiate_sen
d|211]
> > > > [/usr/local/Zope-2.1.4-NT
> > > > -0.1.6/ZServer/medusa/asyncore.py|send|237])
> > > > ------
> > > > 2000-03-20T06:36:51 ERROR(200) ZServer uncaptured python exception,
> > > > closing channel <FCGIChannel connected 206.138.64.10:1819 at 10c1b2f0>
> > > >  (socket.error:(32, 'Broken pipe')
> > > > [/usr/local/Zope-2.1.4-NT-0.1.6/ZServer/medusa/asynchat.py|initiate_sen
d|211]
> > > > [/usr/local/Zope-2.1.4-NT
> > > > -0.1.6/ZServer/medusa/asyncore.py|send|237])
> > > > ------
> > > >

[snip]