Hello List, Zserver stopped responding the other day. The only relevent errors I can find are in the zeo.log, and the event.log zeo.log: 2005-03-07T05:33:53 ERROR(200) zrpc-conn:127.0.0.1:41661 Error caught in asyncore Traceback (most recent call last): File "/home/isarda-s/zope/273/lib/python/ThreadedAsync/LoopCallback.py", line 120, in poll File "/home/isarda-s/Python-2.3.4//lib/python2.3/asyncore.py", line 390, in handle_read_event self.handle_read() File "/home/isarda-s/zope/273/lib/python/ZEO/zrpc/smac.py", line 145, in handle_read File "/home/isarda-s/Python-2.3.4//lib/python2.3/asyncore.py", line 356, in recv raise socket.error, why error: (110, 'Connection timed out') event.log: 2005-03-07T05:01:57 ERROR(200) zrpc-conn:localhost:9999 Error caught in asyncore Traceback (most recent call last): File "/home/isarda-s/Python-2.3.4//lib/python2.3/asyncore.py", line 69, in read obj.handle_read_event() File "/home/isarda-s/Python-2.3.4//lib/python2.3/asyncore.py", line 390, in handle_read_event self.handle_read() File "/home/isarda-s/zope/273/lib/python/ZEO/zrpc/smac.py", line 145, in handle_read File "/home/isarda-s/Python-2.3.4//lib/python2.3/asyncore.py", line 356, in recv raise socket.error, why error: (9, 'Bad file descriptor') Zope runs behind apache using zeo as filestorage. I tried restarting zope and zeo, and still the nothing from zserver. We ended up restarting the machine and it started working again, but I'd like to get to the bottom of what caused the downtime. The machine had been up for 6 months before this happened and everything had been running smoothly prior to this issue. There was an issue with an apache log growing too large (2GB limit) but I don't think this would effect zope. Here's the specs: Zope 2.7.3-0 python 2.3.4 Plone 1.1 (yeah, its old) -- Darian Schramm darian at abstractedge dot com