Can't get ZEO running with zeoctl start
Hello all, I'm trying to install a ZEO server. I already have Zope working, the ZEO-clients installed and testing ZEO with "zeoctl fg" actually works fine - but "zeoctl start" gives me this error: . Traceback (most recent call last): File "/usr/local/deltaweb/zope/lib/python/zdaemon/zdrun.py", line 736, in ? main() File "/usr/local/deltaweb/zope/lib/python/zdaemon/zdrun.py", line 733, in main d.main(args) File "/usr/local/deltaweb/zope/lib/python/zdaemon/zdrun.py", line 232, in main self.run() File "/usr/local/deltaweb/zope/lib/python/zdaemon/zdrun.py", line 245, in run self.opensocket() File "/usr/local/deltaweb/zope/lib/python/zdaemon/zdrun.py", line 267, in opensocket sock.bind(tempname) File "<string>", line 1, in bind socket.error: (13, 'Permission denied') I tested it with users root and zope. The file permissions as far as I know are right. This is annoying because I would want to put zeoctl in init.d and use it with service/chkconfig. Zope 2.7.6, Python 2.3.5, running on RHEL4. Any ideas? -- Mikko Koivunen, IT-department Deltamarin Ltd Raisio, Finland
Am Donnerstag, den 08.09.2005, 08:40 +0300 schrieb Mikko Koivunen:
Hello all,
I'm trying to install a ZEO server. I already have Zope working, the ZEO-clients installed and testing ZEO with "zeoctl fg" actually works fine - but "zeoctl start" gives me this error:
...
opensocket sock.bind(tempname) File "<string>", line 1, in bind socket.error: (13, 'Permission denied')
I tested it with users root and zope. The file permissions as far as I know are right.
This is annoying because I would want to put zeoctl in init.d and use it with service/chkconfig. Zope 2.7.6, Python 2.3.5, running on RHEL4. Any ~~~~~ / ideas? / / I'd say check your SELINUX settings -----------------------/
HTH Tino
-----Original Message----- From: Tino Wildenhain [mailto:tino@wildenhain.de] Sent: 8. syyskuuta 2005 9:19 To: Mikko Koivunen Cc: Zope Subject: Re: [Zope] Can't get ZEO running with zeoctl start
opensocket sock.bind(tempname) File "<string>", line 1, in bind socket.error: (13, 'Permission denied') This is annoying because I would want to put zeoctl in init.d and use it with service/chkconfig. Zope 2.7.6, Python 2.3.5, running on RHEL4.
I'd say check your SELINUX settings -----------------------/
Hi, Thanks for the tip, but selinux is not even installed on the machine. -- Mikko Koivunen
On 8 Sep 2005, at 08:39, Mikko Koivunen wrote:
opensocket sock.bind(tempname) File "<string>", line 1, in bind socket.error: (13, 'Permission denied') This is annoying because I would want to put zeoctl in init.d and use it with service/chkconfig. Zope 2.7.6, Python 2.3.5, running on RHEL4.
Have you checked all file permissions to ensure that the user running Zope can use them? My guess would be that you broke permissions by running as root, which simply is not a good thing to do. Run Zope under a normal user account, and change file ownership to that user. Then don't put zeoctl into init.d, write a small wrapper around it that uses zeoctl. Here is what I use in init.d on my CentOS box, notice how you can change the user account used for starting up a service by passing "-- user FOO" to the daemon helper: ------------------------------------------------------------------------ ------ #!/bin/sh # Startup script for Zope client # chkconfig: 2345 93 03 # description: Start Zope Corp Zope Client # inspired by chrism 01/10/2001 # Source function library. . /etc/rc.d/init.d/functions instance="/path/to/InstanceHome" zopectl="$instance/bin/zopectl" [ -f $zopectl ] || exit 0 prog="Zope" start() { echo -n $"Starting $prog: " daemon --user zope $zopectl start RETVAL=$? echo return $RETVAL } stop() { echo -n $"Stopping $prog: " $zopectl stop RETVAL=$? echo return $RETVAL } case "$1" in start) start ;; stop) stop ;; restart) $zopectl restart ;; logtail) $zopectl logtail ;; rotate) $zopectl logreopen ;; *) echo $"Usage: $0 {start|stop|restart|logtail|rotate}" exit 1 esac ##exit $RETVAL ------------------------------------------------------------------------ ----- jens
-----Original Message----- From: zope-bounces@zope.org [mailto:zope-bounces@zope.org]On Behalf Of Jens Vagelpohl Sent: 8. syyskuuta 2005 10:56 To: Zope Subject: Re: [Zope] Can't get ZEO running with zeoctl start
Have you checked all file permissions to ensure that the user running Zope can use them? My guess would be that you broke permissions by running as root, which simply is not a good thing to do. Run Zope under a normal user account, and change file ownership to that user. Then don't put zeoctl into init.d, write a small wrapper around it that uses zeoctl.
Hi and thanks for the help, User zope can run "zeoctl fg" just fine, so I thought the permissions should be OK. I have them set according to this tutorial: http://plone.org/documentation/tutorial/robust-installation/installing-zope Thanks for the zopectl-wrapper script, it's a lot cleaner than the one I had made. :) I adapted it to zeoctl but the problem still remains, zeoctl start still doesn't work. BTW, I tried the zeo/bin/runzeo script and it works OK too. Is it still possible it would be a file permission thing, even if zeoctl fg and runzeo work? -- Mikko Koivunen
On 8 Sep 2005, at 09:28, Mikko Koivunen wrote:
Is it still possible it would be a file permission thing, even if zeoctl fg and runzeo work?
Yes. You should run something like "chown -R <zope-user>:<zope-user> / path/to/Instance" as root to make absolutely sure everything is indeed owned by the user you're running zope as. jens
-----Original Message----- From: zope-bounces@zope.org [mailto:zope-bounces@zope.org]On Behalf Of Jens Vagelpohl Sent: 8. syyskuuta 2005 11:55 To: Zope user list Subject: Re: [Zope] Can't get ZEO running with zeoctl start
Yes. You should run something like "chown -R <zope-user>:<zope-user> / path/to/Instance" as root to make absolutely sure everything is indeed owned by the user you're running zope as.
Chowning the full zeo/ tree to zope:zope indeed did the trick. I was hesitant to do that because the tutorials I read suggested to only chown the log/ and var/ dirs to user zope. But it works now. Thanks! -- Mikko Koivunen
On 8 Sep 2005, at 09:59, Mikko Koivunen wrote:
Yes. You should run something like "chown -R <zope-user>:<zope- user> / path/to/Instance" as root to make absolutely sure everything is indeed owned by the user you're running zope as.
Chowning the full zeo/ tree to zope:zope indeed did the trick. I was hesitant to do that because the tutorials I read suggested to only chown the log/ and var/ dirs to user zope. But it works now. Thanks!
What tutorials are those? I wouldn't mind auditing those. jens
-----Original Message----- From: zope-bounces@zope.org [mailto:zope-bounces@zope.org]On Behalf Of Jens Vagelpohl Sent: 8. syyskuuta 2005 12:21 To: Zope user list Subject: Re: [Zope] Can't get ZEO running with zeoctl start
Chowning the full zeo/ tree to zope:zope indeed did the trick. I was hesitant to do that because the tutorials I read suggested to only chown the log/ and var/ dirs to user zope. But it works now. Thanks! What tutorials are those? I wouldn't mind auditing those.
Actually should have said tutorial, because only one I used has wrong info. These two were my references: - Zope book, neither the 2.6 or the 2.7 dev version, does not mention permissions at all. This actually applies to most of the documentation I find on zope.org or google. - The plone.org robust installation tutorial apparenly has wrong info: http://plone.org/documentation/tutorial/robust-installation The latter one is the tutorial I mainly used because it fits my scenario perfecly. I get the feeling people do zope installation / configuration stuff as the zope user and thus don't have this problem. I have the habit of working as root or my own user account, then setting permissions and then using user accounts like zope or apache only for starting services. Maybe I just need change my habits. -- Mikko Koivunen
On 8 Sep 2005, at 11:00, Mikko Koivunen wrote:
I get the feeling people do zope installation / configuration stuff as the zope user and thus don't have this problem. I have the habit of working as root or my own user account, then setting permissions and then using user accounts like zope or apache only for starting services. Maybe I just need change my habits.
Working as root is indeed a bad habit in general which is worth changing... jens
participants (3)
-
Jens Vagelpohl -
Mikko Koivunen -
Tino Wildenhain