Gluster users - Mar 2015 - geo-replication create push-pem uses wrong gsyncd path on slave cluster's SSH authorized_keys

Hello,

I am setting up geo replication on Debian wheezy using the official 3.5.3
GlusterFS packages and noticed that when creating the geo-replication session
using the command:

gluster volume geo-replication myvol slavecluster::myvol create push-pem force

the authorized_keys SSH file (/root/.ssh/authorized_keys) on the slave cluster
uses the wrong path to the gsync command. I adds the following command:


command="/usr/libexec/glusterfs/gsyncd"

but on Debian not even /usr/libexec exists... The correcct path to gsyncd should
be the following:


command="/usr/lib/x86_64-linux-gnu/glusterfs/gsyncd"

Can someone please correct that for the next Debian package builds?

Regards
ML

Hi,

Thanks for reporting, will work on having correct path with push-pem 
command.

Created a Bug to track the progress. 
https://bugzilla.redhat.com/show_bug.cgi?id=1199885


--
regards
Aravinda

On 03/08/2015 01:12 AM, ML mail wrote:
> Hello,
>
> I am setting up geo replication on Debian wheezy using the official 3.5.3
GlusterFS packages and noticed that when creating the geo-replication session
using the command:
>
> gluster volume geo-replication myvol slavecluster::myvol create push-pem
force
>
> the authorized_keys SSH file (/root/.ssh/authorized_keys) on the slave
cluster uses the wrong path to the gsync command. I adds the following command:
>
>
> command="/usr/libexec/glusterfs/gsyncd"
>
> but on Debian not even /usr/libexec exists... The correcct path to gsyncd
should be the following:
>
>
> command="/usr/lib/x86_64-linux-gnu/glusterfs/gsyncd"
>
> Can someone please correct that for the next Debian package builds?
>
> Regards
> ML
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users