Dennis Allison wrote:
2006-02-06T14:07:20 INFO ZPublisher.Conflict ConflictError at
:
database conflict error (oid 0x086e, class BTrees._OOBTree.OOBTree, serial
this txn started with 0x03633ca95f75e900 2006-02-06 22:01:22.373575,
serial currently committed 0x03633caf59114244 2006-02-06 22:07:2
Dennis Allison wrote at 2006-2-7 18:18 -0800:
> ...
>What sort of Zope failure can cause this sort of behavior? What's the
>best approach to get more information to localize the failure.
A crash presented to Zope as a fatal signal (usually "SIGSEGV"
or "SIGBUS").
Reconfigure your Linux account
Arh...
I forgot that internal logging levels override.
Still, you'd think something that triggers a crash would have a level
higher than info. Careful examination of the trace log shows nothing.
I'll fix the log level & see if that turns anything up.
On Tue, 7 Feb 2006, Paul Winkler wrote
On Tue, Feb 07, 2006 at 06:18:49PM -0800, Dennis Allison wrote:
>
> Zope 2.9.0
> Python 2.4.2
> Amd dual Opteron
> Linux
>
> I am seeing occasional (several per day) Zope crashes under load. The
> event.log immediately before and after the crash looks like:
>
>
> 2006-02-06T14:07:20 INFO ZPu
