<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">hi Aravinda,<div> had the session created using : create ssh-port 2222 push-pem and also the :</div><div><br></div><div>gluster volume geo-replication vol_75a5fd373d88ba687f591f3353fa05cf 172.16.201.35::vol_e783a730578e45ed9d51b9a80df6c33f config ssh-port 2222<br></div><div><br></div><div>hitting this message:</div><div><div>geo-replication config-set failed for vol_75a5fd373d88ba687f591f3353fa05cf 172.16.201.35::vol_e783a730578e45ed9d51b9a80df6c33f</div><div>geo-replication command failed</div></div><div><br></div><div>Below is snap of status:</div><div><br></div><div><div>[root@k8s-agentpool1-24779565-1 vol_75a5fd373d88ba687f591f3353fa05cf_172.16.201.35_vol_e783a730578e45ed9d51b9a80df6c33f]# gluster volume geo-replication vol_75a5fd373d88ba687f591f3353fa05cf 172.16.201.35::vol_e783a730578e45ed9d51b9a80df6c33f status</div><div><br></div><div>MASTER NODE MASTER VOL MASTER BRICK SLAVE USER SLAVE SLAVE NODE STATUS CRAWL STATUS LAST_SYNCED</div><div>--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------</div><div>172.16.189.4 vol_75a5fd373d88ba687f591f3353fa05cf /var/lib/heketi/mounts/vg_aee3df7b0bb2451bc00a73358c5196a2/brick_116fb9427fb26f752d9ba8e45e183cb1/brick root 172.16.201.35::vol_e783a730578e45ed9d51b9a80df6c33f N/A Created N/A N/A</div><div>172.16.189.35 vol_75a5fd373d88ba687f591f3353fa05cf /var/lib/heketi/mounts/vg_05708751110fe60b3e7da15bdcf6d4d4/brick_266bb08f0d466d346f8c0b19569736fb/brick root 172.16.201.35::vol_e783a730578e45ed9d51b9a80df6c33f N/A Created N/A N/A</div><div>172.16.189.66 vol_75a5fd373d88ba687f591f3353fa05cf /var/lib/heketi/mounts/vg_4b92a2b687e59b7311055d3809b77c06/brick_dfa44c9380cdedac708e27e2c2a443a0/brick root 172.16.201.35::vol_e783a730578e45ed9d51b9a80df6c33f N/A Created N/A N/A</div></div><div><br></div><div>any ideas ? where can find logs for the failed commands check in gysncd.log , the trace is as below:</div><div><br></div><div><div>[2019-03-25 04:04:42.295043] I [gsyncd(monitor):297:main] <top>: Using session config file path=/var/lib/glusterd/geo-replication/vol_75a5fd373d88ba687f591f3353fa05cf_172.16.201.35_vol_e783a730578e45ed9d51b9a80df6c33f/gsyncd.conf</div><div>[2019-03-25 04:04:42.387192] E [syncdutils(monitor):332:log_raise_exception] <top>: FAIL:</div><div>Traceback (most recent call last):</div><div> File "/usr/libexec/glusterfs/python/syncdaemon/gsyncd.py", line 311, in main</div><div> func(args)</div><div> File "/usr/libexec/glusterfs/python/syncdaemon/subcmds.py", line 50, in subcmd_monitor</div><div> return monitor.monitor(local, remote)</div><div> File "/usr/libexec/glusterfs/python/syncdaemon/monitor.py", line 427, in monitor</div><div> return Monitor().multiplex(*distribute(local, remote))</div><div> File "/usr/libexec/glusterfs/python/syncdaemon/monitor.py", line 370, in distribute</div><div> mvol = Volinfo(master.volume, master.host)</div><div> File "/usr/libexec/glusterfs/python/syncdaemon/syncdutils.py", line 860, in __init__</div><div> print "debug varible " %vix</div><div>TypeError: not all arguments converted during string formatting</div><div>[2019-03-25 04:04:48.997519] I [gsyncd(config-get):297:main] <top>: Using session config file path=/var/lib/glusterd/geo-replication/vol_75a5fd373d88ba687f591f3353fa05cf_172.16.201.35_vol_e783a730578e45ed9d51b9a80df6c33f/gsyncd.conf</div><div>[2019-03-25 04:04:49.93528] I [gsyncd(status):297:main] <top>: Using session config file path=/var/lib/glusterd/geo-replication/vol_75a5fd373d88ba687f591f3353fa05cf_172.16.201.35_vol_e783a730578e45ed9d51b9a80df6c33f/gsyncd.conf</div><div>[2019-03-25 04:08:07.194348] I [gsyncd(config-get):297:main] <top>: Using session config file path=/var/lib/glusterd/geo-replication/vol_75a5fd373d88ba687f591f3353fa05cf_172.16.201.35_vol_e783a730578e45ed9d51b9a80df6c33f/gsyncd.conf</div><div>[2019-03-25 04:08:07.262588] I [gsyncd(config-get):297:main] <top>: Using session config file path=/var/lib/glusterd/geo-replication/vol_75a5fd373d88ba687f591f3353fa05cf_172.16.201.35_vol_e783a730578e45ed9d51b9a80df6c33f/gsyncd.conf</div><div>[2019-03-25 04:08:07.550080] I [gsyncd(config-get):297:main] <top>: Using session config file path=/var/lib/glusterd/geo-replication/vol_75a5fd373d88ba687f591f3353fa05cf_172.16.201.35_vol_e783a730578e45ed9d51b9a80df6c33f/gsyncd.conf</div><div>[2019-03-25 04:08:18.933028] I [gsyncd(config-get):297:main] <top>: Using session config file path=/var/lib/glusterd/geo-replication/vol_75a5fd373d88ba687f591f3353fa05cf_172.16.201.35_vol_e783a730578e45ed9d51b9a80df6c33f/gsyncd.conf</div><div>[2019-03-25 04:08:19.25285] I [gsyncd(status):297:main] <top>: Using session config file path=/var/lib/glusterd/geo-replication/vol_75a5fd373d88ba687f591f3353fa05cf_172.16.201.35_vol_e783a730578e45ed9d51b9a80df6c33f/gsyncd.conf</div><div>[2019-03-25 04:09:15.766882] I [gsyncd(config-get):297:main] <top>: Using session config file path=/var/lib/glusterd/geo-replication/vol_75a5fd373d88ba687f591f3353fa05cf_172.16.201.35_vol_e783a730578e45ed9d51b9a80df6c33f/gsyncd.conf</div><div>[2019-03-25 04:09:16.30267] I [gsyncd(config-get):297:main] <top>: Using session config file path=/var/lib/glusterd/geo-replication/vol_75a5fd373d88ba687f591f3353fa05cf_172.16.201.35_vol_e783a730578e45ed9d51b9a80df6c33f/gsyncd.conf</div><div>[2019-03-25 04:09:16.89006] I [gsyncd(config-set):297:main] <top>: Using session config file path=/var/lib/glusterd/geo-replication/vol_75a5fd373d88ba687f591f3353fa05cf_172.16.201.35_vol_e783a730578e45ed9d51b9a80df6c33f/gsyncd.conf</div></div><div><br></div><div>regards,</div><div>Maurya</div></div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Mar 25, 2019 at 9:08 AM Aravinda <<a href="mailto:avishwan@redhat.com">avishwan@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Use `ssh-port <port>` while creating the Geo-rep session<br>
<br>
Ref: <br>
<a href="https://docs.gluster.org/en/latest/Administrator%20Guide/Geo%20Replication/#creating-the-session" rel="noreferrer" target="_blank">https://docs.gluster.org/en/latest/Administrator%20Guide/Geo%20Replication/#creating-the-session</a><br>
<br>
And set the ssh-port option before start.<br>
<br>
```<br>
gluster volume geo-replication <master_volume> \<br>
[<slave_user>@]<slave_host>::<slave_volume> config<br>
ssh-port 2222<br>
```<br>
<br>
-- <br>
regards<br>
Aravinda<br>
<a href="http://aravindavk.in" rel="noreferrer" target="_blank">http://aravindavk.in</a><br>
<br>
<br>
On Sun, 2019-03-24 at 17:13 +0530, Maurya M wrote:<br>
> did all the suggestion as mentioned in the log trace , have another<br>
> setup using root user , but there i have issue on the ssh command as<br>
> i am unable to change the ssh port to use default 22, but my servers<br>
> (azure aks engine) are configure to using 2222 where i am unable to<br>
> change the ports , restart of ssh service giving me error!<br>
> <br>
> Is this syntax correct to config the ssh-command:<br>
> gluster volume geo-replication vol_041afbc53746053368a1840607636e97<br>
> xxx.xx.xxx.xx::vol_a5aee81a873c043c99a938adcb5b5781 config ssh-<br>
> command '/usr/sbin/sshd -D -p 2222'<br>
> <br>
> On Sun, Mar 24, 2019 at 4:38 PM Maurya M <<a href="mailto:mauryam@gmail.com" target="_blank">mauryam@gmail.com</a>> wrote:<br>
> > Did give the persmission on both "/var/log/glusterfs/" &<br>
> > "/var/lib/glusterd/" too, but seems the directory where i mounted<br>
> > using heketi is having issues:<br>
> > <br>
> > [2019-03-22 09:48:21.546308] E [syncdutils(worker<br>
> > /var/lib/heketi/mounts/vg_aee3df7b0bb2451bc00a73358c5196a2/brick_b3<br>
> > eab2394433f02f5617012d4ae3c28f/brick):305:log_raise_exception]<br>
> > <top>: connection to peer is broken<br>
> > [2019-03-22 09:48:21.546662] E [syncdutils(worker<br>
> > /var/lib/heketi/mounts/vg_aee3df7b0bb2451bc00a73358c5196a2/brick_b3<br>
> > eab2394433f02f5617012d4ae3c28f/brick):309:log_raise_exception]<br>
> > <top>: getting "No such file or directory"errors is most likely due<br>
> > to MISCONFIGURATION, please remove all the public keys added by<br>
> > geo-replication from authorized_keys file in slave nodes and run<br>
> > Geo-replication create command again.<br>
> > [2019-03-22 09:48:21.546736] E [syncdutils(worker<br>
> > /var/lib/heketi/mounts/vg_aee3df7b0bb2451bc00a73358c5196a2/brick_b3<br>
> > eab2394433f02f5617012d4ae3c28f/brick):316:log_raise_exception]<br>
> > <top>: If `gsec_create container` was used, then run `gluster<br>
> > volume geo-replication <MASTERVOL><br>
> > [<SLAVEUSER>@]<SLAVEHOST>::<SLAVEVOL> config remote-gsyncd<br>
> > <GSYNCD_PATH> (Example GSYNCD_PATH:<br>
> > `/usr/libexec/glusterfs/gsyncd`)<br>
> > [2019-03-22 09:48:21.546858] E [syncdutils(worker<br>
> > /var/lib/heketi/mounts/vg_aee3df7b0bb2451bc00a73358c5196a2/brick_b3<br>
> > eab2394433f02f5617012d4ae3c28f/brick):801:errlog] Popen: command<br>
> > returned error cmd=ssh -oPasswordAuthentication=no<br>
> > -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-<br>
> > replication/secret.pem -p 22 -oControlMaster=auto -S /tmp/gsyncd-<br>
> > aux-ssh-OaPGc3/c784230c9648efa4d529975bd779c551.sock <br>
> > <a href="mailto:azureuser@172.16.201.35" target="_blank">azureuser@172.16.201.35</a> /nonexistent/gsyncd slave<br>
> > vol_041afbc53746053368a1840607636e97 azureuser@172.16.201.35::vol_a<br>
> > 5aee81a873c043c99a938adcb5b5781 --master-node 172.16.189.4 --<br>
> > master-node-id dd4efc35-4b86-4901-9c00-483032614c35 --master-brick<br>
> > /var/lib/heketi/mounts/vg_aee3df7b0bb2451bc00a73358c5196a2/brick_b3<br>
> > eab2394433f02f5617012d4ae3c28f/brick --local-node 172.16.201.35 --<br>
> > local-node-id 7eb0a2b6-c4d6-41b1-a346-0638dbf8d779 --slave-timeout<br>
> > 120 --slave-log-level INFO --slave-gluster-log-level INFO --slave-<br>
> > gluster-command-dir /usr/sbin error=127<br>
> > [2019-03-22 09:48:21.546977] E [syncdutils(worker<br>
> > /var/lib/heketi/mounts/vg_aee3df7b0bb2451bc00a73358c5196a2/brick_b3<br>
> > eab2394433f02f5617012d4ae3c28f/brick):805:logerr] Popen: ssh> bash:<br>
> > /nonexistent/gsyncd: No such file or directory<br>
> > [2019-03-22 09:48:21.565583] I [repce(agent<br>
> > /var/lib/heketi/mounts/vg_aee3df7b0bb2451bc00a73358c5196a2/brick_b3<br>
> > eab2394433f02f5617012d4ae3c28f/brick):80:service_loop] RepceServer:<br>
> > terminating on reaching EOF.<br>
> > [2019-03-22 09:48:21.565745] I [monitor(monitor):266:monitor]<br>
> > Monitor: worker died before establishing connection <br>
> > brick=/var/lib/heketi/mounts/vg_aee3df7b0bb2451bc00a73358c5196a2/br<br>
> > ick_b3eab2394433f02f5617012d4ae3c28f/brick<br>
> > [2019-03-22 09:48:21.579195] I<br>
> > [gsyncdstatus(monitor):245:set_worker_status] GeorepStatus: Worker<br>
> > Status Change status=Faulty<br>
> > <br>
> > On Fri, Mar 22, 2019 at 10:23 PM Sunny Kumar <<a href="mailto:sunkumar@redhat.com" target="_blank">sunkumar@redhat.com</a>><br>
> > wrote:<br>
> > > Hi Maurya,<br>
> > > <br>
> > > Looks like hook script is failed to set permissions for azureuser<br>
> > > on<br>
> > > "/var/log/glusterfs".<br>
> > > You can assign permission manually for directory then it will<br>
> > > work.<br>
> > > <br>
> > > -Sunny<br>
> > > <br>
> > > On Fri, Mar 22, 2019 at 2:07 PM Maurya M <<a href="mailto:mauryam@gmail.com" target="_blank">mauryam@gmail.com</a>><br>
> > > wrote:<br>
> > > ><br>
> > > > hi Sunny,<br>
> > > > Passwordless ssh to :<br>
> > > ><br>
> > > > ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no -i<br>
> > > /var/lib/glusterd/geo-replication/secret.pem -p 22 <br>
> > > <a href="mailto:azureuser@172.16.201.35" target="_blank">azureuser@172.16.201.35</a><br>
> > > ><br>
> > > > is login, but when the whole command is run getting permission<br>
> > > issues again::<br>
> > > ><br>
> > > > ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no -i<br>
> > > /var/lib/glusterd/geo-replication/secret.pem -p 22 <br>
> > > <a href="mailto:azureuser@172.16.201.35" target="_blank">azureuser@172.16.201.35</a> gluster --xml --remote-host=localhost<br>
> > > volume info vol_a5aee81a873c043c99a938adcb5b5781 -v<br>
> > > > ERROR: failed to create logfile "/var/log/glusterfs/cli.log"<br>
> > > (Permission denied)<br>
> > > > ERROR: failed to open logfile /var/log/glusterfs/cli.log<br>
> > > ><br>
> > > > any idea here ?<br>
> > > ><br>
> > > > thanks,<br>
> > > > Maurya<br>
> > > ><br>
> > > ><br>
> > > > On Thu, Mar 21, 2019 at 2:43 PM Maurya M <<a href="mailto:mauryam@gmail.com" target="_blank">mauryam@gmail.com</a>><br>
> > > wrote:<br>
> > > >><br>
> > > >> hi Sunny,<br>
> > > >> i did use the [1] link for the setup, when i encountered this<br>
> > > error during ssh-copy-id : (so setup the passwordless ssh, by<br>
> > > manually copied the private/ public keys to all the nodes , both<br>
> > > master & slave)<br>
> > > >><br>
> > > >> [root@k8s-agentpool1-24779565-1 ~]# ssh-copy-id <br>
> > > geouser@xxx.xx.xxx.x<br>
> > > >> /usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed:<br>
> > > "/root/.ssh/id_rsa.pub"<br>
> > > >> The authenticity of host ' xxx.xx.xxx.x ( xxx.xx.xxx.x )'<br>
> > > can't be established.<br>
> > > >> ECDSA key fingerprint is<br>
> > > SHA256:B2rNaocIcPjRga13oTnopbJ5KjI/7l5fMANXc+KhA9s.<br>
> > > >> ECDSA key fingerprint is<br>
> > > MD5:1b:70:f9:7a:bf:35:33:47:0c:f2:c1:cd:21:e2:d3:75.<br>
> > > >> Are you sure you want to continue connecting (yes/no)? yes<br>
> > > >> /usr/bin/ssh-copy-id: INFO: attempting to log in with the new<br>
> > > key(s), to filter out any that are already installed<br>
> > > >> /usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed --<br>
> > > if you are prompted now it is to install the new keys<br>
> > > >> Permission denied (publickey).<br>
> > > >><br>
> > > >> To start afresh what all needs to teardown / delete, do we<br>
> > > have any script for it ? where all the pem keys do i need to<br>
> > > delete?<br>
> > > >><br>
> > > >> thanks,<br>
> > > >> Maurya<br>
> > > >><br>
> > > >> On Thu, Mar 21, 2019 at 2:12 PM Sunny Kumar <<br>
> > > <a href="mailto:sunkumar@redhat.com" target="_blank">sunkumar@redhat.com</a>> wrote:<br>
> > > >>><br>
> > > >>> Hey you can start a fresh I think you are not following<br>
> > > proper setup steps.<br>
> > > >>><br>
> > > >>> Please follow these steps [1] to create geo-rep session, you<br>
> > > can<br>
> > > >>> delete the old one and do a fresh start. Or alternative you<br>
> > > can use<br>
> > > >>> this tool[2] to setup geo-rep.<br>
> > > >>><br>
> > > >>><br>
> > > >>> [1]. <br>
> > > <a href="https://docs.gluster.org/en/latest/Administrator%20Guide/Geo%20Replication/" rel="noreferrer" target="_blank">https://docs.gluster.org/en/latest/Administrator%20Guide/Geo%20Replication/</a><br>
> > > >>> [2]. <a href="http://aravindavk.in/blog/gluster-georep-tools/" rel="noreferrer" target="_blank">http://aravindavk.in/blog/gluster-georep-tools/</a><br>
> > > >>><br>
> > > >>><br>
> > > >>> /Sunny<br>
> > > >>><br>
> > > >>> On Thu, Mar 21, 2019 at 11:28 AM Maurya M <<a href="mailto:mauryam@gmail.com" target="_blank">mauryam@gmail.com</a>><br>
> > > wrote:<br>
> > > >>> ><br>
> > > >>> > Hi Sunil,<br>
> > > >>> > I did run the on the slave node :<br>
> > > >>> > /usr/libexec/glusterfs/set_geo_rep_pem_keys.sh azureuser<br>
> > > vol_041afbc53746053368a1840607636e97<br>
> > > vol_a5aee81a873c043c99a938adcb5b5781<br>
> > > >>> > getting this message "/home/azureuser/common_secret.pem.pub<br>
> > > not present. Please run geo-replication command on master with<br>
> > > push-pem option to generate the file"<br>
> > > >>> ><br>
> > > >>> > So went back and created the session again, no change, so<br>
> > > manually copied the common_secret.pem.pub to /home/azureuser/ but<br>
> > > still the set_geo_rep_pem_keys.sh is looking the pem file in<br>
> > > different name : <br>
> > > COMMON_SECRET_PEM_PUB=${master_vol}_${slave_vol}_<a href="http://common_secret.pe" rel="noreferrer" target="_blank">common_secret.pe</a><br>
> > > m.pub , change the name of pem , ran the command again :<br>
> > > >>> ><br>
> > > >>> > /usr/libexec/glusterfs/set_geo_rep_pem_keys.sh azureuser<br>
> > > vol_041afbc53746053368a1840607636e97<br>
> > > vol_a5aee81a873c043c99a938adcb5b5781<br>
> > > >>> > Successfully copied file.<br>
> > > >>> > Command executed successfully.<br>
> > > >>> ><br>
> > > >>> ><br>
> > > >>> > - went back and created the session , start the geo-<br>
> > > replication , still seeing the same error in logs. Any ideas ?<br>
> > > >>> ><br>
> > > >>> > thanks,<br>
> > > >>> > Maurya<br>
> > > >>> ><br>
> > > >>> ><br>
> > > >>> ><br>
> > > >>> > On Wed, Mar 20, 2019 at 11:07 PM Sunny Kumar <<br>
> > > <a href="mailto:sunkumar@redhat.com" target="_blank">sunkumar@redhat.com</a>> wrote:<br>
> > > >>> >><br>
> > > >>> >> Hi Maurya,<br>
> > > >>> >><br>
> > > >>> >> I guess you missed last trick to distribute keys in slave<br>
> > > node. I see<br>
> > > >>> >> this is non-root geo-rep setup so please try this:<br>
> > > >>> >><br>
> > > >>> >><br>
> > > >>> >> Run the following command as root in any one of Slave<br>
> > > node.<br>
> > > >>> >><br>
> > > >>> >> /usr/local/libexec/glusterfs/set_geo_rep_pem_keys.sh <br>
> > > <slave_user><br>
> > > >>> >> <master_volume> <slave_volume><br>
> > > >>> >><br>
> > > >>> >> - Sunny<br>
> > > >>> >><br>
> > > >>> >> On Wed, Mar 20, 2019 at 10:47 PM Maurya M <<br>
> > > <a href="mailto:mauryam@gmail.com" target="_blank">mauryam@gmail.com</a>> wrote:<br>
> > > >>> >> ><br>
> > > >>> >> > Hi all,<br>
> > > >>> >> > Have setup a 3 master nodes - 3 slave nodes (gluster<br>
> > > 4.1) for geo-replication, but once have the geo-replication<br>
> > > configure the status is always on "Created',<br>
> > > >>> >> > even after have force start the session.<br>
> > > >>> >> ><br>
> > > >>> >> > On close inspect of the logs on the master node seeing<br>
> > > this error:<br>
> > > >>> >> ><br>
> > > >>> >> > "E [syncdutils(monitor):801:errlog] Popen: command<br>
> > > returned error cmd=ssh -oPasswordAuthentication=no<br>
> > > -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-<br>
> > > replication/secret.pem -p 22 azureuser@xxxxx.xxxx..xxx. gluster<br>
> > > --xml --remote-host=localhost volume info<br>
> > > vol_a5ae34341a873c043c99a938adcb5b5781 error=255"<br>
> > > >>> >> ><br>
> > > >>> >> > Any ideas what is issue?<br>
> > > >>> >> ><br>
> > > >>> >> > thanks,<br>
> > > >>> >> > Maurya<br>
> > > >>> >> ><br>
> > > >>> >> > _______________________________________________<br>
> > > >>> >> > Gluster-users mailing list<br>
> > > >>> >> > <a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
> > > >>> >> > <a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
> <br>
> _______________________________________________<br>
> Gluster-users mailing list<br>
> <a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
> <a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
<br>
<br>
</blockquote></div>