[Setup] Plone3: some problems using buildout

[Larry Pitcher]

cwarner wrote:
> I can reproduce this, do you have any information on your Python installation
> is it system or are you using a different Python somewhere else on the
> system in addition to having a system install?
> 
> Thanks,
> Christopher Warner
> 
> 
> Toni Mueller-15 wrote:
>>
>> Hi,
>>
>> I'm trying to get a Plone3 instance installed using buildout ("latest" 
>> mode, just updated today) for a deployment configuration, along the
>> lines of Martin's nice tutorial.
>>
>> Everything installs "semi-fine" in that the general machinery works if I 
>> don't attempt to use 'user' or 'effective-user' statements, but run all 
>> processes as me. But I have trouble finding additional information about 
>> doing it in a realistic way, eg. with separate users for these 
>> processes, or otherwise customized zeo.conf and zope.conf configuration 
>> files (ie, extend/modify the recipes). I also have some strange problems 
>> that I couldn't yet fathom:
>>
>>
>> * Starting ZEO works nicely, regardless whether I try to switch
>>    the user or not.
>>
>> * Starting the Zope client ("primary") works nicely if I start
>>    it as me, regardless whether I say "start" or "fg".
>>
>> * Starting the Zope client as root using "start", using an
>>    'effective-user' statement in parts/primary/etc/zope.conf,
>>    does NOT work in that the process starts nicely and doesn't
>>    produce any error messages in the logs (var/log/primary*.log),
>>    but it does not open the listening socket. IOW, I cannot
>>    send any requests to this process.
>>
>> * Starting it as root saying "fg" instead (ie, "./bin/primary fg"),
>>    it does not even start, but yields this error message:
>>
>> # ./bin/primary fg
>> "/home/toni/zope/ffii-plone/parts/primary/bin/runzope"
>> Traceback (most recent call last):
>>    File 
>> "/home/toni/zope/ffii-plone/parts/zope2/lib/python/Zope2/Startup/run.py", 
>> line 56, in ?
>>    File 
>> "/home/toni/zope/ffii-plone/parts/zope2/lib/python/Zope2/Startup/run.py", 
>> line 21, in run
>>    File "/usr/lib/python2.4/site-packages/PIL/__init__.py", line 99, in 
>> prepare
>>
>>    File "/usr/lib/python2.4/site-packages/PIL/__init__.py", line 293, in 
>> makeLockFile
>>
>> ImportError: No module named misc.lock_file
>>
>>
>> Of course, the file is there, and I also chown'ed -R toni:zope and chmod 
>> -R g+rwX everything, so access should really not be a problem.
>>
>>
>> This happens with Plone 3.0.4 with Zope 2.10.5 on Debian Etch/amd64.
>>
>>
>> I've seen a similar problem discussed a few months ago where someone
>> had no luck on Solaris, but I don't know in how far these problems are
>> related.
>>
>>
>> Any help is much appreciated!
>>
>>
>> Best,
>> --Toni++

Toni,

There are some very good examples in Steve's excellent buildout.cfg for 
the UnifiedInstaller found here: 
http://svn.plone.org/svn/plone/Installers/UnifiedInstaller/branches/UnifiedInstallerPlusBuildout/zeo_template/buildout.cfg

His version precompiles the python source files, and only gives write 
permission to the effective-user on the files that need it. You can just 
plug in the values you want where you see something like __EFFECTIVE_USER__.

Have fun!

-- 
Larry Pitcher
Catapult Solutions

Web:   www.catapultsolutions.net
Email: larry.pitcher at gmail.com
Skype: larry.pitcher
Phone: 509.849.2660