[Zope] zope_msg.log Message

[Tony Rossignol]

Michel Pelletier wrote:

> The problem with 2) is that no one can reproduce it reliably (this may
> not be true after I look at something someone sent me today, I'll keep
> everyone updated) including myself.  I have pounded a half dozen
> sandboxes with ab for hours and gotten nowhere.  No crashes.  Not a
> single burp.
>
We have very erratic crashes, the only commonality we can find is
volume.  When requests are low the system is awesome, but once load
starts increasing we see frequent restarts, once an hour at least.  This
could be due to people experience slower response times and breaking the
connection to attempt a reload.  From what someother people have been
saying a 'broken pipe' error in zope_msg.log may cause all the threads
to die off.  The problem here is I generated 30-40 'broken pipe' errors
and could not crash Zope.

When you run ab against it are you hitting a wide variety of objects or
the same page over and over.  I've had Zope perform great accessing the
same page repeatedly but show some strain once you vary it's diet a bit
especially when cached SQL results are involved.

What server method are you using on the sandboxes.  We use a combination
of ZServer and FastCGI connections for our traffic, with all /manage
going through FastCGI and the actual public traffic using a mix of
FastCGI & ZServer.

> 
> bash$ strace -f -e trace=none -signal=all python z2.py -D
> 
I can't get this to work.  When I try it all the messages come on the
screen like they should, each service that is up etc, but the darn thing
will not answer requests.  As soon as I run the exact same command w/o
strace it works.  I've also tried to attach strace directly to the
already running processes, and no luck.

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?



-- 
-------------------------------
tonyr@ep.newtimes.com
Director of Web Technology
New Times, Inc.
-------------------------------