Hmm,
there goes my simple answer! ;-)
I must admit that I can't see what you've done wrong, looking at your code.
So here goes some grasping at straws:
(i) Make sure all the directories you are writing to exist and have the
correct permissions to be written to by plone (I'm sure this was the first
thing you checked!)
(ii) It may be worth trying absolute paths instead of variables (just in
case there is a problem with the variable):
e.g. /opt/plone/blah/blah/var/ahs/prod/Data_ahs_prod.fs
instead of ...
$INSTANCE/var/ahs/prod/Data_ahs_prod.fs
All my modifications are done via buildout. Here are the relevant sections
of mine if they are any use for checking:
# Use this section to install and configure a Zope
# Enterprise Objects server.
# For options see http://pypi.python.org/pypi/plone.recipe.zope2zeoserver
[zeoserver]
recipe = plone.recipe.zope2zeoserver
zope2-location = ${zope2:location}
zeo-address = ${buildout:zeo-address}
effective-user = zeo
# Put the log, pid and socket files in var/zeoserver
zeo-log = ${buildout:directory}/var/zeoserver/zeoserver.log
pid-file = ${buildout:directory}/var/zeoserver/zeoserver.pid
socket-name = ${buildout:directory}/var/zeoserver/zeo.zdsock
zeo-conf-additional =
<filestorage 2>
path ${buildout:zeo-filestorage}/BioMedIA.fs
</filestorage>
<filestorage 3>
path ${buildout:zeo-filestorage}/BioInstruments.fs
</filestorage>
# Use this section to install and configure a Zope
# client instance.
# For options see http://pypi.python.org/pypi/plone.recipe.zope2instance
[client1]
recipe = plone.recipe.zope2instance
zope2-location = ${zope2:location}
zeo-client = true
zeo-address = ${zeoserver:zeo-address}
# The line below sets only the initial password. It will not change an
# existing password.
user = admin:xxxxxxxxxxxxxxxxx
http-address = ${buildout:client1-address}
effective-user = plone
# change debug-mode to "on" to run in development mode
debug-mode = ${buildout:debug-mode}
# change verbose-security to "on" for detailed security
# errors while developing
verbose-security = ${buildout:verbose-security}
deprecation-warnings = ${buildout:deprecation-warnings}
# Put the log, pid, lock files in var/client1
event-log = ${buildout:directory}/var/client1/event.log
z2-log = ${buildout:directory}/var/client1/Z2.log
pid-file = ${buildout:directory}/var/client1/client1.pid
lock-file = ${buildout:directory}/var/client1/client1.lock
# If you want Zope to know about any additional eggs, list them here.
# e.g. eggs = ${buildout:eggs} my.package
eggs =
${buildout:eggs}
# If you want to register ZCML slugs for any packages, list them here.
# e.g. zcml = my.package my.other.package
zcml =
${buildout:zcml}
products =
${buildout:directory}/products
${productdistros:location}
# You may also control the environment variables for the instance.
environment-vars =
PYTHON_EGG_CACHE ${buildout:directory}/var/.python-eggs
# Separate data.fs for each site.
zope-conf-additional =
<zodb_db BioMedIA>
# FileStorage database for Biomedical Image Analysis (BioMedIA)
Laboratory
<zeoclient>
server localhost:8100
storage 2
name BioMedIA
var /usr/local/Plone/zeocluster/parts/client1/var
</zeoclient>
mount-point /BioMedIA
#explicit declaration of object ZODB mount point object type
container-class OFS.Folder.Folder
</zodb_db>
<zodb_db BioInstruments>
# FileStorage database for Biomedical Instrumentation
<zeoclient>
server localhost:8100
storage 3
name BioInstruments
var /usr/local/Plone/zeocluster/parts/client1/var
</zeoclient>
mount-point /BioInstruments
#explicit declaration of object ZODB mount point object type
container-class OFS.Folder.Folder
</zodb_db>
# client2 picks up nearly all its configuration
# from client1. If you need to create a new client
# stanza, you should be able to copy this (with a new part name),
# changing only the parts with "client2" in them.
# For options see http://pypi.python.org/pypi/collective.recipe.zope2cluster
[client2]
recipe = collective.recipe.zope2cluster
instance-clone = client1
# we only need to specify what's different from the clone instance.
http-address = ${buildout:client2-address}
# Put the log, pid, lock files in var/client2
event-log = ${buildout:directory}/var/client2/event.log
z2-log = ${buildout:directory}/var/client2/Z2.log
pid-file = ${buildout:directory}/var/client2/client1.pid
lock-file = ${buildout:directory}/var/client2/client1.lock
# Separate data.fs for each site.
zope-conf-additional =
<zodb_db BioMedIA>
# FileStorage database for Biomedical Image Analysis (BioMedIA)
Laboratory
<zeoclient>
server localhost:8100
storage 2
name BioMedIA
var /usr/local/Plone/zeocluster/parts/client2/var
</zeoclient>
mount-point /BioMedIA
#explicit declaration of object ZODB mount point object type
container-class OFS.Folder.Folder
</zodb_db>
<zodb_db BioInstruments>
# FileStorage database for Biomedical Instrumentation
<zeoclient>
server localhost:8100
storage 3
name BioInstruments
var /usr/local/Plone/zeocluster/parts/client2/var
</zeoclient>
mount-point /BioInstruments
#explicit declaration of object ZODB mount point object type
container-class OFS.Folder.Folder
</zodb_db>
Cheers, Jim
--
View this message in context:
http://plone.293351.n2.nabble.com/Having-Problems-with-Multiple-Data-fs-Files-on-One-Zope-tp5068530p5097530.html
Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com.
_______________________________________________
Setup mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/setup
