zeo.log Format

ZEO Server Howto

INFO

WARNING

CRITICAL

INFO ZEO.StorageServer (8559/127.0.0.1:44914) Transaction blocked waiting for storage. Clients waiting: 1.

INFO ZEO.StorageServer (8559/127.0.0.1:44913) Blocked transaction restarted.

POSKeyError for Object 0

2008-02-23T10:39:55 INFO ZEO.zrpc.Connection(S) (127.0.0.1:50478) loadEx() raise
d exception: 0x00
Traceback (most recent call last):
  File "/home/marr/Plone-3.0.6/lib/python/ZEO/zrpc/connection.py", line 531, in
handle_request
    ret = meth(*args)
  File "/home/marr/Plone-3.0.6/lib/python/ZEO/StorageServer.py", line 254, in lo
adEx
    return self.storage.loadEx(oid, version)
  File "/home/marr/Plone-3.0.6/lib/python/ZODB/FileStorage/FileStorage.py", line
 523, in loadEx
    pos = self._lookup_pos(oid)
  File "/home/marr/Plone-3.0.6/lib/python/ZODB/FileStorage/FileStorage.py", line
 514, in _lookup_pos
    raise POSKeyError(oid)
POSKeyError: 0x00

Jim Fulton: The POSKey error for object 0 can be ignored. It is normal. When the 
database is opened for the first time, it tries to load object 0 and then creates it if it doesn't exist.