mysterious dying server!

[GoogleCodeExporter]

silouan$ aspen
launching child process
starting child server
aspen starting on ('0.0.0.0', 8080)
cleaning up after critical exception:
Traceback (most recent call last):
  File "/home/whit537/lib/python/aspen/__init__.py", line 221, in start_server
    server.start()
  File "/home/whit537/lib/python/aspen/wsgiserver.py", line 870, in start
    self.tick()
  File "/home/whit537/lib/python/aspen/__init__.py", line 166, in tick
    Server.tick(server)
  File "/home/whit537/lib/python/aspen/wsgiserver.py", line 897, in tick
    s, addr = self.socket.accept()
  File "/usr/local/lib/python2.5/socket.py", line 167, in accept
    sock, addr = self._sock.accept()
error: (53, 'Software caused connection abort')

shutting down

Original issue reported on code.google.com by whit537@gmail.com on 8 Aug 2007 at 7:08

[GoogleCodeExporter]

Further info:

http://www.google.com/search?q=error%3A+%2853%2C+%27Software+caused+connection+a
bort%27%29
http://www.cherrypy.org/ticket/686
http://twistedmatrix.com/trac/ticket/1274

Original comment by whit537@gmail.com on 28 Aug 2007 at 1:22

[GoogleCodeExporter]

Original comment by whit537@gmail.com on 29 Oct 2007 at 3:21

• Added labels: Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

In r243 on the trunk, I tweaked the try-except around server.start() in
aspen/__init__.py so that it swallows all exceptions except SystemExit. This 
should
cover all socket errors that _cpwsgiserver doesn't swallow, plus whatever else 
life
might throw at us.

Original comment by whit537@gmail.com on 30 Oct 2007 at 1:23

• Changed state: Closed
• Removed labels: Type-Defect