[Tilecache] Connection reset by peer error

lukast lukast at poczta.fm
Tue Jan 13 06:10:22 EST 2009


Thanks for help !

I have updated python to version 2.6 but the problem still exists - after
one day server stopped responding :( I have noticed that "Connection
timeout" error occured juts before it stopped responding. 

Last logs:

Cache hit: 532000.0,354000.0,548000.0,370000.0, Tile: x: 43, y: 33, z: 4,
time: 0.00884294509888, debug: True
Traceback (most recent call last):
  File "/usr/local/lib/python2.6/wsgiref/handlers.py", line 94, in run
    self.finish_response()
  File "/usr/local/lib/python2.6/wsgiref/handlers.py", line 135, in
finish_response
    self.write(data)
  File "/usr/local/lib/python2.6/wsgiref/handlers.py", line 223, in write
    self._write(data)
  File "/usr/local/lib/python2.6/socket.py", line 297, in write
    self.flush()
  File "/usr/local/lib/python2.6/socket.py", line 284, in flush
    self._sock.sendall(buffer)
error: [Errno 110] Connection timed out
Cache hit: 468000.0,290000.0,484000.0,306000.0, Tile: x: 39, y: 29, z: 4,
time: 0.00954103469849, debug: True

Appreciate your help.
Best regards,
lukast 



Christopher Schmidt-2 wrote:
> 
> On Fri, Jan 02, 2009 at 06:12:36AM -0800, lukast wrote:
>> 
>> I am still trying to resolve this problem...
>> I have noticed that the problem occurs ('connection reset by peer'
>> exception') also when tile is already cached by tilecache, so I think
>> that
>> it is not the problem with WMS server...(when tile is cached tilecache
>> does
>> not connect WMS server). 
> 
> Connection reset by peer messages are relatively standard; they are a
> sign that the user zoomed (and therefore the browser stopped requestin
> the tile) before the server finished sending it.
> 
> I do not think thisi s related to the BaseHTTPServer locking up, but
> there have ben a number of improvements over the years in the
> BaseHTTPServer in Python, and you're currently using a version that's 4
> years old. You might consider upgrading Python as a possibility.
> 
>> So, my conclusion is that it is rather problem with connection between IE
>> and tilecache. I am using tilecache by launching
>> 'tilecache_http_server.py'
>> script. Exceptions like 'connection reset by peer' occur from time to
>> time
>> and, after a week or two tilecache stops responding at all and needs to
>> be
>> restarted. Below is the log... Any sugestions ? I am loosing my mind...
>> :(
>> PS: adresses such as 10.97.88.39  are adresses of clients requesting
>> tiles
>> from tilecache..
>> 
>> Exception happened during processing of request from ('10.97.88.39',
>> 1153)
>> ----------------------------------------
>> ----------------------------------------
>> Exception happened during processing of request from ('10.97.88.39',
>> 1468)
>> ----------------------------------------
>> ----------------------------------------
>> Exception happened during processing of request from ('10.100.10.5',
>> 1886)
>> ----------------------------------------
>> ----------------------------------------
>> Exception happened during processing of request from ('10.97.12.7', 2833)
>> ----------------------------------------
>> ----------------------------------------
>> Exception happened during processing of request from ('126.66.54.179',
>> 3560)
>> ----------------------------------------
>> ----------------------------------------
>> Exception happened during processing of request from ('126.66.54.179',
>> 3781)
>> ----------------------------------------
>> ----------------------------------------
>> Exception happened during processing of request from ('126.66.54.179',
>> 4609)
>> ----------------------------------------
>> ----------------------------------------
>> Exception happened during processing of request from ('126.66.54.179',
>> 1053)
>> ----------------------------------------
>> ----------------------------------------
>> Exception happened during processing of request from ('126.66.52.203',
>> 4714)
>> ----------------------------------------
>> ----------------------------------------
>> Exception happened during processing of request from ('126.66.52.203',
>> 4713)
>> ----------------------------------------
>> ----------------------------------------
>> Exception happened during processing of request from ('126.66.52.203',
>> 4811)
>> ----------------------------------------
>> ----------------------------------------
>> Exception happened during processing of request from ('10.100.2.1', 1982)
>> ----------------------------------------
>> ----------------------------------------
>> Exception happened during processing of request from ('10.100.2.1', 1991)
>> ----------------------------------------
>> ----------------------------------------
>> Exception happened during processing of request from ('10.97.88.4', 1195)
>> ----------------------------------------
>> ----------------------------------------
>> Exception happened during processing of request from ('10.101.4.3', 2728)
>> ----------------------------------------
>> ----------------------------------------
>> Exception happened during processing of request from ('126.66.52.244',
>> 2046)
>> ----------------------------------------
>> ----------------------------------------
>> Exception happened during processing of request from ('126.66.52.244',
>> 2367)
>> ----------------------------------------
>> ----------------------------------------
>> Exception happened during processing of request from ('126.66.52.244',
>> 2368)
>> ----------------------------------------
>> ----------------------------------------
>> Exception happened during processing of request from ('126.66.52.244',
>> 2369)
>> ----------------------------------------
>> ----------------------------------------
>> Exception happened during processing of request from ('126.66.52.244',
>> 2370)
>> ----------------------------------------
>> ----------------------------------------
>> Exception happened during processing of request from ('126.66.52.244',
>> 2371)
>> ----------------------------------------
>> ----------------------------------------
>> Exception happened during processing of request from ('126.66.52.244',
>> 2372)
>> ----------------------------------------
>> ----------------------------------------
>> Exception happened during processing of request from ('126.66.52.244',
>> 2373)
>> ----------------------------------------
>> ----------------------------------------
>> Exception happened during processing of request from ('126.66.52.244',
>> 2374)
>> ----------------------------------------
>> ----------------------------------------
>> Exception happened during processing of request from ('126.66.52.244',
>> 2375)
>> ----------------------------------------
>> ----------------------------------------
>> Exception happened during processing of rTraceback (most recent call
>> last):
>>   File "/usr/lib64/python2.3/SocketServer.py", line 222, in
>> handle_request
>>     self.process_request(request, client_address)
>>   File "/usr/lib64/python2.3/SocketServer.py", line 241, in
>> process_request
>>     self.finish_request(request, client_address)
>>   File "/usr/lib64/python2.3/SocketServer.py", line 254, in
>> finish_request
>>     self.RequestHandlerClass(request, client_address, self)
>>   File "/usr/lib64/python2.3/SocketServer.py", line 521, in __init__
>>     self.handle()
>>   File
>> "/usr/lib/python2.3/site-packages/wsgiref-0.1.2-py2.3.egg/wsgiref/simple_server.py",
>> line 130, in handle
>>   File "/usr/lib64/python2.3/socket.py", line 338, in readline
>>     data = self._sock.recv(self._rbufsize)
>> error: (104, 'Connection reset by peer')
>> Traceback (most recent call last):
>>   File "/usr/lib64/python2.3/SocketServer.py", line 222, in
>> handle_request
>>     self.process_request(request, client_address)
>>   File "/usr/lib64/python2.3/SocketServer.py", line 241, in
>> process_request
>>     self.finish_request(request, client_address)
>>   File "/usr/lib64/python2.3/SocketServer.py", line 254, in
>> finish_request
>>     self.RequestHandlerClass(request, client_address, self)
>>   File "/usr/lib64/python2.3/SocketServer.py", line 521, in __init__
>>     self.handle()
>>   File
>> "/usr/lib/python2.3/site-packages/wsgiref-0.1.2-py2.3.egg/wsgiref/simple_server.py",
>> line 130, in handle
>>   File "/usr/lib64/python2.3/socket.py", line 338, in readline
>>     data = self._sock.recv(self._rbufsize)
>> error: (104, 'Connection reset by peer')
>> Traceback (most recent call last):
>>   File "/usr/lib64/python2.3/SocketServer.py", line 222, in
>> handle_request
>>     self.process_request(request, client_address)
>>   File "/usr/lib64/python2.3/SocketServer.py", line 241, in
>> process_request
>>     self.finish_request(request, client_address)
>>   File "/usr/lib64/python2.3/SocketServer.py", line 254, in
>> finish_request
>>     self.RequestHandlerClass(request, client_address, self)
>>   File "/usr/lib64/python2.3/SocketServer.py", line 521, in __init__
>>     self.handle()
>>   File
>> "/usr/lib/python2.3/site-packages/wsgiref-0.1.2-py2.3.egg/wsgiref/simple_server.py",
>> line 130, in handle
>>   File "/usr/lib64/python2.3/socket.py", line 338, in readline
>>     data = self._sock.recv(self._rbufsize)
>> error: (104, 'Connection reset by peer')
>> 
>> 
>> 
>> ritesh ambastha 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://n2.nabble.com/Connection-reset-by-peer-error-tp1837757p2101875.html
>> Sent from the TileCache mailing list archive at Nabble.com.
>> 
>> _______________________________________________
>> Tilecache mailing list
>> Tilecache at openlayers.org
>> http://openlayers.org/mailman/listinfo/tilecache
> 
> -- 
> Christopher Schmidt
> MetaCarta
> _______________________________________________
> Tilecache mailing list
> Tilecache at openlayers.org
> http://openlayers.org/mailman/listinfo/tilecache
> 
> 

-- 
View this message in context: http://n2.nabble.com/Connection-reset-by-peer-error-tp1837757p2150647.html
Sent from the TileCache mailing list archive at Nabble.com.




More information about the Tilecache mailing list