我在安装后运行plone 4.3.2时遇到问题(在Fedora 18中)。我正在使用统一安装程序。我已经多次重新安装了同样的问题。我正在使用统一安装。我已经使用了Plone 2和3没有问题,所以我不确定这里发生了什么。似乎有一些许可问题。 README似乎说应该使用plone_daemon调用“plonectl start”。但是Plone文件夹由plone_buildout拥有。我已经包含了安装输出以及Plone目录权限的打印输出。
有人可以告诉我该怎么做。感谢。
[root@localhost Plone-4.3.2-UnifiedInstaller]# ./install.sh zeo --password=admin
Testing /usr/bin/python2.7 for Zope/Plone requirements....
/usr/bin/python2.7 looks OK. We'll try to use it.
Root install method chosen. Will install for use by users:
ZEO & Client Daemons: plone_daemon
Code Resources & buildout: plone_buildout
Detailed installation log being written to /home/student/Desktop/Plone-4.3.2-UnifiedInstaller/install.log
Installing Plone 4.3.2 at /usr/local/Plone
Using useradd and groupadd to create users and groups.
useradd: warning: the home directory already exists.
Not copying any file from skel directory into it.
Creating mailbox file: File exists
useradd: warning: the home directory already exists.
Not copying any file from skel directory into it.
Creating mailbox file: File exists
Creating python virtual environment, no site packages.
New python executable in /usr/local/Plone/Python-2.7/bin/python2.7
Also creating executable in /usr/local/Plone/Python-2.7/bin/python
Installing Setuptools..............................................................................................................................................................................................................................done.
Installing Pip.....................................................................................................................................................................................................................................................................................................................................done.
Compiling and installing jpeg local libraries ...
Unpacking buildout cache to /usr/local/Plone/buildout-cache
Copying Plone-docs
Setting /usr/local/Plone ownership to plone_buildout:plone_group
Copying buildout skeleton
Fixing up bin/buildout
Building Zope/Plone; this takes a while...
Buildout completed
#####################################################################
###################### Installation Complete ######################
Plone successfully installed at /usr/local/Plone
See /usr/local/Plone/zeocluster/README.html
for startup instructions
Use the account information below to log into the Zope Management Interface
The account has full 'Manager' privileges.
Username: admin
Password: admin
This account is created when the object database is initialized. If you change
the password later (which you should!), you'll need to use the new password.
Use this account only to create Plone sites and initial users. Do not use it
for routine login or maintenance.
- If you need help, ask the mailing lists or #plone on irc.freenode.net.
- The live support channel also exists at http://plone.org/chat
- You can read/post to the lists via http://plone.org/forums
- Submit feedback and report errors at http://dev.plone.org/plone
(For install problems, specify component "Installer (Unified)")
[root@localhost Plone-4.3.2-UnifiedInstaller]# sudo -u plone_daemon /usr/local/Plone/zeocluster/bin/plonectl start
sudo: unable to execute /usr/local/Plone/zeocluster/bin/plonectl: Permission denied
[root@localhost Plone-4.3.2-UnifiedInstaller]# cd /usr/local/Plone/
[root@localhost Plone]# ls -la
total 24
drwxr-sr-x. 6 plone_buildout plone_group 4096 Dec 25 14:59 .
drwxr-xr-x. 12 root root 4096 Dec 25 14:56 ..
drwxr-xr-x. 4 plone_buildout plone_group 4096 Mar 8 2011 buildout-cache
drwx------. 2 plone_buildout plone_group 4096 Dec 25 14:56 Plone-docs
drwxr-xr-x. 7 plone_buildout plone_group 4096 Dec 25 14:56 Python-2.7
drwx--S---. 8 plone_buildout plone_group 4096 Dec 25 14:59 zeocluster
[root@localhost Plone]# ls -la zeocluster/
total 128
drwx--S---. 8 plone_buildout plone_group 4096 Dec 25 14:59 .
drwxr-sr-x. 6 plone_buildout plone_group 4096 Dec 25 14:59 ..
-rw-------. 1 plone_buildout plone_group 424 Dec 25 14:59 adminPassword.txt
-rw-------. 1 plone_buildout plone_group 8765 Dec 25 14:56 base.cfg
drwx--S---. 2 plone_buildout plone_group 4096 Dec 25 14:59 bin
-rw-------. 1 plone_buildout plone_group 10525 Dec 25 14:56 bootstrap.py
-rw-------. 1 plone_buildout plone_group 6812 Dec 25 14:56 buildout.cfg
-rw-------. 1 plone_buildout plone_group 4399 Dec 25 14:56 develop.cfg
drwxr-sr-x. 2 plone_buildout plone_group 4096 Dec 25 14:56 develop-eggs
-rw-------. 1 plone_buildout plone_group 18297 Dec 25 14:59 .installed.cfg
-rw-------. 1 plone_buildout plone_group 815 Dec 25 14:56 lxml_static.cfg
drwxr-sr-x. 5 plone_buildout plone_group 4096 Dec 25 14:59 parts
drwx--S---. 2 plone_buildout plone_group 4096 Dec 25 14:56 products
-rw-r--r--. 1 plone_buildout plone_group 3469 Dec 25 14:59 README.html
drwx--S---. 3 plone_buildout plone_group 4096 Dec 25 14:56 src
drwxrws---. 7 plone_buildout plone_group 4096 Dec 25 14:59 var
-rw-------. 1 plone_buildout plone_group 9521 Dec 25 14:56 versions.cfg
-rw-------. 1 plone_buildout plone_group 1902 Dec 25 14:56 zopeapp-versions.cfg
-rw-------. 1 plone_buildout plone_group 1022 Dec 25 14:56 zope-versions.cfg
-rw-------. 1 plone_buildout plone_group 2518 Dec 25 14:56 ztk-versions.cfg
[root@localhost Plone]#
答案 0 :(得分:0)
它看起来肯定是权限问题。可能与Fedora安全策略有关。
老实说:确实有没有的理由以root身份安装Plone。请继续将其安装为普通(专用但非万能)用户帐户。这将在以后缓解你的许多问题。