Re: geo-rep will not initialize

Strahil Nikolov <hunter86_bg@xxxxxxxxx> · Wed, 28 Aug 2024 22:20:05 +0000 (UTC)

        It seems the problem is not in you but in a deprecated python package.

The following link gave me a hint where to look at: https://issues.apache.org/jira/browse/SVN-4899

After replacing 'readfp' with 'read_file on both nodes:
/usr/libexec/glusterfs/python/syncdaemon/gsyncd.py
/usr/libexec/glusterfs/python/syncdaemon/gsyncdconfig.py

the push-pem (in my test case gluster volume geo-replication sourcevol geoaccount@glusterdest::destvol create ssh-port 2244 push-pem force) succeeded and then the rest of the commands in https://docs.redhat.com/en/documentation/red_hat_gluster_storage/3.5/html/administration_guide/sect-Preparing_to_Deploy_Geo-replication#Setting_Up_the_Environment_for_a_Secure_Geo-replication_Slave worke

d without any more issues and the georep was established:

root@glustersource:/mnt# gluster volume geo-replication sourcevol geoaccount@glusterdest::destvol status

PRIMARY NODE     PRIMARY VOL    PRIMARY BRICK          SECONDARY USER    SECONDARY                          SECONDARY NODE    STATUS    CRAWL STATUS       LAST_SYNCED                  
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
glustersource    sourcevol      /bricks/vol1/brick1    geoaccount        geoaccount@glusterdest::destvol                      Active    Changelog Crawl    2024-08-29 01:15:36

root@glustersource:/mnt# ls -l /mnt | wc -l
151

root@glusterdest:~# ls -l /mnt | wc -l
151

Best Regards,
Strahil Nikolov

                        В петък, 23 август 2024 г. в 14:58:50 ч. Гринуич+3, Karl Kleinpaste <karl@xxxxxxxxxxxxxx> написа:

    On 8/22/24 21:54, Gilberto Ferreira
      wrote:

      Perhaps you can use this tools:

        https://aravindavk.in/blog/gluster-georep-tools/

      I am using it with great success.

    I'll try anything once. In fact, I tried
      twice. It can't set up.

      First, the code has port 22 baked in. I mentioned earlier that my
      sshd listens on a nonstandard port.

      Looking at the code (gluster_georep_tools/setup/cli.py,
      glustercli/cli/georep.py), there is provision within functions for
      a different port, but there is no way that I see to use that in
      command line args.

      Oddly shortsighted, or maybe I'm missing something.

      So second, I tweaked the code to use my nonstandard port as its
      default, replacing all "22" with mine, and tried again...nope.

    Geo-replication session will be established
      between j and geoacct@pms::n

      root@pms password is required to complete the setup. NOTE:
      Password will not be stored.

      root@pms's password: 

      [    OK] pms is Reachable(Port 6247)

      Traceback (most recent call last):

        File "/usr/local/bin/gluster-georep-setup", line 8, in
      <module>

          sys.exit(main())

                   ^^^^^^

        File
"/usr/local/lib/python3.12/site-packages/gluster_georep_tools/setup/cli.py",
      line 524, in main

          setup_georep()

        File
"/usr/local/lib/python3.12/site-packages/gluster_georep_tools/setup/cli.py",
      line 461, in setup_georep

          ssh = ssh_initialize(secondary_host, args.secondary_user,
      passwd)

      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

        File
"/usr/local/lib/python3.12/site-packages/gluster_georep_tools/setup/cli.py",
      line 212, in ssh_initialize

          ssh.connect(secondary_host, username=username,
      password=passwd)

        File "/usr/lib/python3.12/site-packages/paramiko/client.py",
      line 409, in connect

          raise NoValidConnectionsError(errors)

      paramiko.ssh_exception.NoValidConnectionsError: [Errno None]
      Unable to connect to port 22 on 172.17.4.3

    It seems that paramiko is either still using
      22 under the hood somewhere (cf.
      last line error), or 22 is misinfo
      but it's insisting on connection using a password, but my
      (otherwise pretty standard) sshd configuration requires keys-only
      root login, no password, which is already in place among all these
      machines.

      I'm open to other suggestions.

________

Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://meet.google.com/cpu-eiue-hvk
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users