Hide Forgot
`gluster volume geo-replication <master> <slave> config` assume that the slave has gsyncd binary under /usr/local, not true when using debian binary package. I got a working georeplication manually changing /etc/glusterd/geo-replication/gsyncd.conf to: remote_gsyncd = /usr/lib/glusterfs/glusterfs/gsyncd This is the error I was getting: [2011-05-20 15:30:19.641797] I [gsyncd:287:main_i] <top>: syncing: gluster://localhost:volume1 -> ssh://192.168.178.13:/srv/data [2011-05-20 15:30:24.791280] E [syncdutils:131:log_raise_exception] <top>: FAIL: Traceback (most recent call last): File "/usr/lib/glusterfs/glusterfs/python/syncdaemon/syncdutils.py", line 152, in twrap tf(*aa) File "/usr/lib/glusterfs/glusterfs/python/syncdaemon/repce.py", line 118, in listen rid, exc, res = recv(self.inf) File "/usr/lib/glusterfs/glusterfs/python/syncdaemon/repce.py", line 42, in recv return pickle.load(inf) EOFError
Giovanni, you are supposed to configure the geo-rep master/slave pair appropriately before starting the geo-rep session. So the phenomenon as you met with it is not a bug. Still your case raises some things to think over: - we could install a convenience symlink to gsyncd at the default [prefix-less build] gsyncd path (/usr/local/libexec/glusterfs/gsyncd), like we do for rpm-s but I fear that would be intrusive to debian fs layout, so I still think it's better to fall back to the requirement of manual initial configuration - yes, the error shown is not user-friendly. We want to improve on that (http://bugs.gluster.com/show_bug.cgi?id=2778) - the deb was not updated for 3.2.0; it could do with some refinements (eg. add python dependency for geo-replication). Csaba
*** Bug 2967 has been marked as a duplicate of this bug. ***
creating a symlink on the postinst script of deb seems to be working. -------------- #cat debian/postinst #!/bin/sh # postinst script for glusterfs # # see: dh_installdeb(1) set -e case "$1" in configure) mkdir -p /usr/local/libexec/glusterfs/ ln -s /usr/lib/glusterfs/glusterfs/gsyncd /usr/local/libexec/glusterfs/gsyncd ;; --------------
(In reply to comment #3) > creating a symlink on the postinst script of deb seems to be working. This sentence is subtly interwoven with underlying assumption of a bug being faced here. As of my agenda, there is no bug, the program is just needed to be configured properly (although a bug can exist at documentation level, by not making this clear). I'm not adamantly fixed on this agenda, it's possible to argue against it. Just please relate to this statement first, before trying to provide workarounds.
this issue becomes irrelevant since new changes are implemented with the bug 764557 regarding geo-rep setup.