search for: geoacct

On 8/30/24 04:17, Strahil Nikolov wrote: > Have you done the following setup on the receiving gluster volume: Yes. For completeness' sake: grep geoacct /etc/passwd /etc/group /etc/passwd:geoacct:x:5273:5273:gluster geo-replication:/var/lib/glusterd/geoacct:/bin/bash /etc/group:geoacct:x:5273: gluster-mountbroker status +-----------+-------------+---------------------------+-------------+----------------+ |??? NODE?? | NODE STATUS |???????? MOUNT...

...docs.gluster.org/en/main/Administrator-Guide/Geo-Replication/ Hosts are pjs and pms, with respective volumes j and n. I have created, started, and mounted the volumes, each on their own localhost. I can also 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-r...

...he geo-rep session was created. And status remains just "Created." > Can you share the output of your version of? 'sh -x > /usr/libexec/glusterfs/gverify.sh masterVol slaveUser slaveHost > slaveVol sshPort logFileName' check ? sh -x /usr/libexec/glusterfs/gverify.sh j geoacct pms n 7887 /tmp/logger + BUFFER_SIZE=104857600 + SSH_PORT=7887 ++ gluster --print-logdir + primary_log_file=/var/log/glusterfs/geo-replication/gverify-primarymnt.log ++ gluster --print-logdir + secondary_log_file=/var/log/glusterfs/geo-replication/gverify-secondarymnt.log + main j geoacct pms n 78...

....gluster.org/en/main/Administrator-Guide/Geo-Replication/ Hosts are pjs and pms, with respective volumes j and n. I have created, started, and mounted the volumes, each on their own localhost. I can also 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...

...ailed: 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 doing with this. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.glus...

...ot 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 doing with this. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://li...