[Zope] Re: zope_msg.log Message

[Dr. Ross Lazarus]

Made no difference here either.

In desperation, I moved the server behind an apache using fastcgi. Same
problem persists...random crashes with aaiiieee 11 and 256 in the debug
log, often with core dumps.

May be time to move away from the Lintel box (stock redhat 6.1, 2.16 src
install, pII350, 256mB ram) - I don't see this on a sun box I'm also
running.

Does this happen with binary installs ? Is it just redhat 6.1 (we didn't
see this on 5.2!)? One problem is that the zmonitor usually works - the
server restarts itself and users may only notice a long delay. I see it
because I'm watching the logs anxiously.

jon prettyman <jprettyma-@acm.org> wrote: 
original article:http://www.egroups.com/group/zope/?start=27180
> Setting DEBUG to 1 had no affect on my server.  Crashed within 15
> minutes of setting it.
> 
> -Jon
> 
> Pavlos Christoforou <pavlos@gaaros.com> writes:
> 
> > On Fri, 24 Mar 2000, Michel Pelletier wrote:
> > 
> > > 
> > > > As soon as I'm able to collect more info I'll forward it to you.  Is
> > > > there anywhere else I should be posting this information?
> > > 
> > > The list.  just keep ccing me.
> > > 
> > 
> > Some good news at last ...
> > 
> > When I set DEBUG in asyncore.py to 1 so I could view the lists going into
> > select, ZServer stabilised and hasn't crashed since. Smells like a race
> > condition and somehow the extra time it takes to print the list contents
> > stabilises things.

-- 

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