Plone 扩展赢得';在构建和重新启动后不显示
我正在尝试在我的Plone 4.3.1环境(使用ZEO)中安装一个egg 因此,我在buildout.cfg文件中添加了行“collective.quickupload”,并使用以下命令运行buildout:Plone 扩展赢得';在构建和重新启动后不显示,plone,buildout,egg,zeos,Plone,Buildout,Egg,Zeos,我正在尝试在我的Plone 4.3.1环境(使用ZEO)中安装一个egg 因此,我在buildout.cfg文件中添加了行“collective.quickupload”,并使用以下命令运行buildout: /usr/local/Plone/zeocluster# sudo -E -u plone_buildout ./bin/buildout 以下是我得到的: Updating zeoserver. Updating client1. Updating client2. Updating
/usr/local/Plone/zeocluster# sudo -E -u plone_buildout ./bin/buildout
以下是我得到的:
Updating zeoserver.
Updating client1.
Updating client2.
Updating backup.
Updating zopepy.
Updating unifiedinstaller.
Updating precompiler.
Compiling Python files.
Compiling locale files.
Error while compiling /usr/local/Plone/buildout-cache/eggs/python_gettext-1.2-py2.7.egg/pythongettext/tests/test_escape.po
Error while compiling /usr/local/Plone/buildout-cache/eggs/python_gettext-1.2-py2.7.egg/pythongettext/tests/test5.po
Updating setpermissions.
setpermissions: Running
# Dummy references to force this to execute after referenced parts
echo /usr/local/Plone/zeocluster/var/backups yes > /dev/null
chmod 600 .installed.cfg
# Make sure anything we've created in var is r/w by our group
find /usr/local/Plone/zeocluster/var -type d -exec chmod 770 {} \; 2> /dev/null
find /usr/local/Plone/zeocluster/var -type f -exec chmod 660 {} \; 2> /dev/null
find /usr/local/Plone/zeocluster/var -type d -exec chmod 770 {} \; 2> /dev/null
find /usr/local/Plone/zeocluster/var -type f -exec chmod 660 {} \; 2> /dev/null
chmod 754 /usr/local/Plone/zeocluster/bin/*
*************** PICKED VERSIONS ****************
[versions]
collective.quickupload = 1.6.1
ua-parser = 0.3.4
*************** /PICKED VERSIONS ***************
然后,我使用以下命令重新启动了Plone实例:
/bin/plonectl重新启动
重新启动工作正常,但该扩展未显示在Plone的扩展列表中
我还尝试在fg模式下启动zeoserver、client1和client2。这不管用。我得到了以下错误:
[……]
File "/usr/local/Plone/buildout-cache/eggs/zc.lockfile-1.0.2-py2.7.egg/zc/lockfile/__init__.py", line 59, in _lock_file
raise LockError("Couldn't lock %r" % file.name)
zc.lockfile.LockError: Couldn't lock '/usr/local/Plone/zeocluster/var/filestorage/Data.fs.lock'
非常感谢您的反馈 非常感谢您的回答。我重新启动了服务器(再次),在buildout.cfg中更改了ZEO的IP地址和端口,并正常启动了实例。现在它似乎起作用了。我想你是对的:另一个进程使用了相同的端口。尽管我试图显示正在运行的进程,但它不在列表中。fg模式错误可能是因为后台仍在运行。您认为Plone/Zeo进程是否仍在运行?请尝试。/bin/restartcluster.sh这将重新启动zeoserver和所有客户端。感谢您的回答。但是我的垃圾箱里没有commande restartcluster.shdirectory@AlexMiccoli也可能是您使用了错误的用户运行,或者您的文件权限不正确。