On Wed, 2002-01-30 at 03:43, Terry Kerr wrote:
[...]
2002-01-30T02:02:02 ERROR(200) ZServer uncaptured python exception, closing channel <zhttp_channel connected 24.237.103.242:4496 at 8a2b88c channel#: 5927 requests:> (exceptions.AttributeError:'None' object has no attribute 'split' [/usr/local/lib/python2.1/asyncore.py|poll|104] [/usr/local/lib/python2.1/asyncore.py|handle_write_event|393] [/usr/local/zope/Zope-2.4.3-src/ZServer/medusa/asynchat.py|handle_write|147] [/usr/local/zope/Zope-2.4.3-src/ZServer/medusa/asynchat.py|initiate_send|209] [/usr/local/zope/Zope-2.4.3-src/ZServer/medusa/asynchat.py|refill_buffer|196] [/usr/local/zope/Zope-2.4.3-src/ZServer/Producers.py|more|108] [/usr/local/zope/Zope-2.4.3-src/ZServer/medusa/http_server.py|log|287]) ------ 2002-01-30T02:02:03 ERROR(200) zdaemon zdaemon: Wed Jan 30 13:02:03 2002: Aiieee! 21875 exited with error code: 256
I don't know why your webserver might be crashing, but I do know that 'exited with error code: 256' usually means that the Zope process exited normally with ERRORLEVEL 1, for instance, if it called sys.exit(1). One of the places this happens is when you restart the Zope process thru the Control_Panel. -- Ideas don't stay in some minds very long because they don't like solitary confinement.