Simplify the Problem

by John Samuel Anderson — last modified Jan 15, 2009 01:56 AM

Modify buildout to run Zope without ZEO.

Temporarily running Zope without ZEO

Debugging ZEO is apparently more than my brain can handle today. Consequently, I'm going to remove it from the problem. Thankfully, I'm using buildout, so this should be fairly painless. Here are the steps:

Edit buildout.cfg and comment-out the ZEO-specific lines:

[buildout]
parts =    
    pil
    python-ldap
    plone
    zope2
    productdistros
    svnproducts
    instance1
    zopepy
    translations

#Don't forget to put this back before instance1!
#    zeoserver

...

[instance1]
recipe = plone.recipe.zope2instance==2.4
zope2-location = ${zope2:location}
#Set zeo-client = true to enable ZEO.
zeo-client = false
zeo-address = ${zeoserver:zeo-address}
zodb-cache-size = 15000
zeo-client-cache-size = 500MB
...

Run buildout and hope it works.
Restart Zope in foreground mode.

Honest Mistake #3 Explained

When I made the change to the eggs/ZODB3-3.8.1b7-py2.4-linux-x86_64.egg/ZODB/utils.py

file, it got overwritten when I re-ran buildout. By default, buildout will download a fresh copy of the codebase everytime you run it. So, be careful, and read up on how to make buildout use caches.

Fortunately, this code change was easy to make again.