Problems starting ZEO with zeoctl
I am receiving error messages when attempting to start ZEO in daemon mode. I have setup ZEO according to: http://plone.org/documentation/tutorial/robust-installation I have tried the Plone setup list, but their suggestions (changing the permissions on zeo/log/ and related files) did not lead to a resolution. I receive an error message and a progressive series of dots when I attempt to start ZEO: [zope@localhost zope]$ zeo/bin/zeoctl start . Traceback (most recent call last): File "/opt/zope/zope/lib/python/zdaemon/zdrun.py", line 719, in ? main() File "/opt/zope/zope/lib/python/zdaemon/zdrun.py", line 716, in main d.main(args) File "/opt/zope/zope/lib/python/zdaemon/zdrun.py", line 243, in main self.run() File "/opt/zope/zope/lib/python/zdaemon/zdrun.py", line 256, in run self.opensocket() File "/opt/zope/zope/lib/python/zdaemon/zdrun.py", line 278, in opensocket sock.bind(tempname) File "<string>", line 1, in bind socket.error: (13, 'Permission denied') . . . . . . . . [dots continue to appear at a regular interval] If I start ZEO using: zeo/bin/runzeo then all is fine, the Zope clients connect, etc. but it logs to the console and I want to run in daemon mode. I am using: Plone 2.5 Zope 2.9.4 Python 2.4.3 CentOS 3.7 TIA, Ben
----- Original Message ----- From: "Ben" <shadroth@gmail.com> To: <zope@zope.org> Sent: Saturday, September 02, 2006 2:13 AM Subject: [Zope] Problems starting ZEO with zeoctl
I am receiving error messages when attempting to start ZEO in daemon mode.
I have setup ZEO according to: http://plone.org/documentation/tutorial/robust-installation I have tried the Plone setup list, but their suggestions (changing the permissions on zeo/log/ and related files) did not lead to a resolution.
I receive an error message and a progressive series of dots when I attempt to start ZEO:
[zope@localhost zope]$ zeo/bin/zeoctl start . Traceback (most recent call last): File "/opt/zope/zope/lib/python/zdaemon/zdrun.py", line 719, in ? main() File "/opt/zope/zope/lib/python/zdaemon/zdrun.py", line 716, in main d.main(args) File "/opt/zope/zope/lib/python/zdaemon/zdrun.py", line 243, in main self.run() File "/opt/zope/zope/lib/python/zdaemon/zdrun.py", line 256, in run self.opensocket() File "/opt/zope/zope/lib/python/zdaemon/zdrun.py", line 278, in opensocket sock.bind(tempname) File "<string>", line 1, in bind socket.error: (13, 'Permission denied') . . . . . . . . [dots continue to appear at a regular interval]
If I start ZEO using: zeo/bin/runzeo
then all is fine, the Zope clients connect, etc. but it logs to the console and I want to run in daemon mode.
I am using: Plone 2.5 Zope 2.9.4 Python 2.4.3 CentOS 3.7
What port is zeo configured to use and what 'user' are you running as when you run zeoctl? Jonathan
On 9/2/06, Jonathan <dev101@magma.ca> wrote:
What port is zeo configured to use and what 'user' are you running as when you run zeoctl?
ZEO is configured to use port 8100 (the default, I believe). I run 'zeoctl start' as user 'zope' unsucessfully, but I can run 'runzeo' as user 'zope' without any hassles. I'm not sure what permissions are involved, but it occurred to me that Red Hat's user private group system might be what's messing things up for me (and why it works for users of other distros), but I don't know enough about Zope or ZEO to check if this is the case. Ben
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ben wrote:
I am receiving error messages when attempting to start ZEO in daemon mode.
I have setup ZEO according to: http://plone.org/documentation/tutorial/robust-installation I have tried the Plone setup list, but their suggestions (changing the permissions on zeo/log/ and related files) did not lead to a resolution.
I receive an error message and a progressive series of dots when I attempt to start ZEO:
[zope@localhost zope]$ zeo/bin/zeoctl start . Traceback (most recent call last): File "/opt/zope/zope/lib/python/zdaemon/zdrun.py", line 719, in ? main() File "/opt/zope/zope/lib/python/zdaemon/zdrun.py", line 716, in mainxxxxx File "/opt/zope/zope/lib/python/zdaemon/zdrun.py", line 256, in run self.opensocket() File "/opt/zope/zope/lib/python/zdaemon/zdrun.py", line 278, in opensocket sock.bind(tempname) File "<string>", line 1, in bind socket.error: (13, 'Permission denied') . . . . . . . . [dots continue to appear at a regular interval]
If I start ZEO using: zeo/bin/runzeo
then all is fine, the Zope clients connect, etc. but it logs to the console and I want to run in daemon mode.
I am using: Plone 2.5 Zope 2.9.4 Python 2.4.3 CentOS 3.7
The permission needed here is for the "effective" user to write to the "ZEO control socket", which is normally in the 'etc' direcdtory of your instance home, and named 'zeo.zdsock'. Try changing 'zeo.conf' to put that file in your 'var' directory, where you *must* be able to create files (otherwise you wouldn't be able to use 'runzeo'). Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE+bNy+gerLs4ltQ4RAvmPAJ9DDR9/vX5umajLE2CWoss9U4ZQJQCgsvYd pHVsOxk7qLdeoSfHGoqFPzM= =Ngq6 -----END PGP SIGNATURE-----
Tres Seaver wrote:
The permission needed here is for the "effective" user to write to the "ZEO control socket", which is normally in the 'etc' direcdtory of your instance home, and named 'zeo.zdsock'. Try changing 'zeo.conf' to put that file in your 'var' directory, where you *must* be able to create files (otherwise you wouldn't be able to use 'runzeo').
...and, to be fair, check if there's anything in the zeo event log :-) Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On 9/2/06, Tres Seaver <tseaver@palladion.com> wrote:
The permission needed here is for the "effective" user to write to the "ZEO control socket", which is normally in the 'etc' direcdtory of your instance home, and named 'zeo.zdsock'. Try changing 'zeo.conf' to put that file in your 'var' directory, where you *must* be able to create files (otherwise you wouldn't be able to use 'runzeo').
I keep meaning to file a bug and patch to change the default location of the socket file to the var/ dir like zopectl does. The effective ZEO user should not be able to write in my etc/ dir, thank you very much! -- Martijn Pieters
On 9/3/06, Tres Seaver <tseaver@palladion.com> wrote:
The permission needed here is for the "effective" user to write to the "ZEO control socket", which is normally in the 'etc' direcdtory of your instance home, and named 'zeo.zdsock'. Try changing 'zeo.conf' to put that file in your 'var' directory, where you *must* be able to create files (otherwise you wouldn't be able to use 'runzeo').
This fixed it. Thankyou, Ben
participants (5)
-
Ben -
Chris Withers -
Jonathan -
Martijn Pieters -
Tres Seaver