Hi Markos
I just tried your suggestions running this setup as root. This on a
fresh Ubuntu 14.04 64bit server. It did not work out very well, here
are the errors: (I will now try on Debian 7.8):
Got mr.developer 1.21.
Version conflict while processing requirement zc.buildout (constrained
to zc.buildout==1.7.1)
Getting required 'zc.buildout==1.7.1'
We have no distributions for zc.buildout that satisfies
'zc.buildout==1.7.1'.
Getting distribution for 'zc.buildout==1.7.1'.
Running easy_install:
"/home/ubuntubasic/plumi/plumi.app/bin/python" "-c" "from
setuptools.command.easy_install import main; main()" "-mZUNxd"
"/home/ubuntubasic/plumi/plumi.app/eggs/tmpvYU16S" "-q"
"/home/ubuntubasic/plumi/plumi.app/downloads/dist/zc.buildout-1.7.1.tar.gz"
path=/home/ubuntubasic/plumi/plumi.app/eggs/setuptools-14.0-py2.7.egg
Got zc.buildout 1.7.1.
Version conflict while processing requirement setuptools (constrained to
setuptools==0.6c11)
Getting required 'setuptools==0.6c11'
We have no distributions for setuptools that satisfies 'setuptools==0.6c11'.
Getting distribution for 'setuptools==0.6c11'.
While:
Installing.
Loading extensions.
Getting distribution for 'setuptools==0.6c11'.
An internal error occurred due to a bug in either zc.buildout or in a
recipe being used:
Traceback (most recent call last):
File
"/home/ubuntubasic/plumi/plumi.app/eggs/zc.buildout-2.3.1-py2.7.egg/zc/buildout/buildout.py",
line 1946, in main
getattr(buildout, command)(args)
File
"/home/ubuntubasic/plumi/plumi.app/eggs/zc.buildout-2.3.1-py2.7.egg/zc/buildout/buildout.py",
line 467, in install
self._load_extensions()
File
"/home/ubuntubasic/plumi/plumi.app/eggs/zc.buildout-2.3.1-py2.7.egg/zc/buildout/buildout.py",
line 995, in _load_extensions
newest=self.newest, allow_hosts=self._allow_hosts)
File
"/home/ubuntubasic/plumi/plumi.app/eggs/zc.buildout-2.3.1-py2.7.egg/zc/buildout/easy_install.py",
line 848, in install
return installer.install(specs, working_set)
File
"/home/ubuntubasic/plumi/plumi.app/eggs/zc.buildout-2.3.1-py2.7.egg/zc/buildout/easy_install.py",
line 685, in install
for_buildout_run=for_buildout_run):
File
"/home/ubuntubasic/plumi/plumi.app/eggs/zc.buildout-2.3.1-py2.7.egg/zc/buildout/easy_install.py",
line 549, in _get_dist
dist = self._env.best_match(requirement, ws)
File "build/bdist.linux-x86_64/egg/pkg_resources/__init__.py", line
1042, in best_match
dist = working_set.find(req)
File "build/bdist.linux-x86_64/egg/pkg_resources/__init__.py", line
674, in find
raise VersionConflict(dist, req)
VersionConflict: (setuptools 14.0
(/home/ubuntubasic/plumi/plumi.app/eggs/setuptools-14.0-py2.7.egg),
Requirement.parse('setuptools==0.6c11'))
Den 09. mars 2015 11:41, skrev Markos Gogoulos:
Hi Graabein,
the buildout needs update, but if you follow Simoni's instructions you
can make it work.
Personally I run Plumi buildout as root, to take care of all the
chowns/chmods etc, since you define users that will run services on
site.cfg. I usually create a user (eg zope) and set this on site.cfg as
transcode-user, zeo-user, zope_user etc.
On a debian 7.8 system I was able to install plumi following the
instructions to pin the two packages. I didn't have to upgrade
setuptools etc, I used system's python (with virtualenv)
So on buildout.cfg on [versions] I added these two lines
zc.buildout = 1.7.1
distribute = 0.6.35
then
./bin/python bootstrap.py && ./bin/buildout -v
after this finishes
cd ffmpeg && ../bin/python bootstrap.py &&./bin/buildout -v
after that I could start supervisord as root, and it chowns to the
specified users.
A quick fix for the PYTHON_EGG_CACHE issue, is to set this env before
you run supervisord or supervisorctl.
Eg if your plumi installation is /home/videomaster/plumi/plumi.app,
create /home/videomaster/plumi/plumi.app/var/.python-eggs (and chown
the dir as the zope-user of site.cfg)
Then before you start supervisord or supervisorctl run
PYTHON_EGG_CACHE="/home/videomaster/plumi/plumi.app/var/.python-eggs"
export PYTHON_EGG_CACHE
/home/videomaster/plumi/plumi.app/bin/supervisord
you can set this to /etc/rc.local if you plan to start plumi after
reboots. You can also set the above on supervisord script, by adding
to bin/supervisord
import sys, os
os.environ['PYTHON_EGG_CACHE'] =
"/home/videomaster/plumi/plumi.app/var/.python-eggs"
(in this case note that this will be overridden next time buildout is
run )
Hope this helps!
YG. based on the last output you've sent I would suggest that you
re-run the buildout as root, and let it fix the permissions.
On Mon, Mar 9, 2015 at 5:57 AM, Graabein <[email protected]
<mailto:[email protected]>> wrote:
Another test on Ubuntu64, end up with the exact same install error
as described below.
Den 06. mars 2015 21:32, skrev Graabein:
Thanks again Simone, your help is very appreciated.
I am making progress, but still get errors (see in the bottom of
this thread).
Here is what I did (Debian 7.8 DigitalOcean):
root@mydomain:# apt-get install build-essential pkg-config
git-core python-dev libjpeg62-dev zlib1g-dev libxslt1-dev
groff-base python-virtualenv
root@mydomain:# useradd zope
root@mydomain:# adduser videomaster (set password)
root@mydomain:# su videomaster
videomaster@mydomain:~/ cd (to home)
videomaster@mydomain:~/mkdir plumi
Then followed
http://docs.plone.org/old-reference-manuals/buildout/defaults.html
videomaster@mydomain:~/mkdir .buildout
videomaster@mydomain:~/cd .buildout
videomaster@mydomain:~/.buildout$
<mailto:videomaster@mydomain:%7E/.buildout$> mkdir eggs
videomaster@mydomain:~/.buildout$
<mailto:videomaster@mydomain:%7E/.buildout$> mkdir downloads
videomaster@mydomain:~/.buildout$
<mailto:videomaster@mydomain:%7E/.buildout$> mkdir extends
videomaster@mydomain:~/.buildout$
<mailto:videomaster@mydomain:%7E/.buildout$> nano default.cfg
Added the following in default.cfg
[buildout]
eggs-directory = /home/videomaster/.buildout/eggs
download-cache = /home/videomaster/.buildout/downloads
extends-cache = /home/videomaster/.buildout/extends
(saved default.cfg)
$ cd ..
$ cd plumi
$ git clone https://github.com/plumi/plumi.app/
$ cd plumi.app
$ nano buildout.cfg
Added:
[versions]
zc.buildout = 1.7.1
distribute = 0.6.35
(saved buildout.cfg)
$ nano site.cfg
Modified
www-server-name = mydomain.org <http://mydomain.org>
www-videoserver-name = newvideos.mydomain.org
<http://newvideos.mydomain.org>
(saved site.cfg)
~/plumi.app$ virtualenv .
~/plumi.app$ cd ffmpeg
~/plumi.app/ffmpeg$ ../bin/python bootstrap.py && ./bin/buildout -vN
Looks like all went well in ffmpeg, so elevated up one dir
~/plumi.app$ ./bin/python bootstrap.py && ./bin/buildout -v
Then it worked for a long time, much longer than earlier.
I got a lot of "syntax error" messages along the way, but it
continued and continued, and at the end it looked like you see
below. I just copy&past a little part of the final compiling for
you to see.
chgrp: changing group of
`/home/videomaster/plumi/plumi.app/var/log': Operation not permitted
chgrp: changing group of `/home/videomaster/plumi/plumi.app/var':
Operation not permitted
chown: changing ownership of
`/home/videomaster/plumi/plumi.app/transcoded': Operation not
permitted
mkdir: cannot create directory
`/home/videomaster/plumi/plumi.app/var/filestorage': File exists
mkdir: cannot create directory
`/home/videomaster/plumi/plumi.app/var/blobstorage': File exists
chown: cannot access `/home/videomaster/plumi/plumi.app/eggs': No
such file or directory
chown: changing ownership of
`/home/videomaster/plumi/plumi.app/torrents': Operation not permitted
chown: changing ownership of
`/home/videomaster/plumi/plumi.app/torrents_safe': Operation not
permitted
chown: changing ownership of
`/home/videomaster/plumi/plumi.app/var/filestorage': Operation
not permitted
chown: changing ownership of
`/home/videomaster/plumi/plumi.app/var/blobstorage': Operation
not permitted
chown: changing ownership of
`/home/videomaster/plumi/plumi.app/var/log/plone.log': Operation
not permitted
chown: changing ownership of
`/home/videomaster/plumi/plumi.app/var/log/plone-Z2.log':
Operation not permitted
chown: changing ownership of
`/home/videomaster/plumi/plumi.app/parts/transcodedaemon/transcodedaemon.log':
Operation not permitted
chown: changing ownership of
`/home/videomaster/plumi/plumi.app/parts/transcodedaemon':
Operation not permitted
chown: changing ownership of `/tmp//plumitmp': Operation not
permitted
chmod: changing permissions of `/tmp//plumitmp': Operation not
permitted
Unused options for chown: 'update-command'.
Installing plumisite.
Installing 'zc.recipe.egg', 'collective.recipe.scriptgen'.
We have the distribution that satisfies 'zc.recipe.egg==1.2.2'.
We have the best distribution that satisfies
'collective.recipe.scriptgen'.
Picked: collective.recipe.scriptgen = 0.2
Getting required 'zc.buildout==1.7.1'
We have the distribution that satisfies 'zc.buildout==1.7.1'.
Getting required 'distribute==0.6.35'
We have the distribution that satisfies 'distribute==0.6.35'.
Generated script '/home/videomaster/plumi/plumi.app/bin/plumisite'.
Installing auto-install-plumisite.
Error: only root can use -u USER to change users
For help, use /home/videomaster/plumi/plumi.app/bin/zeoserver -h
While:
Installing auto-install-plumisite.
An internal error occurred due to a bug in either zc.buildout or in a
recipe being used:
Traceback (most recent call last):
File
"/home/videomaster/.buildout/eggs/zc.buildout-1.7.1-py2.7.egg/zc/buildout/buildout.py",
line 1866, in main
getattr(buildout, command)(args)
File
"/home/videomaster/.buildout/eggs/zc.buildout-1.7.1-py2.7.egg/zc/buildout/buildout.py",
line 625, in install
installed_files = self[part]._call(recipe.install)
File
"/home/videomaster/.buildout/eggs/zc.buildout-1.7.1-py2.7.egg/zc/buildout/buildout.py",
line 1345, in _call
return f()
File
"/home/videomaster/.buildout/eggs/collective.recipe.cmd-0.10-py2.7.egg/collective/recipe/cmd/__init__.py",
line 56, in install
self.execute()
File
"/home/videomaster/.buildout/eggs/collective.recipe.cmd-0.10-py2.7.egg/collective/recipe/cmd/__init__.py",
line 69, in execute
run_commands(cmds, self.shell)
File
"/home/videomaster/.buildout/eggs/collective.recipe.cmd-0.10-py2.7.egg/collective/recipe/cmd/__init__.py",
line 39, in run_commands
check_call('%s %s' % (shell, tmpfile), shell=True)
File "/usr/lib/python2.7/subprocess.py", line 511, in check_call
raise CalledProcessError(retcode, cmd)
CalledProcessError: Command 'sh /tmp/tmpV_mayD/run' returned
non-zero exit status 2
*********************************************
Writing picked versions to versions.cfg
*********************************************
_______________________________________________
Discuss mailing list
[email protected] <mailto:[email protected]>
http://lists.plumi.org/listinfo/discuss
_______________________________________________
Discuss mailing list
[email protected] <mailto:[email protected]>
http://lists.plumi.org/listinfo/discuss
--
https://unweb.me
state of the art information systems
_______________________________________________
Discuss mailing list
[email protected]
http://lists.plumi.org/listinfo/discuss
_______________________________________________
Discuss mailing list
[email protected]
http://lists.plumi.org/listinfo/discuss
