Zope not restarting itself after crash
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 When I start Zope (2.4.2), I get warning messages about the use of deprecated modules, so I figured I'd give the following a shot. For some reason, if I change z2.py as follows, it doesn't have problems restarting itself. Coincidence or is there a good explanation? - zdaemon.run(sys.argv, os.path.join(CLIENT_HOME, Zpid)) + zdaemon.run(['-W', 'ignore'] + sys.argv, os.path.join(CLIENT_HOME, Zpid)) _______________________ Ron Bickers Logic Etc, Inc.
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
-----Original Message----- From: Dieter Maurer [mailto:dieter@handshake.de]
Aiieee! 32533 exited with error code: 256 "error code: 256" means "exit(1)". Some component in your Zope system calls this...
Does this mean I should be able to find "exit(1)" somewhere in my Zope code or in a Zope product's code?
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.
It's currently Zope 2.4.1, but if I recall, it happened with 2.3.x as well. I guess the changes didn't work. :-) _______________________ Ron Bickers Logic Etc, Inc.
Ron Bickers writes:
-----Original Message----- From: Dieter Maurer [mailto:dieter@handshake.de]
Aiieee! 32533 exited with error code: 256 "error code: 256" means "exit(1)". Some component in your Zope system calls this...
Does this mean I should be able to find "exit(1)" somewhere in my Zope code or in a Zope product's code? Yes, but it may come from external "C" code (--> database adapter)
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.
It's currently Zope 2.4.1, but if I recall, it happened with 2.3.x as well. I guess the changes didn't work. :-) Indeed, seems so...
Dieter
participants (3)
-
Dieter Maurer -
Ron Bickers -
Ron Bickers