I set t -2 yesterday arvo after what seemed like blissful stability with t -1 crashed this morning under almost zero load - after a 3 hour period of inactivity, when I opened up the management screen. sigh... Houston, we have a serious problem here which seems to go away when we run a single thread. Unfortunately, a single threaded zope is not much use to us here.... ------ 2000-03-31T00:24:22 ERROR(200) zdaemon zdaemon: Fri Mar 31 10:24:22 2000: Aiieee! 5589 exited with error code: 11 ------ 2000-03-31T00:24:22 INFO(0) zdaemon zdaemon: Fri Mar 31 10:24:22 2000: Houston, we have forked ------ 2000-03-31T00:24:22 INFO(0) zdaemon zdaemon: Fri Mar 31 10:24:22 2000: Hi, I just forked off a kid: 7344 ------ 2000-03-31T00:24:22 INFO(0) zdaemon zdaemon: Fri Mar 31 10:24:22 2000: Houston, we have forked ------ 2000-03-31T00:24:31 ERROR(200) zdaemon zdaemon: Fri Mar 31 10:24:31 2000: Aiieee! 7344 exited with error code: 256 ------ Michel Pelletier wrote:
"Dr. Ross Lazarus" wrote:
We're running with a single thread here.
30 hours, no crash yet....
Single threaded operation is noticably sluggish - in fact it just stops if someone starts a long task) but at least it seems stable....
Starting to look like a thread problem for linux zopes ?
I think it's a thread problem but not anything linux related, or at least I'd need to see proof of that.
Wait another day, and try -t 2. See what happens.
-Michel
-- Dr Ross Lazarus Associate Professor and Sub-Dean for Information Technology Faculty of Medicine, Room 126A, A27, University of Sydney, Camperdown, NSW 2006, Australia Tel: (+61 2) 93514429 Mobile: +61414872482 Fax: (+61 2) 93516646 Email: rossl@med.usyd.edu.au