flup error

[Alex K]

Hi Guys,

From time to time I get the following error:

Unhandled exception in thread started by <bound method Request.run of
<flup.server.fcgi_base.Request object at 0xb473a58c>>
Traceback (most recent call last):
File "/var/lib/python-support/python2.4/flup/server/fcgi_base.py",
line 570, in run
self._flush()
File "/var/lib/python-support/python2.4/flup/server/fcgi_base.py",
line 577, in _flush
self.stdout.close()
File "/var/lib/python-support/python2.4/flup/server/fcgi_base.py",
line 336, in close
self._conn.writeRecord(rec)
File "/var/lib/python-support/python2.4/flup/server/fcgi_base.py",
line 831, in writeRecord
rec.write(self._sock)
File "/var/lib/python-support/python2.4/flup/server/fcgi_base.py",
line 530, in write
self._sendall(sock, header)
File "/var/lib/python-support/python2.4/flup/server/fcgi_base.py",
line 507, in _sendall
sent = sock.send(data)
socket.error: (32, 'Broken pipe')

Did anyone get a similar error? Would anyone know what might be wrong
with my configuration? It's not crashing the server.

Thank you so much,

Alex

[Brendan W. McAdams]

I'm probably not the best person to answer as my web.py apps aren't in
in production yet but I'm assuming you're seeing this in your log?

" socket.error: (32, 'Broken pipe')" typically indicates that the
remote connection has closed and you tried to write data to the closed
socket. E.g. their browser disconnected. Unfortunately since it's a
stateless connection the webserver typically doesn't find out until it
tries to write. If you're seeing these in your logs, it's probably
indicative of that. I say "if you're seeing it in your logs" because
it's probably a separate issue if you're surfing the site yourself and
getting back broken pipe errors.