I think it is ZODB corruption. See my post of a couple of weeks ago for
suggestions for recovery.

This the fourth example of ZClass related DB corruption that I've seen in
the past six weeks. In my own brush with this, it seemed to be triggered
by uninstalling and reinstalling products.


On Wed, 8 Nov 2000, Chris McDonough wrote:

> In your start script, set the STUPID_LOG_FILE environment variable to the
> path of a file to which you want log messages to be sent (before 'start'
> calls z2.py).  Then review the log file.  You'll probably get more clues as
> to what is going wrong, allowing you to fix the problem.

> > Error Type: Could not load oid ={, pickled data in traceback info may
> > contain clues
> > Error Value: None

Zope maillist  -  [EMAIL PROTECTED]
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-dev )

Reply via email to