<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 08/02/17 10:06, Kotresh Hiremath
Ravishankar wrote:<br>
</div>
<blockquote
cite="mid:1825353875.28335196.1486548361459.JavaMail.zimbra@redhat.com"
type="cite">
<pre wrap="">Hi lejeczek,
Try stop force.
gluster vol geo-rep <mastervol> <slavehost>::<slavevol> stop force
</pre>
</blockquote>
<br>
I think something broke:<br>
<br>
[2017-02-12 18:30:09.970683] E
[resource(/__.aLocalStorages/3/0-GLUSTERs/3GLUSTER--DATA):234:errlog]
Popen: command "ssh -oPasswordAuthentication=no
-oStrictHostKeyChecking=no -i
/var/lib/glusterd/geo-replication/secret.pem -p 22
-oControlMaster=auto -S
/tmp/gsyncd-aux-ssh-AmCjT1/375cc55387150cdada9c394f5008e9b1.sock
<a class="moz-txt-link-abbreviated" href="mailto:root@10.5.6.32">root@10.5.6.32</a> /usr/libexec/glusterfs/gsyncd --session-owner
18ffba73-532e-4a4d-84da-fceea52f8c2e -N --listen --timeout 120
gluster://localhost:-DATA-Replica" returned with 1, saying:<br>
[2017-02-12 18:30:09.970925] E
[resource(/__.aLocalStorages/3/0-GLUSTERs/3GLUSTER--DATA):238:logerr]
Popen: ssh> stty: standard input: Inappropriate ioctl for device<br>
[2017-02-12 18:30:09.971138] E
[resource(/__.aLocalStorages/3/0-GLUSTERs/3GLUSTER--DATA):238:logerr]
Popen: ssh> [2017-02-12 18:30:08.841288] I [cli.c:728:main]
0-cli: Started running /usr/sbin/gluster with version 3.8.8<br>
[2017-02-12 18:30:09.971334] E
[resource(/__.aLocalStorages/3/0-GLUSTERs/3GLUSTER--DATA):238:logerr]
Popen: ssh> [2017-02-12 18:30:08.841384] I
[cli.c:611:cli_rpc_init] 0-cli: Connecting to remote glusterd at
localhost<br>
[2017-02-12 18:30:09.971538] E
[resource(/__.aLocalStorages/3/0-GLUSTERs/3GLUSTER--DATA):238:logerr]
Popen: ssh> [2017-02-12 18:30:08.967954] I [MSGID: 101190]
[event-epoll.c:628:event_dispatch_epoll_worker] 0-epoll: Started
thread with index 1<br>
[2017-02-12 18:30:09.971733] E
[resource(/__.aLocalStorages/3/0-GLUSTERs/3GLUSTER--DATA):238:logerr]
Popen: ssh> [2017-02-12 18:30:09.965125] I
[cli-cmd.c:130:cli_cmd_process] 0-: Exiting with: 110<br>
[2017-02-12 18:30:09.971925] E
[resource(/__.aLocalStorages/3/0-GLUSTERs/3GLUSTER--DATA):238:logerr]
Popen: ssh> gsyncd initializaion failed<br>
<br>
I even remove geo-repl and recreated but...<br>
thanks,<br>
L<br>
<br>
<br>
<blockquote
cite="mid:1825353875.28335196.1486548361459.JavaMail.zimbra@redhat.com"
type="cite">
<pre wrap="">
Thanks and Regards,
Kotresh H R
Thanks and Regards,
Kotresh H R
----- Original Message -----
</pre>
<blockquote type="cite">
<pre wrap="">From: "lejeczek" <a class="moz-txt-link-rfc2396E" href="mailto:peljasz@yahoo.co.uk"><peljasz@yahoo.co.uk></a>
To: "Kotresh Hiremath Ravishankar" <a class="moz-txt-link-rfc2396E" href="mailto:khiremat@redhat.com"><khiremat@redhat.com></a>
Cc: <a class="moz-txt-link-abbreviated" href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a>
Sent: Tuesday, February 7, 2017 3:42:18 PM
Subject: [Gluster-users] should geo repl pick up changes to a vol?
On 03/02/17 07:25, Kotresh Hiremath Ravishankar wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
The following steps needs to be followed when a brick is added from new
node on master.
1. Stop geo-rep
</pre>
</blockquote>
<pre wrap="">geo repl which master volume had a brick removed:
~]$ gluster volume geo-replication GROUP-WORK
10.5.6.32::GROUP-WORK-Replica status
MASTER NODE MASTER VOL MASTER
BRICK SLAVE USER
SLAVE SLAVE NODE STATUS
CRAWL STATUS LAST_SYNCED
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
10.5.6.100 GROUP-WORK
/__.aLocalStorages/3/0-GLUSTERs/GROUP-WORK root
10.5.6.32::GROUP-WORK-Replica 10.5.6.32 Active
History Crawl 2017-02-01 15:24:05
~]$ gluster volume geo-replication GROUP-WORK
10.5.6.32::GROUP-WORK-Replica stop
Staging failed on 10.5.6.49. Error: Geo-replication session
between GROUP-WORK and 10.5.6.32::GROUP-WORK-Replica does
not exist.
geo-replication command failed
10.5.6.49 is the brick which was added, now part of the
master vol.
</pre>
<blockquote type="cite">
<pre wrap="">
2. Run the following command on the master node where passwordless SSH
connection is configured, in order to create a common pem pub file.
# gluster system:: execute gsec_create
3. Create the geo-replication session using the following command.
The push-pem and force options are required to perform the necessary
pem-file setup on the slave nodes.
# gluster volume geo-replication MASTER_VOL SLAVE_HOST::SLAVE_VOL
create push-pem force
4. Start geo-rep
Thanks and Regards,
Kotresh H R
----- Original Message -----
</pre>
<blockquote type="cite">
<pre wrap="">From: "lejeczek" <a class="moz-txt-link-rfc2396E" href="mailto:peljasz@yahoo.co.uk"><peljasz@yahoo.co.uk></a>
To: <a class="moz-txt-link-abbreviated" href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a>
Sent: Thursday, February 2, 2017 1:14:07 AM
Subject: [Gluster-users] should geo repl pick up changes to a vol?
dear all
should gluster update geo repl when a volume changes?
eg. bricks are added, taken away.
reason I'm asking is because it doe not seem like gluster is
doing it on my systems?
Well, I see gluster removed a node form geo-repl, brick that
I removed.
But I added a brick to a vol and it's not there in geo-repl.
bw.
L.
_______________________________________________
Gluster-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>
<a class="moz-txt-link-freetext" href="http://lists.gluster.org/mailman/listinfo/gluster-users">http://lists.gluster.org/mailman/listinfo/gluster-users</a>
</pre>
</blockquote>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
</blockquote>
<br>
</body>
</html>