search for: gverify

Hi, When creating a geo-replication session is the gverify.sh used or ran respectively? or is gverify.sh just an ad-hoc command to test manually if creating a geo-replication creationg would succeed? Best, M. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20...

On Saturday 19 August 2017 02:05 AM, mabi wrote: > Hi, > > When creating a geo-replication session is the gverify.sh used or ran > respectively? Yes, It is executed as part of geo-replication session creation. > or is gverify.sh just an ad-hoc command to test manually if creating a > geo-replication creationg would succeed? > No need to run separately ~ Saravana -------------- next part -...

...for the geoaccount user, I ran the command again, and then got this error: root at glusterA:/data/brick# gluster volume geo-replication ansible geoaccount at glusterX::ansible create push-pem Unable to mount and fetch slave volume details. Please check the log: /var/log/glusterfs/geo-replication/gverify-slavemnt.log geo-replication command failed That log file contained this: [2023-03-14 19:13:48.904461 +0000] I [MSGID: 100030] [glusterfsd.c:2685:main] 0-glusterfs: Started running version [{arg=glusterfs}, {version=9.2}, {cmdlinestr=glusterfs --xlator- option=*dht.lookup-unhashed=off --volfile-s...

...n the command again, and then got this > error: > > root at glusterA:/data/brick# gluster volume geo-replication ansible > geoaccount at glusterX::ansible create push-pem > Unable to mount and fetch slave volume details. Please check the log: > /var/log/glusterfs/geo-replication/gverify-slavemnt.log > geo-replication command failed > > That log file contained this: > > [2023-03-14 19:13:48.904461 +0000] I [MSGID: 100030] > [glusterfsd.c:2685:main] 0-glusterfs: Started running version > [{arg=glusterfs}, {version=9.2}, {cmdlinestr=glusterfs --xlator- > opt...