On 07-nov-08, at 22:00, Pascal Hartig wrote: > Tried this before. I thought it's not very informative. After start: > >> Cherokee Web Server 0.11.0 (Nov 7 2008): Listening on port 9090, >> TLS disabled, >> IPv6 disabled, using epoll, 1024 fds system limit, max. 505 >> connections, >> single thread > > This output appears after the first connect and the 503: > >> Server 0.11.0 running.. PID=9113 Port=4000 > > After the second and subsequent connects: > >> Traceback (most recent call last): >> File "/usr/share/cherokee/admin/server.py", line 208, in <module> >> main() >> File "/usr/share/cherokee/admin/server.py", line 189, in main >> srv = pyscgi.ServerFactory (True, handler_class=Handler, >> host="127.0.0.1", port=scgi_port) >> File "/usr/share/cherokee/admin/pyscgi.py", line 154, in >> ServerFactory >> return SCGIServer(*args, **kargs) >> File "/usr/share/cherokee/admin/pyscgi.py", line 144, in __init__ >> SocketServer.ThreadingTCPServer.__init__ (self, (host, port), >> handler_class) >> File "/usr/lib64/python2.5/SocketServer.py", line 330, in __init__ >> self.server_bind() >> File "/usr/lib64/python2.5/SocketServer.py", line 341, in >> server_bind >> self.socket.bind(self.server_address) >> File "<string>", line 1, in bind >> socket.error: (98, 'Address already in use')
This issue is puzzling me, actually. It looks like if the first Python interpreter crashed or something, and the subsequent interpreters couldn't reopen the port because it hadn't timed out. :-mm By the way, there is something that has just come across my mind. Your DomU does have a 'lo' interface plumbed, up and configured as local loop, right? (just to be sure). -- Octality http://www.octality.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
