[Zope-DB] Re: Database Corruption (1 possible solution)
el-spam at yandex.ru
Wed Jun 30 14:03:58 EDT 2004
Wednesday, June 30, 2004, 9:47:59 PM, you wrote:
NB> Nope - the genericness of the reported error in event.log and many other
NB> frustrated posts of users in lists/web pages experiencing similar things
NB> (during frantic google searching) led me to believe ZODB problems like
NB> this are commonplace.
I tried to find info about a problem in logs. Unsuccessful :(
I've even turn on trace.log.
I see log only when I get Read Error - but I dont see moment when DB
makes errorneous record.
NB> I'll see if I can dig up a log then. The log was not particularly
NB> descriptive however as the problem happened on a production ZEO platform
NB> both times with logging turned down.
NB> Jim Fulton wrote:
>> Nick Bower wrote:
>>> I was going to post this tip on it's own, but seeing how it's relevant
>>> to the current discussion, I'll post it here.
>>> Recently we've been having "read conflict errors" preventing Zope from
>>> connecting to a ZODB on startup in a ZEO deployment. (Moving the
>>> Data.fs* to a standalone non-ZEO configuration made no difference).
>>> Upon a little digging, I found an error relating to an illegal
>>> attempted reassignment of an oid.
>>> I tried the recovery tools, but these did nothing.
>>> The solution was to remove the Data.fs.index and Data.fs.tmp files and
>>> let ZODB rebuild them on startup. Why this worked I have no idea (it
>>> was a stab in the dark at the time) as I don't know much about ZODB
>>> internals. However, this happened to us twice in a single week (which
>>> on it's own is quite sad).
>> Did you report this to either the zodb-dev list or to the
>> zodb bug tracker?
NB> Zope-DB mailing list
NB> Zope-DB at zope.org
Eugene mailto:el-spam at yandex.ru
More information about the Zope-DB