On Feb 3, 2006, at 1:06 PM, Paul Winkler wrote:
If I were in your shoes the first thing I'd do is bump up the log
levels
on both zope and zeo to BLATHER. Adds overhead I know, but you
need to find
the problem somehow... it's a weird one, I've never seen zope
restart "for no reason".
This
On Fri, Feb 03, 2006 at 08:35:11AM -0800, Dennis Allison wrote:
> Timing correlates to the second. Zope and ZEO live on the
> same physical box.
OK. Do you have more than one ZEO client? If not,
I'd reevaluate whether you need ZEO at all.
(It's great for zopectl debug on a live sys
Paul,
Thanks for the assist. Comments on your comments interlinearly below.
I have increased cache and other resources to see what the impact will be.
On Fri, 3 Feb 2006, Paul Winkler wrote:
> On Fri, Feb 03, 2006 at 01:00:45AM -0800, Dennis Allison wrote:
> >
> > Zope 2.9.0
> >
> > We
On Fri, Feb 03, 2006 at 01:00:45AM -0800, Dennis Allison wrote:
>
> Zope 2.9.0
>
> We are seeing spontaneous restarts of Zope with no indication in any of
> the standard Zope logs. Looking at the ZEO log indicates that the
> restarts of Zope are due to a lost connection between Zope & ZEO but
Zope 2.9.0
We are seeing spontaneous restarts of Zope with no indication in any of
the standard Zope logs. Looking at the ZEO log indicates that the
restarts of Zope are due to a lost connection between Zope & ZEO but
with no other information. The logging level is set at the distribution
d