hi Sunny, Passwordless ssh to : ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-replication/secret.pem -p 22 [email protected]
is login, but when the whole command is run getting permission issues again:: ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-replication/secret.pem -p 22 [email protected] gluster --xml --remote-host=localhost volume info vol_a5aee81a873c043c99a938adcb5b5781 -v ERROR: failed to create logfile "/var/log/glusterfs/cli.log" (Permission denied) ERROR: failed to open logfile /var/log/glusterfs/cli.log any idea here ? thanks, Maurya On Thu, Mar 21, 2019 at 2:43 PM Maurya M <[email protected]> wrote: > hi Sunny, > i did use the [1] link for the setup, when i encountered this error > during ssh-copy-id : (so setup the passwordless ssh, by manually copied the > private/ public keys to all the nodes , both master & slave) > > [root@k8s-agentpool1-24779565-1 ~]# ssh-copy-id [email protected] > /usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: > "/root/.ssh/id_rsa.pub" > The authenticity of host ' xxx.xx.xxx.x ( xxx.xx.xxx.x )' can't be > established. > ECDSA key fingerprint is > SHA256:B2rNaocIcPjRga13oTnopbJ5KjI/7l5fMANXc+KhA9s. > ECDSA key fingerprint is > MD5:1b:70:f9:7a:bf:35:33:47:0c:f2:c1:cd:21:e2:d3:75. > Are you sure you want to continue connecting (yes/no)? yes > /usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to > filter out any that are already installed > /usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are > prompted now it is to install the new keys > Permission denied (publickey). > > To start afresh what all needs to teardown / delete, do we have any script > for it ? where all the pem keys do i need to delete? > > thanks, > Maurya > > On Thu, Mar 21, 2019 at 2:12 PM Sunny Kumar <[email protected]> wrote: > >> Hey you can start a fresh I think you are not following proper setup >> steps. >> >> Please follow these steps [1] to create geo-rep session, you can >> delete the old one and do a fresh start. Or alternative you can use >> this tool[2] to setup geo-rep. >> >> >> [1]. >> https://docs.gluster.org/en/latest/Administrator%20Guide/Geo%20Replication/ >> [2]. http://aravindavk.in/blog/gluster-georep-tools/ >> >> >> /Sunny >> >> On Thu, Mar 21, 2019 at 11:28 AM Maurya M <[email protected]> wrote: >> > >> > Hi Sunil, >> > I did run the on the slave node : >> > /usr/libexec/glusterfs/set_geo_rep_pem_keys.sh azureuser >> vol_041afbc53746053368a1840607636e97 vol_a5aee81a873c043c99a938adcb5b5781 >> > getting this message "/home/azureuser/common_secret.pem.pub not >> present. Please run geo-replication command on master with push-pem option >> to generate the file" >> > >> > So went back and created the session again, no change, so manually >> copied the common_secret.pem.pub to /home/azureuser/ but still the >> set_geo_rep_pem_keys.sh is looking the pem file in different name : >> COMMON_SECRET_PEM_PUB=${master_vol}_${slave_vol}_common_secret.pem.pub , >> change the name of pem , ran the command again : >> > >> > /usr/libexec/glusterfs/set_geo_rep_pem_keys.sh azureuser >> vol_041afbc53746053368a1840607636e97 vol_a5aee81a873c043c99a938adcb5b5781 >> > Successfully copied file. >> > Command executed successfully. >> > >> > >> > - went back and created the session , start the geo-replication , still >> seeing the same error in logs. Any ideas ? >> > >> > thanks, >> > Maurya >> > >> > >> > >> > On Wed, Mar 20, 2019 at 11:07 PM Sunny Kumar <[email protected]> >> wrote: >> >> >> >> Hi Maurya, >> >> >> >> I guess you missed last trick to distribute keys in slave node. I see >> >> this is non-root geo-rep setup so please try this: >> >> >> >> >> >> Run the following command as root in any one of Slave node. >> >> >> >> /usr/local/libexec/glusterfs/set_geo_rep_pem_keys.sh <slave_user> >> >> <master_volume> <slave_volume> >> >> >> >> - Sunny >> >> >> >> On Wed, Mar 20, 2019 at 10:47 PM Maurya M <[email protected]> wrote: >> >> > >> >> > Hi all, >> >> > Have setup a 3 master nodes - 3 slave nodes (gluster 4.1) for >> geo-replication, but once have the geo-replication configure the status is >> always on "Created', >> >> > even after have force start the session. >> >> > >> >> > On close inspect of the logs on the master node seeing this error: >> >> > >> >> > "E [syncdutils(monitor):801:errlog] Popen: command returned error >> cmd=ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no -i >> /var/lib/glusterd/geo-replication/secret.pem -p 22 [email protected]. >> gluster --xml --remote-host=localhost volume info >> vol_a5ae34341a873c043c99a938adcb5b5781 error=255" >> >> > >> >> > Any ideas what is issue? >> >> > >> >> > thanks, >> >> > Maurya >> >> > >> >> > _______________________________________________ >> >> > Gluster-users mailing list >> >> > [email protected] >> >> > https://lists.gluster.org/mailman/listinfo/gluster-users >> >
_______________________________________________ Gluster-users mailing list [email protected] https://lists.gluster.org/mailman/listinfo/gluster-users
