search for: georep

...ary Volume to see the available size. To mount the secondary volume in Primary, port 24007 and 49152-49664 of the secondary volume needs to be accessible from the Primary (Only in the node from where the Geo-rep create command is executed). This need to be changed to use SSH(bug). Alternatively use georep setup tool from?https://github.com/aravindavk/gluster-georep-tools. This tool only uses Port 22 of SSH. Once the Geo-rep session is created, all the communication and the data transfer happens via SSH(Default port: 22).? Aravinda Kadalu Technologies https://kadalu.tech ---- On Tue, 3...

...that was at all restricted was /var/lib/glusterd/geo-replication, so... chmod ugo+rx /var/lib/glusterd/geo-replication ...to take care of that. Again, attempted start, to no effect, the session remains in Created state. I wish there was a single, exhaustive description of "problems causing georep not to initiate." The fact that it reports apparent success without moving forward to Active state is odd, and maddening. What event or state is which part of the process waiting for? Having started (in principle), what is evaluating conditions for moving to Active? -------------- next part...

...r my test configuration of 1-brick volumes. gluster volume set j cluster.enable-shared-storage on volume set: failed: Not a valid option for single volume I looked through that documentation. It comes down to the same geo-rep create command, with the same result. In any event, I re-ran gluster-georep-sshkey generate on both nodes, which worked fine. Then, just as before gluster volume geo-replication j geoacct at pms::n create ssh-port 6247 push-pem Please check gsync config file. Unable to get statefile's name geo-replication command failed I don't yet see what else I could be doin...

...op/start quota on/off, adding and removing entries self heal status turning protocols off/on - CIFS (user.cifs) and NFS (nfs.disable) Xattr's reusing a brick - viewing the xattr - deleting xattr showing a file's relationship with the bricks and translators Disaster recovery establish georep check status - list of states - Initializing || Stable || Failed Client Side Help Windows drive map example (net use) NFS mount example for fstab glusterfs native mount (with backupvolfile-server syntax) Common tuning options Table network.ping-timeout server.root-squash cluster.server-quorum-ty...

Hi All, What are the ports needed to be opened for Gluster Geo replication ? We have a very closed setup, I could gather below info, does all of these ports need to be open on master and slave for inter communication or just 22 would work since it's using the rsync over ssh for actual data push ? *?* *Port 22 (TCP):* Used by SSH for secure data communication in Geo-replication. *?* *Port 24007

...have each mount the other's volume, so general operation seems ok. I have added the geoacct user and group, set up password-less login for each local root -> geoacct at other. gluster-mountbroker things have been done and "gluster-mountbroker status" is sensible. "gluster-georep-sshkey generate" has done what I'd expect. I'm at the point of creating geo-replication. Command on pjs is: gluster volume geo-replication j geoacct at pms::n create ssh-port 6247 push-pem (Yes, sshd listens on a nonstandard port.) This fails with: Please check gsync config...

...have each mount the other's volume, so general operation seems ok. I have added the geoacct user and group, set up password-less login for each local root -> geoacct at other. gluster-mountbroker things have been done and "gluster-mountbroker status" is sensible. "gluster-georep-sshkey generate" has done what I'd expect. I'm at the point of creating geo-replication. Command on pjs is: gluster volume geo-replication j geoacct at pms::n create ssh-port 6247 push-pem (Yes, sshd listens on a nonstandard port.) This fails with: Please check gsync config file. U...

...ume Passwordless SSH not required for all nodes, it is required from one of the master node to one of the slave node. (From the master node where you want to run create command to the slave node which will be specified in the Create command) Alternatively you can use a tool called "gluster-georep-setup", which doesn't require initial passwordless step. http://aravindavk.in/blog/gluster-georep-tools/ https://github.com/aravindavk/gluster-georep-tools > > I check the status and they switch between being active with history > crawl and faulty with n/a every few second &gt...

Don't forget to test with the georep key. I think it was /var/lib/glusterd/geo-replication/secret.pem Best Regards, Strahil Nikolov ? ??????, 27 ?????? 2024 ?. ? 07:24:07 ?. ???????+2, Strahil Nikolov <hunter86_bg at yahoo.com> ??????: Hi Anant, i would first start checking if you can do ssh from all masters to the sla...

...est configuration of 1-brick volumes. gluster volume set j cluster.enable-shared-storage on volume set: failed: Not a valid option for single volume I looked through that documentation. It comes down to the same geo-rep create command, with the same result. In any event, I re-ran gluster-georep-sshkey generate on both nodes, which worked fine. Then, just as before gluster volume geo-replication j geoacct at pms::n create ssh-port 6247 push-pem Please check gsync config file. Unable to get statefile's name geo-replication command failed I don't yet see what else I could...

FYI, I will be traveling for the next week, and may not see email much until then. Your questions... On 8/31/24 04:59, Strahil Nikolov wrote: > One silly question: Did you try adding some files on the source volume > after the georep was created ? Yes. I wondered that, too, whether geo-rep would not start simply because there was nothing to do. But yes, there are a few files created after the geo-rep session was created. And status remains just "Created." > Can you share the output of your version of? 'sh -...

On 8/22/24 14:08, Strahil Nikolov wrote: > I can try to reproduce it if you could provide the gluster version, > operating system and volume options. Most kind. Fedora39,? Packages: $ grep gluster /var/log/rpmpkgs gluster-block-0.5-11.fc39.x86_64.rpm glusterfs-11.1-1.fc39.x86_64.rpm glusterfs-cli-11.1-1.fc39.x86_64.rpm glusterfs-client-xlators-11.1-1.fc39.x86_64.rpm

