ValueError: already have current data for oid

[ChrisW]

This is a bonus one, seems to happen only under very high load, and even then pretty rarely...

  File "lib/python/Products/Transience/Transience.py
", line 297, in _move_item
    abucket = self._data.get(ts, None) # XXX ReadConflictError hotspot
  File "lib/python/ZODB/Connection.py", line
704, in setstate
    self._setstate(obj)
  File "lib/python/ZODB/Connection.py", line
742, in _setstate
    p, serial = self._storage.load(obj._p_oid, self._version)
  File "lib/python/ZEO/ClientStorage.py",
line 746, in load
    return self.loadEx(oid, version)[:2]
  File "lib/python/ZEO/ClientStorage.py",
line 774, in loadEx
    self._cache.store(oid, ver, tid, None, data)
  File "lib/python/ZEO/cache.py", line 279,
in store
    raise ValueError(

ValueError: already have current data for oid

[ChrisW (chris-simplistix)]

Changes: submitter email, revised version_info, new comment

Adding information from latest occurence.

[ChrisW (chris-simplistix)]

Just had another occurence of this also under high load:

# Module Products.ZCatalog.CatalogBrains, line 86, in getObject
# Module OFS.Traversable, line 250, in restrictedTraverse
# Module OFS.Traversable, line 185, in unrestrictedTraverse
__traceback_info__: ([], 'some_id')
# Module Products.BTreeFolder2.BTreeFolder2, line 514, in __getattr__
# Module ZODB.Connection, line 732, in setstate
# Module ZODB.Connection, line 768, in _setstate
# Module ZEO.ClientStorage, line 746, in load
# Module ZEO.ClientStorage, line 774, in loadEx
# Module ZEO.cache, line 279, in store

ValueError: already have current data for oid

I wonder if this could be caused by memory exhaustion on the app server?

[Simon Michael (simon)]

Possibly same error (?) experienced with Zope 2.10.3 at zwiki.org, only when using ZEO. See http://zwiki.org/1358 .

[Alec Mitchell (alecm)]

Looking up through the logs this all seemed to start with running out of space on /tmp, I wonder if this is the cause for everyone? If so this can probably be safely closed.

[Alec Mitchell (alecm)]

I'm seeing this with zope 2.9.7 mostly during catalog queries. Very disturbing. Is there some configuration that con be done to at least reduce the likelihood of these?

[Youenn Boussard (y-boussard)]

zeo client write this cache in /tmp if your cache is not persistent. So if you don't have enought space in /tmp you can have that error .
Be careful , you can see the zope cache open file by ls in /tmp.
To see open file use lsof -a -p <pid> where pid is the pid of zope process.
But I have today the same bug in a persistant cache so I invistigate too.
Regards Youenn

[Hanno Schlichting (hannosch)]

Looks like this is caused in insufficient disk space in /tmp. I don't see an easy way of introducing a more helpful error message here.