[ZODB-Dev] "zeoLoad() raised exception" for a TemporaryStorage in a ZEO/Zope cluster

[Jan-Wijbrand Kolman]

Jeremy,


snip
>> 3) start second ZCS; no errors reported on the ZCS, no errors on 
>> the ZSS, just the messages that also this client connected just 
>> fine.
snip

> Does that means it doesn't work correctly before step 3?  In what 
> way is its operation incorrect?

I only meant to say that, even with this error msg, after step 3 I 
have my ZEO cluster (one ZSS, two ZCSs) fully functional. Before step 
3 I obviously have just one ZCS running, which nonetheless runs fine, 
although it reported the KeyError.

> It doesn't seem like you're doing anything wrong, but it's hard to 
> be sure since you didn't describe what you expect to happen.
>
> Note that any time you open a new database, it tries to load the 
> root object from the storage.  If it doesn't exist, it will create 
> the root.
>
> So if your KeyError is for oid '\x00\x00\x00\x00\x00\x00\x00\x00', 
> then this KeyError isn't at all surprising.  What would be 
> surprising is if the first connection failed to operate correctly 
> after a KeyError?  Is that what happens?

Hmm, I guess I should've included my dbtab config too, to explain the 
setup I'm aiming for. Roughly this is a Zope root mounted on the 
FileStorage on the ZSS and a mount point in the root (say 
'/sharedcache'), mounted on the TemporaryStorage on the ZSS.

The log file didn't tell me what the oid for this KeyError was. But by 
hacking a print statement in the load() method just now, it indeed 
printed '\x00\x00\x00\x00\x00\x00\x00\x00'. So, this is just normal(?)

Again, the setup does work now, regardless of the KeyError. I just 
wanted to be sure whether something is wrong and thus might bite me 
later on, or whether this can be explained and is something I should 
not care about - maybe this specific 'the root does not exist in the 
storage yet' situation deserves a more informational log message 
instead of just a traceback?

Anyway, thanks for your answer!!


regards,
jw


-- 
Jan-Wijbrand Kolman
jw at infrae.com