plone.recipe.zope2zeoserver ?generates? zeoctl and runzeo with incorrect PYTHONPATH and ZODB3_HOME

Bug #179117 reported by ken manheimer on 2007-12-28
Affects Status Importance Assigned to Milestone

Bug Description

i'm actually very unclear about where the responsibility lies for the failure of proper PYTHONPATH and ZODB3_HOME settings in the generated bin/runzeo and bin/zeoctl scripts. i am trying to use plone.recipe.zope2zeoserver in combination with andi zeidler's adaptation to use a blob-aware-ZODB version of Zope with plone, and unable to get it to make the right settings. plone.recipe.zope2instance does the right thing for the client's bin/runzope and bin/zopectl, however.

see for details.

LeoRochael (leorochael) wrote :

ZODB3_HOME is a rather useless variable that goes back to the monolithic days of full Zope installations. It's a single path that is supposed to be added to PYTHONPATH and contain a ZODB distribution and all its dependencies, like ZConfig and zdaemon.

On my branch at:

I'm extending the zope2zeoinstance strategy of patching the script files and setting more appropriate values.

LeoRochael (leorochael) wrote :

Code commited, Please test.

ken manheimer (ken-manheimer) wrote :

i can confirm that your version of plone.recipe.zope2zeoserver resolves the problems i was seeing! the server's zeo.conf has the correct blobstorage storage declaration, and the server's bin/runzeo and bin/zeoctl scripts have the right ZODB_HOME and PYTHONPATH settings. thanks!

Hanno Schlichting (hannosch) wrote :

The branch is merged to trunk, new release follows shortly after I get a comment on 'blob-cache-writable' mentioned in

Changed in collective.buildout:
status: New → Fix Committed
Hanno Schlichting (hannosch) wrote :

0.9 releease is out.

Changed in collective.buildout:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers