[Tilecache] Connection reset by peer error

Steven M. Ottens steven at minst.net
Mon Dec 22 09:16:56 EST 2008 

Hi all,

I've configured tilecache to use amazons S3 as cache backend and I've  
got 150+ layers configured. I want to seed them all up to a specific  
zoomlevel. So I created a shell script to call tilecache_seed for all  
layers. However every now and then tilecache_seed.py fails with one  
of the errors below. The exact reason why they fail do not matter for  
me, I just want tilecache_seed to either continue or retry. Is there  
a way to do that, other than calling tilecache_seed again after a  
failed attempt?

(the errors:)

  File "/var/lib/python-support/python2.5/TileCache/Caches/S3.py",  
line 278, in _make_request
     resp = connection.getresponse()
   File "/usr/lib/python2.5/httplib.py", line 928, in getresponse
     response.begin()
   File "/usr/lib/python2.5/httplib.py", line 385, in begin
     version, status, reason = self._read_status()
   File "/usr/lib/python2.5/httplib.py", line 343, in _read_status
     line = self.fp.readline()
   File "/usr/lib/python2.5/httplib.py", line 1047, in readline
     s = self._read()
   File "/usr/lib/python2.5/httplib.py", line 1003, in _read
     buf = self._ssl.read(self._bufsize)
socket.error: (104, 'Connection reset by peer')

  File "/var/lib/python-support/python2.5/TileCache/Client.py", line  
54, in fetch
     response = self.client.open(urlrequest)
   File "/usr/lib/python2.5/urllib2.py", line 387, in open
     response = meth(req, response)
   File "/usr/lib/python2.5/urllib2.py", line 498, in http_response
     'http', request, response, code, msg, hdrs)
   File "/usr/lib/python2.5/urllib2.py", line 425, in error
     return self._call_chain(*args)
   File "/usr/lib/python2.5/urllib2.py", line 360, in _call_chain
     result = func(*args)
   File "/usr/lib/python2.5/urllib2.py", line 506, in http_error_default
     raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
urllib2.HTTPError: HTTP Error 502: Proxy Error


On Dec 5, 2008, at 12:36 PM, riteshambastha wrote:

