[ZCM] [ZC] 1204/ 6 Comment "ZODB load state error"

[Collector: Zope Bugs, Features, and Patches ...]

Issue #1204 Update (Comment) "ZODB load state error"
 Status Accepted, Zope/bug medium
To followup, visit:
  http://zope.org/Collectors/Zope/1204

==============================================================
= Comment - Entry #6 by thyb on Jan 28, 2004 8:22 am

I vote for gamma ray =] that bastard...
________________________________________
= Comment - Entry #5 by tim_one on Jan 27, 2004 1:49 pm

This is such a low-level "impossible" error that I doubt any logging is going to help.  There are no other reports of it, either -- it *could* be due to things like a flaky memory chip, a bad network device, a bad spot on a disk, or a stray gamma ray flipping a bit.

I may (or may not) have seen a similar thing when running test suites intensively overnight, but about 6 months ago:  there was one instance of a mysterious MemoryError in the same place.  I've never seen that again.

But because I did see something similar once, I want to keep the Collector report open to gather clues in one place.  If it's actually a bug in ZODB code, it's extremely shy, and diagnosing and fixing something like that will most likely require finding someone for whom it happens often, and who can reduce it to a self-contained stress test.  I've tried (and failed) to provoke it on purpose.
________________________________________
= Comment - Entry #4 by thyb on Jan 27, 2004 4:15 am

Hi,

I can't tell if it's reproducible or not. This was the first time I ran into this problem. My Zope system was running for a week then crashed. So I guess I have to wait another week for the same error to occure if reproduceable.

How do I get more information on what has happened? How should I configure logging? Debugging?

Otherwise I get the same error message like the one in 'Entry #1', which you said doesn't help much.

Thx for the assistance

________________________________________
= Assign - Entry #3 by tim_one on Jan 26, 2004 11:19 am

 Status: Rejected => Accepted

 Supporters added: jeremy, tim_one

Accepting this, and assigned to Jeremy and me.

I've heard of this happening before, and I want a Collector issue open on it so we can collect clues in one place.

Thyb, is this reproducible?

Chances are "something is corrupted", but without a reproducible guess it's hard to guess what or how or why.
________________________________________
= Reject - Entry #2 by ajung on Jan 26, 2004 6:59 am

 Status: Pending => Rejected

Please use the Zope or Zodb-Dev mailing list for asking questions.

-aj
________________________________________
= Request - Entry #1 by Anonymous User on Jan 26, 2004 6:20 am

I just found this in my Zope log file. After this error the Zope system stopped. No wonder, but certainly not because of physical memory error. What could be the problem?

2004-01-25T02:55:21 ERROR(200) ZODB Couldn't load state for 0000000000003ef2
Traceback (most recent call last):
  File "/opt/freeware/zope/lib/python/ZODB/Connection.py", line 564, in setstate
    self._set_ghost_state(obj, p)
  File "/opt/freeware/zope/lib/python/ZODB/Connection.py", line 603, in _set_ghost_state
    state = unpickler.load()
MemoryError

==============================================================