...> > The only log that is not empty is glusterd.log, I attach the log > from the restart time. The brick log, glustershd.log and glfsheal-gds-common.log is empty. > > This are the errors in the log: > [2023-02-20 07:23:46.235263 +0000] E [MSGID: 106061] [glusterd.c:597:glusterd_crt_georep_folders] 0-glusterd: Dict get failed [{Key=log-group}, {errno=2}, {error=No such file or directory}] > [2023-02-20 07:23:47.359917 +0000] E [MSGID: 106010] [glusterd-utils.c:3542:glusterd_compare_friend_volume] 0-management: Version of Cksums gds-common differ. local cksum = 3017846959, remote c...

Hi Strahil, hm, don't get me wrong, it may sound a bit stupid, but... where do i set the log level? Using debian... https://access.redhat.com/documentation/de-de/red_hat_gluster_storage/3/html/administration_guide/configuring_the_log_level ls /etc/glusterfs/ eventsconfig.json glusterfs-georep-logrotate gluster-rsyslog-5.8.conf group-db-workload group-gluster-block group-nl-cache group-virt.example logger.conf.example glusterd.vol glusterfs-logrotate gluster-rsyslog-7.2.conf group-distributed-virt group-metadata-cache group-samba gsyncd.conf thin-arbiter.vo...

...og that is not empty is glusterd.log, I attach the log > > from the restart time. The brick log, glustershd.log and glfsheal-gds-common.log is empty. > > > > This are the errors in the log: > > [2023-02-20 07:23:46.235263 +0000] E [MSGID: 106061] [glusterd.c:597:glusterd_crt_georep_folders] 0-glusterd: Dict get failed [{Key=log-group}, {errno=2}, {error=No such file or directory}] > > [2023-02-20 07:23:47.359917 +0000] E [MSGID: 106010] [glusterd-utils.c:3542:glusterd_compare_friend_volume] 0-management: Version of Cksums gds-common differ. local cksum = 3017846959, rem...

...15:53:30.232738] I [changelogagent(/gfs/brick1/gv0):73:__init__] ChangelogAgent: Agent listining... [2017-09-29 15:53:30.248094] I [monitor(monitor):363:monitor] Monitor: worker died in startup phase brick=/gfs/brick2/gv0 [2017-09-29 15:53:30.252793] I [gsyncdstatus(monitor):242:set_worker_status] GeorepStatus: Worker Status Change status=Faulty [2017-09-29 15:53:30.742058] I [master(/gfs/arbiter/gv0):1515:register] _GMaster: Working dir path=/var/lib/misc/glusterfsd/gfsvol/ssh%3A%2F%2Fgeo-rep-user%4010.1.1.104%3Agluster%3A%2F%2F127.0.0.1%3Agfsvol_rep/40efd54bad1d5828a1221dd560de376f [2017-09-29 15...

...et me wrong, it may sound a bit stupid, but... where do i > set the log level? Using debian... > > > https://access.redhat.com/documentation/de-de/red_hat_gluster_storage/3/html/administration_guide/configuring_the_log_level > > ls /etc/glusterfs/ > eventsconfig.json glusterfs-georep-logrotate > gluster-rsyslog-5.8.conf group-db-workload group-gluster-block > group-nl-cache group-virt.example logger.conf.example > glusterd.vol glusterfs-logrotate > gluster-rsyslog-7.2.conf group-distributed-virt group-metadata-cache > group-samba gsyncd.con...

...sound a bit stupid, but... where do i >> set the log level? Using debian... >> >> https://access.redhat.com/documentation/de-de/red_hat_gluster_storage/3/html/administration_guide/configuring_the_log_level >> >> ls /etc/glusterfs/ >> eventsconfig.json glusterfs-georep-logrotate >> gluster-rsyslog-5.8.conf group-db-workload group-gluster-block >> group-nl-cache group-virt.example logger.conf.example >> glusterd.vol glusterfs-logrotate >> gluster-rsyslog-7.2.conf group-distributed-virt group-metadata-cache >> group-...

...is glusterd.log, I attach the log > > > from the restart time. The brick log, glustershd.log and glfsheal-gds-common.log is empty. > > > > > > This are the errors in the log: > > > [2023-02-20 07:23:46.235263 +0000] E [MSGID: 106061] [glusterd.c:597:glusterd_crt_georep_folders] 0-glusterd: Dict get failed [{Key=log-group}, {errno=2}, {error=No such file or directory}] > > > [2023-02-20 07:23:47.359917 +0000] E [MSGID: 106010] [glusterd-utils.c:3542:glusterd_compare_friend_volume] 0-management: Version of Cksums gds-common differ. local cksum = 3017846959...

...sound a bit stupid, but... where do i >> set the log level? Using debian... >> >> https://access.redhat.com/documentation/de-de/red_hat_gluster_storage/3/html/administration_guide/configuring_the_log_level >> >> ls /etc/glusterfs/ >> eventsconfig.json? glusterfs-georep-logrotate >> gluster-rsyslog-5.8.conf? group-db-workload? ? ? group-gluster-block >>? group-nl-cache? group-virt.example? logger.conf.example >> glusterd.vol? ? ? glusterfs-logrotate >> gluster-rsyslog-7.2.conf? group-distributed-virt? group-metadata-cache >>? group-sa...