[Gluster-users] why is geo-rep so bloody impossible?

Kotresh Hiremath Ravishankar khiremat at redhat.com
Mon Feb 20 13:29:34 UTC 2017

This could happen if two same ssh-key pub keys one with "command=..." and one with out 
distributed to slave ~/.ssh/authorized_keys. Please check and remove the one without "command=..".
It should work. For passwordless SSH connection, a separate ssh key pair should be create.

Thanks and Regards,
Kotresh H R

----- Original Message -----
> From: "lejeczek" <peljasz at yahoo.co.uk>
> To: gluster-users at gluster.org
> Sent: Friday, February 17, 2017 8:39:48 PM
> Subject: [Gluster-users] why is geo-rep so bloody impossible?
> hi everyone,
> I've been browsing list's messages and it seems to me that users struggle, I
> do.
> I do what I thought was simple, I follow official docs.
> I, as root always do..
> ]$ gluster system:: execute gsec_create
> ]$ gluster volume geo-replication WORK create
> push-pem force
> ]$ gluster volume geo-replication WORK start
> and I see:
> 256:log_raise_exception] <top>: getting "No such file or directory"errors is
> most likely due to MISCONFIGURATION, please remove all the public keys added
> by geo-replication from authorized_keys file in slave nodes and run
> Geo-replication create command again.
> 263:log_raise_exception] <top>: If `gsec_create container` was used, then run
> `gluster volume geo-replication <MASTERVOL>
> [<SLAVEUSER>@]<SLAVEHOST>::<SLAVEVOL> config remote-gsyncd <GSYNCD_PATH>
> (Example GSYNCD_PATH: `/usr/libexec/glusterfs/gsyncd`)
> so I remove all command="tar.. from ~/.ssh/authorized_keys on the geo-repl
> slave, then recreate session on master, but.. naturally, unfortunately it
> was not that.
> So I tried config gsyncd only to see:
> ...
> ..Popen: command "ssh -oPasswordAuthentication=no.. returned with 1, saying:
> 0-cli: Started running /usr/sbin/gluster with version 3.8.8
> 0-cli: Connecting to remote glusterd at localhost
> [event-epoll.c:628:event_dispatch_epoll_worker] 0-epoll: Started thread with
> index 1
> [cli-cmd.c:130:cli_cmd_process] 0-: Exiting with: 110
> gsyncd initializaion failed
> and no idea where how to troubleshoot it further.
> for any help many thanks,
> L.
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users

More information about the Gluster-users mailing list