Thanks, This might be the fix. I too had tried ProxyTimeout without success.
It is now behaving a lot better. Dave On Thu, 2006-01-19 at 09:25 +0100, Luca Olivetti wrote: > En/na Jim Fulton ha escrit: > > > It works for a few people. If I try too many people it fails with an > > Error reading from remote server > > message from the Apache. > > > > I cannot find any hints in the apache or zope logs. I have tried to > > monitor the server to see if any resources are running out, but have not > > found anything. > > > > > > Can anyone suggest how I try to diagnose this failure. > > Maybe (just maybe) it's a timeout: I saw this when performing a long > plone migration (though the migration completed anyway). The default > timeout is 5 minutes, so this is easy to rule out: if the error comes > out after five minutes it's probably this error (or less if the apache > configuration uses a lower value). > There are many apache parameters to control the timeout, but IIRC the > only one that worked here is the Timeout parameter (though I'm not sure > it solved my issue, I *do* remember that ProxyTimeout, which seemed the > correct parameter to me, did nothing to prevent the problem). > > http://httpd.apache.org/docs/2.0/mod/core.html#timeout > http://httpd.apache.org/docs/2.0/mod/mod_proxy.html#proxytimeout > > Bye -- Dave Whiteley The School of Electronic and Electrical Engineering The University of Leeds Leeds [EMAIL PROTECTED] 0113 343 2059 _______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )