I have seen a similar problems bringing up a system which has been
brought down with the usual
zeoctl stop
zopectl start
mantra. The zope/zeo connection is via a network connection.
Next time it happens I'll file a bug report.
On Thu, 12 Jan 2006, Sidnei da Silva wrote:
> On
On Thu, Jan 12, 2006 at 10:17:54AM -0500, Tim Peters wrote:
| [Sidnei da Silva]
| >> Every now and then I face a corruption of the persistent zeo cache, but
| >> this is the first time I get this variant.
|
| What other variants do you see?
Can't remember right now, it was quite some time ago and
[Tim Peters]
> ...
> It doesn't call fsync() unless it's explicitly closed cleanly, but it's
> unclear what good fsync() actually does across platforms when flush() is
> called routinely and the power stays on.
LOL. Immediately upon sending that msg, there was a power outage here,
which left behi
[Sidnei da Silva]
>> Every now and then I face a corruption of the persistent zeo cache, but
>> this is the first time I get this variant.
What other variants do you see?
>> The cause is very likely to be a forced shutdown of the box this zope
>> instance was running on, but I thought it would be
Sidnei da Silva wrote:
Every now and then I face a corruption of the persistent zeo cache,
but this is the first time I get this variant.
The cause is very likely to be a forced shutdown of the box this zope
instance was running on, but I thought it would be nice to report the
issue.
Here's the
