Ron Bickers writes:
Besides the problem that Zope crashes every once in a while (it could be days it could be many weeks) for no apparent reason, it won't restart itself. I get the following in the stupid log. It just keeps trying as fast as it can until I kill it.
2001-11-05T20:18:55 ERROR(200) zdaemon zdaemon: Mon Nov 5 15:18:55 2001: Aiieee! 32529 exited with error code: 256 ------ 2001-11-05T20:18:55 INFO(0) zdaemon zdaemon: Mon Nov 5 15:18:55 2001: Houston, we have forked ------ 2001-11-05T20:18:55 INFO(0) zdaemon zdaemon: Mon Nov 5 15:18:55 2001: Hi, I just forked off a kid: 32533 ------ 2001-11-05T20:18:55 INFO(0) zdaemon zdaemon: Mon Nov 5 15:18:55 2001: Houston, we have forked ------ 2001-11-05T20:18:55 ERROR(200) zdaemon zdaemon: Mon Nov 5 15:18:55 2001: Aiieee! 32533 exited with error code: 256 "error code: 256" means "exit(1)". Some component in your Zope system calls this...
Seems to be quite an old Zope because some time ago (I think for 2.2.2 or 2.2.3) changes have been made to prevent a restart when a start/restart immediately failed. Dieter