[zope2-tracker] [Bug 142861] Re: ZODB load state error
Juan Jose Amor Iglesias
jjamor at gsyc.escet.urjc.es
Fri May 15 14:34:50 EDT 2009
We got these errors using Plone 3.1 and Zope 2.10.6-final. The Plone
finally crashed:
2009-05-13T13:32:19 ERROR ZODB.Connection Couldn't load state for 0x03db0a
Traceback (most recent call last):
File "/usr/local/Plone-3.1/zinstance/parts/zope2/lib/python/ZODB/Connection.py", line 761, in setstate
self._setstate(obj)
File "/usr/local/Plone-3.1/zinstance/parts/zope2/lib/python/ZODB/Connection.py", line 819, in _setstate
self._reader.setGhostState(obj, p)
File "/usr/local/Plone-3.1/zinstance/parts/zope2/lib/python/ZODB/serialize.py", line 604, in setGhostState
state = self.getState(pickle)
File "/usr/local/Plone-3.1/zinstance/parts/zope2/lib/python/ZODB/serialize.py", line 597, in getState
return unpickler.load()
File "/usr/local/Plone-3.1/zinstance/parts/zope2/lib/python/ZODB/serialize.py", line 471, in _persistent_load
return self.load_oid(reference)
File "/usr/local/Plone-3.1/zinstance/parts/zope2/lib/python/ZODB/serialize.py", line 537, in load_oid
return self._conn.get(oid)
File "/usr/local/Plone-3.1/zinstance/parts/zope2/lib/python/ZODB/Connection.py", line 213, in get
p, serial = self._storage.load(oid, self._version)
File "/usr/local/Plone-3.1/zinstance/parts/zope2/lib/python/ZODB/FileStorage/FileStorage.py", line 554, in load
data = self._file.read(h.plen)
MemoryError
------
also a lots of errors like this:
2009-05-13T13:45:11 ERROR Zope.SiteErrorLog http://nnn/nnn/nnn/sendto_form
Traceback (innermost last):
Module ZPublisher.Publish, line 122, in publish
Module ZServer.HTTPResponse, line 262, in setBody
Module ZPublisher.HTTPResponse, line 324, in setBody
Module ZPublisher.HTTPResponse, line 476, in _encode_unicode
MemoryError
Is this bug still unsolved? We have this Plone in a production site
since more than 1 year and this is the first time it crashes with these
errors...
--
ZODB load state error
https://bugs.launchpad.net/bugs/142861
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.
More information about the zope2-tracker
mailing list