[Tilecache] Broken Pipe

[Christopher Schmidt]

On Tue, Mar 24, 2009 at 04:19:29PM +0100, Stephan Holl wrote:
> Hi TileCache-users,
> 
> I just evaluated TileCache for a project and found the following error
> messages in my shell where I started the tilecache_http_server:
> 
> Cache hit:
> 3329653.23092,5797715.44339,3338684.33715,5806746.54962, Tile: x: 21,
> y: 23, z: 3, time: 0.000220060348511, debug: True Traceback (most
> recent call last): File "/usr/lib/python2.5/wsgiref/handlers.py", line
> 93, in run self.finish_response() File
> 	"/usr/lib/python2.5/wsgiref/handlers.py", line 134, in
> 	finish_response self.write(data) File
> 	"/usr/lib/python2.5/wsgiref/handlers.py", line 217, in write
> 	self.send_headers() File
> 	"/usr/lib/python2.5/wsgiref/handlers.py", line 273, in
> 	send_headers self.send_preamble() File
> 	"/usr/lib/python2.5/wsgiref/handlers.py", line 199, in
> 	send_preamble 'Date: %s\r\n' % format_date_time(time.time())
> 	File "/usr/lib/python2.5/socket.py", line 274, in write
> 	self.flush() File "/usr/lib/python2.5/socket.py", line 261, in
> 	flush self._sock.sendall(buffer)
> error: (32, 'Broken pipe')
> Cache hit: 3329653.23092,5788684.33715,3338684.33715,5797715.44339,
> 	Tile: x: 21, y: 22, z: 3, time: 0.000218868255615, debug: True
> 	Traceback (most recent call last): File
> 	"/usr/lib/python2.5/wsgiref/handlers.py", line 93, in run
> 	self.finish_response() File
> 	"/usr/lib/python2.5/wsgiref/handlers.py", line 134, in
> 	finish_response self.write(data) File
> 	"/usr/lib/python2.5/wsgiref/handlers.py", line 217, in write
> 	self.send_headers() File
> 	"/usr/lib/python2.5/wsgiref/handlers.py", line 273, in
> 	send_headers self.send_preamble() File
> 	"/usr/lib/python2.5/wsgiref/handlers.py", line 199, in
> 	send_preamble 'Date: %s\r\n' % format_date_time(time.time())
> 	File "/usr/lib/python2.5/socket.py", line 274, in write
> 	self.flush() File "/usr/lib/python2.5/socket.py", line 261, in
> 	flush self._sock.sendall(buffer)
> error: (32, 'Broken pipe')
> 
> This mostly appears when accessing a not-yet-requested tile. Basically
> tilecache works as expected, so I assume I can ignore the logs?

This is in an indication that the remote client did not finish loading
the data, but instead broke off in mid-connection. This is common when a
user zooms before tiles are completely finished loading, and since
not-yet-cached tiles take longer to load, they are more likely to cause
the symptom. However, it si not a problem to worry about, you are
correct.

> My installation:
> * Debian Lenny stock-installation
> * TileCache (2.03 from Lenny) running as a standalone-server using
>   tilecache_http_server_server.
> * Disc-Cache
> * WMS-Server to Cache.
> 
> Thanks for any pointers.
> 
> 	Stephan



> _______________________________________________
> Tilecache mailing list
> Tilecache at openlayers.org
> http://openlayers.org/mailman/listinfo/tilecache


-- 
Christopher Schmidt
MetaCarta