>
> Yeah, this may happen when the server where the tiles are residing  
> is down. I
> guess, the machine on which your tiles are kept is a different  
> machine.
>
> Regards,
> Ritesh
>
> lukast wrote:
>>
>> Thanks,
>> But this bug also occurs when tile is already cached by tilecache  
>> - seems
>> as if it's OpenLayers that resets connection ?:( See the attachement.
>> tilecache_error.JPG
>>
>> Thanks for help.
>>
>>
>>
>> riteshambastha wrote:
>>>
>>> Very obvious that this is a WMS server error. Connection closed  
>>> by peer
>>> means that the server is disconnected, and hence is throwing  
>>> errors to
>>> the client. If openlayers is unable to connect to the wms server,  
>>> this
>>> error has to come.
>>>
>>> Regards,
>>> Ritesh
>>>
>>> lukast wrote:
>>>>
>>>> Any ideas ?
>>>> This bug also occurs when tile is already cached by tilecache -  
>>>> seems as
>>>> if it's OpenLayers that resets connection ?:( See the attachement.
>>>>  http://www.nabble.com/file/p20851604/tilecache_error.JPG
>>>> tilecache_error.JPG
>>>>
>>>> Thanks for any help.
>>>>
>>>>
>>>> lukast wrote:
>>>>>
>>>>> Hello,
>>>>>
>>>>> I have got problem with TileCache 2.04. Sometimes (not always) it
>>>>> generates errors when OpenLayers asks for tiles that are not  
>>>>> cached
>>>>> already by TileCache and, as a result, it must ask WMS Server  
>>>>> for tile.
>>>>> My question is if it OpenLayers or WMS server resets the  
>>>>> connection ?
>>>>> And hot to fix it ?. Below, you can see the logs. Appreciate  
>>>>> your help.
>>>>>
>>>>> Best regards,
>>>>> lukast
>>>>>
>>>>> Cache miss: 487750.0,464500.0,488000.0,464750.0, Tile: x: 2575, y:
>>>>> 2554, z: 10, time: 0.0494420528412
>>>>> Traceback (most recent call last):
>>>>>   File
>>>>> "/usr/lib/python2.4/site-packages/wsgiref-0.1.2-py2.4.egg/ 
>>>>> wsgiref/handlers.py",
>>>>> line 93, in run
>>>>>   File
>>>>> "/usr/lib/python2.4/site-packages/wsgiref-0.1.2-py2.4.egg/ 
>>>>> wsgiref/handlers.py",
>>>>> line 134, in finish_response
>>>>>   File
>>>>> "/usr/lib/python2.4/site-packages/wsgiref-0.1.2-py2.4.egg/ 
>>>>> wsgiref/handlers.py",
>>>>> line 217, in write
>>>>>   File
>>>>> "/usr/lib/python2.4/site-packages/wsgiref-0.1.2-py2.4.egg/ 
>>>>> wsgiref/handlers.py",
>>>>> line 273, in send_headers
>>>>>   File
>>>>> "/usr/lib/python2.4/site-packages/wsgiref-0.1.2-py2.4.egg/ 
>>>>> wsgiref/handlers.py",
>>>>> line 196, in send_preamble
>>>>>   File
>>>>> "/usr/lib/python2.4/site-packages/wsgiref-0.1.2-py2.4.egg/ 
>>>>> wsgiref/handlers.py",
>>>>> line 403, in _write
>>>>>   File "/usr/lib64/python2.4/socket.py", line 248, in write
>>>>>     self.flush()
>>>>>   File "/usr/lib64/python2.4/socket.py", line 235, in flush
>>>>>     self._sock.sendall(buffer)
>>>>> error: (104, 'Connection reset by peer')
>>>>> Cache miss: 488000.0,464500.0,488250.0,464750.0, Tile: x: 2576, y:
>>>>> 2554, z: 10, time: 0.0464081764221
>>>>> Traceback (most recent call last):
>>>>>   File
>>>>> "/usr/lib/python2.4/site-packages/wsgiref-0.1.2-py2.4.egg/ 
>>>>> wsgiref/handlers.py",
>>>>> line 93, in run
>>>>>   File
>>>>> "/usr/lib/python2.4/site-packages/wsgiref-0.1.2-py2.4.egg/ 
>>>>> wsgiref/handlers.py",
>>>>> line 134, in finish_response
>>>>>   File
>>>>> "/usr/lib/python2.4/site-packages/wsgiref-0.1.2-py2.4.egg/ 
>>>>> wsgiref/handlers.py",
>>>>> line 217, in write
>>>>>   File
>>>>> "/usr/lib/python2.4/site-packages/wsgiref-0.1.2-py2.4.egg/ 
>>>>> wsgiref/handlers.py",
>>>>> line 273, in send_headers
>>>>>   File
>>>>> "/usr/lib/python2.4/site-packages/wsgiref-0.1.2-py2.4.egg/ 
>>>>> wsgiref/handlers.py",
>>>>> line 196, in send_preamble
>>>>>   File
>>>>> "/usr/lib/python2.4/site-packages/wsgiref-0.1.2-py2.4.egg/ 
>>>>> wsgiref/handlers.py",
>>>>> line 403, in _write
>>>>>   File "/usr/lib64/python2.4/socket.py", line 248, in write
>>>>>     self.flush()
>>>>>   File "/usr/lib64/python2.4/socket.py", line 235, in flush
>>>>>     self._sock.sendall(buffer)
>>>>> error: (104, 'Connection reset by peer')
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
> -- 
> View this message in context: http://www.nabble.com/Connection- 
> reset-by-peer-error-tp20832215p20852132.html
> Sent from the TileCache mailing list archive at Nabble.com.
>
> _______________________________________________
> Tilecache mailing list
> Tilecache at openlayers.org
> http://openlayers.org/mailman/listinfo/tilecache

More information about the Tilecache mailing list