<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta content="text/html; charset=utf-8">
</head>
<body>
<div dir="auto">Thanks for your help, Sunny and Kotresh!
<div dir="auto"><br>
</div>
<div dir="auto">The geo-replication is working now!</div>
<div dir="auto">The final step I tried was to make a symlink </div>
<div dir="auto">ln -s /usr/lib64/libgfchangelog.so.1 /usr/lib64/libgfchangelog.so</div>
<div dir="auto"><br>
</div>
<div dir="auto">After that everything started working! </div>
<div dir="auto"><br>
</div>
<div dir="auto">Do I need to report the steps I made somewhere? I don't know if rpm is made by gluster or Cent os?</div>
<div dir="auto"><br>
</div>
<div dir="auto">I started with Cent os 7 and gluster 3.12.9, installed from Cent os SIG gluster </div>
<div dir="auto">I did the following steps:</div>
<div dir="auto">- Installed and upgraded to 4.1.1 from Cent os SIG gluster</div>
<div dir="auto">- Installed fix https://review.gluster.org/#/c/20207/</div>
<div dir="auto">- Changed permissions on file /var/log/glusterfs/cli.log so geo user could access it</div>
<div dir="auto">- Made symlinks to /usr/local/sbin/gluster and <span style="font-family:sans-serif">/usr/local/sbin/gluster</span></div>
<div dir="auto"><font face="sans-serif">Better way should have been to change config:</font></div>
<div dir="auto"><font face="sans-serif" style=""> </font><span style="font-family:sans-serif; font-size:13.3333px">#gluster vol geo-rep <mastervol> <slave-vol> config gluster-command-dir <gluster-binary-location></span></div>
<div dir="auto"><span style="font-family:sans-serif; font-size:13.3333px"> </span><span style="font-family:sans-serif; font-size:13.3333px">#gluster vol geo-rep <mastervol> <slave-vol> config slave-gluster-command-dir <gluster-binary-location></span></div>
<div dir="auto"><font face="sans-serif">- Made symlink:</font><span style="font-family:sans-serif; font-size:13.3333px"><br>
</span></div>
<div dir="auto"><font face="sans-serif">ln -s /usr/lib64/libgfchangelog.so.0 /usr/lib64/libgfchangelog.so<br>
</font></div>
<div dir="auto"><font face="sans-serif"><br>
</font></div>
<div dir="auto"><font face="sans-serif">Thanks for all help!</font></div>
<div dir="auto"><font face="sans-serif"><br>
</font></div>
<div dir="auto"><font face="sans-serif">Regards</font></div>
<div dir="auto"><font face="sans-serif">Marcus </font></div>
<div dir="auto"><br>
</div>
<div dir="auto">
<div dir="auto">################<br>
Marcus Pedersén<br>
Systemadministrator <br>
Interbull Centre<br>
################<br>
Sent from my phone <br>
################</div>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">Den 23 juli 2018 20:11 skrev Marcus Pedersén <marcus.pedersen@slu.se>:<br type="attribution">
</div>
</div>
<div>
<div dir="auto">
<div>Hi again Sunny,
<div dir="auto">Sorry, I missed the obvious myself!</div>
<div dir="auto"> <br>
#find /usr/ -name libgfchangelog.so</div>
<div dir="auto">Gives nothing</div>
<div dir="auto"><br>
</div>
<div dir="auto">#find /usr/ -name libgfchangelog.so*</div>
<div dir="auto">Gives:</div>
<div dir="auto">/usr/lib64/libgfchangelog.so.0 /usr/lib64/libgfchangelog.so.0.0.1</div>
<div dir="auto"><br>
</div>
<div dir="auto">Regards</div>
<div dir="auto">Marcus </div>
<div dir="auto"><br>
<div dir="auto">################<br>
Marcus Pedersén<br>
Systemadministrator <br>
Interbull Centre<br>
################<br>
Sent from my phone <br>
################</div>
</div>
<br>
<div class="gmail_extra"><br>
<div class="gmail_quote">Den 23 juli 2018 15:15 skrev Sunny Kumar <sunkumar@redhat.com>:<br type="attribution">
<blockquote class="quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
<div><font size="2"><span style="font-size:10pt">
<div>Hi Marcus,<br>
<br>
Okay first apologies for wrong pattern here, please run<br>
<br>
# find /usr/ -name libgfchangelog.so<br>
<br>
- Sunny<br>
On Mon, Jul 23, 2018 at 6:25 PM Marcus Pedersén <marcus.pedersen@slu.se> wrote:<br>
><br>
> Hi,<br>
> #find /usr/ -name libglusterfs.so<br>
> Gives nothing.<br>
><br>
> #find /usr/ -name libglusterfs.so*<br>
> Gives:<br>
> /usr/lib64/libglusterfs.so.0 /usr/lib64/libglusterfs.so.0.0.1<br>
><br>
> Thanks!<br>
> Marcus<br>
><br>
> ################<br>
> Marcus Pedersén<br>
> Systemadministrator<br>
> Interbull Centre<br>
> ################<br>
> Sent from my phone<br>
> ################<br>
><br>
> Den 23 juli 2018 14:17 skrev Sunny Kumar <sunkumar@redhat.com>:<br>
><br>
> Hi,<br>
><br>
> Can you confirm the location for libgfchangelog.so<br>
> by sharing output of following command -<br>
> # find /usr/ -name libglusterfs.so<br>
><br>
> - Sunny<br>
><br>
> On Mon, Jul 23, 2018 at 5:12 PM Marcus Pedersén <marcus.pedersen@slu.se> wrote:<br>
> ><br>
> > Hi Sunny,<br>
> > Here comes a part of gsyncd.log (The same info is repeated over and over again):<br>
> ><br>
> > File "/usr/libexec/glusterfs/python/syncdaemon/repce.py", line 207, in __call__<br>
> > raise res<br>
> > OSError: libgfchangelog.so: cannot open shared object file: No such file or directory<br>
> > [2018-07-23 11:33:09.254915] I [repce(agent /urd-gds/gluster):89:service_loop] RepceServer: terminating on reaching EOF.<br>
> > [2018-07-23 11:33:10.225150] I [monitor(monitor):272:monitor] Monitor: worker died in startup phase brick=/urd-gds/gluster<br>
> > [2018-07-23 11:33:20.250036] I [monitor(monitor):158:monitor] Monitor: starting gsyncd worker brick=/urd-gds/gluster slave_node=urd-gds-geo-000<br>
> > [2018-07-23 11:33:20.326205] I [gsyncd(agent /urd-gds/gluster):297:main] <top>: Using session config file path=/var/lib/glusterd/geo-replication/urd-gds-volume_urd-gds-geo-001_urd-gds-volume/gsyncd.conf<br>
> > [2018-07-23 11:33:20.326282] I [gsyncd(worker /urd-gds/gluster):297:main] <top>: Using session config file path=/var/lib/glusterd/geo-replication/urd-gds-volume_urd-gds-geo-001_urd-gds-volume/gsyncd.conf<br>
> > [2018-07-23 11:33:20.327152] I [changelogagent(agent /urd-gds/gluster):72:__init__] ChangelogAgent: Agent listining...<br>
> > [2018-07-23 11:33:20.335777] I [resource(worker /urd-gds/gluster):1348:connect_remote] SSH: Initializing SSH connection between master and slave...<br>
> > [2018-07-23 11:33:22.11188] I [resource(worker /urd-gds/gluster):1395:connect_remote] SSH: SSH connection between master and slave established. duration=1.6752<br>
> > [2018-07-23 11:33:22.11744] I [resource(worker /urd-gds/gluster):1067:connect] GLUSTER: Mounting gluster volume locally...<br>
> > [2018-07-23 11:33:23.101602] I [resource(worker /urd-gds/gluster):1090:connect] GLUSTER: Mounted gluster volume duration=1.0894<br>
> > [2018-07-23 11:33:23.102168] I [subcmds(worker /urd-gds/gluster):70:subcmd_worker] <top>: Worker spawn successful. Acknowledging back to monitor<br>
> > [2018-07-23 11:33:23.119129] E [repce(agent /urd-gds/gluster):114:worker] <top>: call failed:<br>
> > Traceback (most recent call last):<br>
> > File "/usr/libexec/glusterfs/python/syncdaemon/repce.py", line 110, in worker<br>
> > res = getattr(self.obj, rmeth)(*in_data[2:])<br>
> > File "/usr/libexec/glusterfs/python/syncdaemon/changelogagent.py", line 37, in init<br>
> > return Changes.cl_init()<br>
> > File "/usr/libexec/glusterfs/python/syncdaemon/changelogagent.py", line 21, in __getattr__<br>
> > from libgfchangelog import Changes as LChanges<br>
> > File "/usr/libexec/glusterfs/python/syncdaemon/libgfchangelog.py", line 17, in <module><br>
> > class Changes(object):<br>
> > File "/usr/libexec/glusterfs/python/syncdaemon/libgfchangelog.py", line 19, in Changes<br>
> > use_errno=True)<br>
> > File "/usr/lib64/python2.7/ctypes/__init__.py", line 360, in __init__<br>
> > self._handle = _dlopen(self._name, mode)<br>
> > OSError: libgfchangelog.so: cannot open shared object file: No such file or directory<br>
> > [2018-07-23 11:33:23.119609] E [repce(worker /urd-gds/gluster):206:__call__] RepceClient: call failed call=29589:140155686246208:1532345603.11 method=init error=OSError<br>
> > [2018-07-23 11:33:23.119708] E [syncdutils(worker /urd-gds/gluster):330:log_raise_exception] <top>: FAIL:<br>
> > Traceback (most recent call last):<br>
> > File "/usr/libexec/glusterfs/python/syncdaemon/gsyncd.py", line 311, in main<br>
> > func(args)<br>
> > File "/usr/libexec/glusterfs/python/syncdaemon/subcmds.py", line 72, in subcmd_worker<br>
> > local.service_loop(remote)<br>
> > File "/usr/libexec/glusterfs/python/syncdaemon/resource.py", line 1236, in service_loop<br>
> > changelog_agent.init()<br>
> > File "/usr/libexec/glusterfs/python/syncdaemon/repce.py", line 225, in __call__<br>
> > return self.ins(self.meth, *a)<br>
> > File "/usr/libexec/glusterfs/python/syncdaemon/repce.py", line 207, in __call__<br>
> > raise res<br>
> > OSError: libgfchangelog.so: cannot open shared object file: No such file or directory<br>
> > [2018-07-23 11:33:23.130100] I [repce(agent /urd-gds/gluster):89:service_loop] RepceServer: terminating on reaching EOF.<br>
> > [2018-07-23 11:33:24.104176] I [monitor(monitor):272:monitor] Monitor: worker died in startup phase brick=/urd-gds/gluster<br>
> ><br>
> > Thanks, Sunny!!<br>
> ><br>
> > Regards<br>
> > Marcus Pedersén<br>
> ><br>
> > ________________________________________<br>
> > Från: Sunny Kumar <sunkumar@redhat.com><br>
> > Skickat: den 23 juli 2018 12:53<br>
> > Till: Marcus Pedersén<br>
> > Kopia: Kotresh Hiremath Ravishankar; gluster-users@gluster.org<br>
> > Ämne: Re: [Gluster-users] Upgrade to 4.1.1 geo-replication does not work<br>
> ><br>
> > Hi Marcus,<br>
> ><br>
> > On Mon, Jul 23, 2018 at 4:04 PM Marcus Pedersén <marcus.pedersen@slu.se> wrote:<br>
> > ><br>
> > > Hi Sunny,<br>
> > > ldconfig -p /usr/local/lib | grep libgf<br>
> > > Output:<br>
> > > libgfxdr.so.0 (libc6,x86-64) => /lib64/libgfxdr.so.0 libgfrpc.so.0 (libc6,x86-64) => /lib64/libgfrpc.so.0<br>
> > > libgfdb.so.0 (libc6,x86-64) => /lib64/libgfdb.so.0 libgfchangelog.so.0 (libc6,x86-64) => /lib64/libgfchangelog.so.0 libgfapi.so.0 (libc6,x86-64)
=> /lib64/libgfapi.so.0<br>
> > ><br>
> > > So that seems to be alright, right?<br>
> > ><br>
> > Yes, this seems wright can you share the gsyncd.log again<br>
> > > Best regards<br>
> > > Marcus<br>
> > ><br>
> > > ################<br>
> > > Marcus Pedersén<br>
> > > Systemadministrator<br>
> > > Interbull Centre<br>
> > > ################<br>
> > > Sent from my phone<br>
> > > ################<br>
> > ><br>
> > > Den 23 juli 2018 11:17 skrev Sunny Kumar <sunkumar@redhat.com>:<br>
> > ><br>
> > > Hi Marcus,<br>
> > ><br>
> > > On Wed, Jul 18, 2018 at 4:08 PM Marcus Pedersén <marcus.pedersen@slu.se> wrote:<br>
> > > ><br>
> > > > Hi Kotresh,<br>
> > > ><br>
> > > > I ran:<br>
> > > ><br>
> > > > #ldconfig /usr/lib<br>
> > > can you do -<br>
> > > ldconfig /usr/local/lib<br>
> > ><br>
> > ><br>
> > > Output:<br>
> > ><br>
> > > ><br>
> > > > on all nodes in both clusters but I still get the same error.<br>
> > > ><br>
> > > > What to do?<br>
> > > ><br>
> > > ><br>
> > > > Output for:<br>
> > > ><br>
> > > > # ldconfig -p /usr/lib | grep libgf<br>
> > > ><br>
> > > > libgfxdr.so.0 (libc6,x86-64) => /lib64/libgfxdr.so.0<br>
> > > > libgfrpc.so.0 (libc6,x86-64) => /lib64/libgfrpc.so.0<br>
> > > > libgfdb.so.0 (libc6,x86-64) => /lib64/libgfdb.so.0<br>
> > > > libgfchangelog.so.0 (libc6,x86-64) => /lib64/libgfchangelog.so.0<br>
> > > > libgfapi.so.0 (libc6,x86-64) => /lib64/libgfapi.so.0<br>
> > > ><br>
> > > ><br>
> > > > I read somewere that you could change some settings for geo-replication to speed up sync.<br>
> > > ><br>
> > > > I can not remember where I saw that and what config parameters.<br>
> > > ><br>
> > > > When geo-replication works I have 30TB on master cluster that has to be synced to slave nodes,<br>
> > > ><br>
> > > > and that will take a while before the slave nodes have catched up.<br>
> > > ><br>
> > > ><br>
> > > > Thanks and regards<br>
> > > ><br>
> > > > Marcus Pedersén<br>
> > > ><br>
> > > ><br>
> > > > Part of gsyncd.log:<br>
> > > ><br>
> > > > File "/usr/libexec/glusterfs/python/syncdaemon/repce.py", line 207, in __call__<br>
> > > > raise res<br>
> > > > OSError: libgfchangelog.so: cannot open shared object file: No such file or directory<br>
> > > > [2018-07-18 10:23:52.305119] I [repce(agent /urd-gds/gluster):89:service_loop] RepceServer: terminating on reaching EOF.<br>
> > > > [2018-07-18 10:23:53.273298] I [monitor(monitor):272:monitor] Monitor: worker died in startup phase brick=/urd-gds/gluster<br>
> > > > [2018-07-18 10:24:03.294312] I [monitor(monitor):158:monitor] Monitor: starting gsyncd worker brick=/urd-gds/gluster slave_node=urd-gds-geo-000<br>
> > > > [2018-07-18 10:24:03.334563] I [gsyncd(agent /urd-gds/gluster):297:main] <top>: Using session config file path=/var/lib/glusterd/geo-replication/urd-gds-volume_urd-gds-geo-001_urd-gds-volume/gsyncd.conf<br>
> > > > [2018-07-18 10:24:03.334702] I [gsyncd(worker /urd-gds/gluster):297:main] <top>: Using session config file path=/var/lib/glusterd/geo-replication/urd-gds-volume_urd-gds-geo-001_urd-gds-volume/gsyncd.conf<br>
> > > > [2018-07-18 10:24:03.335380] I [changelogagent(agent /urd-gds/gluster):72:__init__] ChangelogAgent: Agent listining...<br>
> > > > [2018-07-18 10:24:03.343605] I [resource(worker /urd-gds/gluster):1348:connect_remote] SSH: Initializing SSH connection between master and slave...<br>
> > > > [2018-07-18 10:24:04.881148] I [resource(worker /urd-gds/gluster):1395:connect_remote] SSH: SSH connection between master and slave established. duration=1.5373<br>
> > > > [2018-07-18 10:24:04.881707] I [resource(worker /urd-gds/gluster):1067:connect] GLUSTER: Mounting gluster volume locally...<br>
> > > > [2018-07-18 10:24:05.967451] I [resource(worker /urd-gds/gluster):1090:connect] GLUSTER: Mounted gluster volume duration=1.0853<br>
> > > > [2018-07-18 10:24:05.968028] I [subcmds(worker /urd-gds/gluster):70:subcmd_worker] <top>: Worker spawn successful. Acknowledging back to monitor<br>
> > > > [2018-07-18 10:24:05.984179] E [repce(agent /urd-gds/gluster):114:worker] <top>: call failed:<br>
> > > > Traceback (most recent call last):<br>
> > > > File "/usr/libexec/glusterfs/python/syncdaemon/repce.py", line 110, in worker<br>
> > > > res = getattr(self.obj, rmeth)(*in_data[2:])<br>
> > > > File "/usr/libexec/glusterfs/python/syncdaemon/changelogagent.py", line 37, in init<br>
> > > > return Changes.cl_init()<br>
> > > > File "/usr/libexec/glusterfs/python/syncdaemon/changelogagent.py", line 21, in __getattr__<br>
> > > > from libgfchangelog import Changes as LChanges<br>
> > > > File "/usr/libexec/glusterfs/python/syncdaemon/libgfchangelog.py", line 17, in <module><br>
> > > > class Changes(object):<br>
> > > > File "/usr/libexec/glusterfs/python/syncdaemon/libgfchangelog.py", line 19, in Changes<br>
> > > > use_errno=True)<br>
> > > > File "/usr/lib64/python2.7/ctypes/__init__.py", line 360, in __init__<br>
> > > > self._handle = _dlopen(self._name, mode)<br>
> > > > OSError: libgfchangelog.so: cannot open shared object file: No such file or directory<br>
> > > > [2018-07-18 10:24:05.984647] E [repce(worker /urd-gds/gluster):206:__call__] RepceClient: call failed call=1146:139672481965888:1531909445.98 method=init error=OSError<br>
> > > > [2018-07-18 10:24:05.984747] E [syncdutils(worker /urd-gds/gluster):330:log_raise_exception] <top>: FAIL:<br>
> > > > Traceback (most recent call last):<br>
> > > > File "/usr/libexec/glusterfs/python/syncdaemon/gsyncd.py", line 311, in main<br>
> > > > func(args)<br>
> > > > File "/usr/libexec/glusterfs/python/syncdaemon/subcmds.py", line 72, in subcmd_worker<br>
> > > > local.service_loop(remote)<br>
> > > > File "/usr/libexec/glusterfs/python/syncdaemon/resource.py", line 1236, in service_loop<br>
> > > > changelog_agent.init()<br>
> > > > File "/usr/libexec/glusterfs/python/syncdaemon/repce.py", line 225, in __call__<br>
> > > > return self.ins(self.meth, *a)<br>
> > > > File "/usr/libexec/glusterfs/python/syncdaemon/repce.py", line 207, in __call__<br>
> > > > raise res<br>
> > > > OSError: libgfchangelog.so: cannot open shared object file: No such file or directory<br>
> > > I think then you will not see this.<br>
> > > > [2018-07-18 10:24:05.994826] I [repce(agent /urd-gds/gluster):89:service_loop] RepceServer: terminating on reaching EOF.<br>
> > > > [2018-07-18 10:24:06.969984] I [monitor(monitor):272:monitor] Monitor: worker died in startup phase brick=/urd-gds/gluster<br>
> > > ><br>
> > > ><br>
> > > > ________________________________<br>
> > > > Från: Kotresh Hiremath Ravishankar <khiremat@redhat.com><br>
> > > > Skickat: den 18 juli 2018 06:05<br>
> > > > Till: Marcus Pedersén<br>
> > > > Kopia: gluster-users@gluster.org<br>
> > > > Ämne: Re: [Gluster-users] Upgrade to 4.1.1 geo-replication does not work<br>
> > > ><br>
> > > > Hi Marcus,<br>
> > > ><br>
> > > > Well there is nothing wrong in setting up a symlink for gluster binary location, but<br>
> > > > there is a geo-rep command to set it so that gsyncd will search there.<br>
> > > ><br>
> > > > To set on master<br>
> > > > #gluster vol geo-rep <mastervol> <slave-vol> config gluster-command-dir <gluster-binary-location><br>
> > > ><br>
> > > > To set on slave<br>
> > > > #gluster vol geo-rep <mastervol> <slave-vol> config slave-gluster-command-dir <gluster-binary-location><br>
> > > ><br>
> > > > Thanks,<br>
> > > > Kotresh HR<br>
> > > ><br>
> > > ><br>
> > > > On Wed, Jul 18, 2018 at 9:28 AM, Kotresh Hiremath Ravishankar <khiremat@redhat.com> wrote:<br>
> > > >><br>
> > > >> Hi Marcus,<br>
> > > >><br>
> > > >> I am testing out 4.1 myself and I will have some update today.<br>
> > > >> For this particular traceback, gsyncd is not able to find the library.<br>
> > > >> Is it the rpm install? If so, gluster libraries would be in /usr/lib.<br>
> > > >> Please run the cmd below.<br>
> > > >><br>
> > > >> #ldconfig /usr/lib<br>
> > > >> #ldconfig -p /usr/lib | grep libgf (This should list libgfchangelog.so)<br>
> > > >><br>
> > > >> Geo-rep should be fixed automatically.<br>
> > > >><br>
> > > >> Thanks,<br>
> > > >> Kotresh HR<br>
> > > >><br>
> > > >> On Wed, Jul 18, 2018 at 1:27 AM, Marcus Pedersén <marcus.pedersen@slu.se> wrote:<br>
> > > >>><br>
> > > >>> Hi again,<br>
> > > >>><br>
> > > >>> I continue to do some testing, but now I have come to a stage where I need help.<br>
> > > >>><br>
> > > >>><br>
> > > >>> gsyncd.log was complaining about that /usr/local/sbin/gluster was missing so I made a link.<br>
> > > >>><br>
> > > >>> After that /usr/local/sbin/glusterfs was missing so I made a link there as well.<br>
> > > >>><br>
> > > >>> Both links were done on all slave nodes.<br>
> > > >>><br>
> > > >>><br>
> > > >>> Now I have a new error that I can not resolve myself.<br>
> > > >>><br>
> > > >>> It can not open libgfchangelog.so<br>
> > > >>><br>
> > > >>><br>
> > > >>> Many thanks!<br>
> > > >>><br>
> > > >>> Regards<br>
> > > >>><br>
> > > >>> Marcus Pedersén<br>
> > > >>><br>
> > > >>><br>
> > > >>> Part of gsyncd.log:<br>
> > > >>><br>
> > > >>> OSError: libgfchangelog.so: cannot open shared object file: No such file or directory<br>
> > > >>> [2018-07-17 19:32:06.517106] I [repce(agent /urd-gds/gluster):89:service_loop] RepceServer: terminating on reaching EOF.<br>
> > > >>> [2018-07-17 19:32:07.479553] I [monitor(monitor):272:monitor] Monitor: worker died in startup phase brick=/urd-gds/gluster<br>
> > > >>> [2018-07-17 19:32:17.500709] I [monitor(monitor):158:monitor] Monitor: starting gsyncd worker brick=/urd-gds/gluster slave_node=urd-gds-geo-000<br>
> > > >>> [2018-07-17 19:32:17.541547] I [gsyncd(agent /urd-gds/gluster):297:main] <top>: Using session config file path=/var/lib/glusterd/geo-replication/urd-gds-volume_urd-gds-geo-001_urd-gds-volume/gsyncd.conf<br>
> > > >>> [2018-07-17 19:32:17.541959] I [gsyncd(worker /urd-gds/gluster):297:main] <top>: Using session config file path=/var/lib/glusterd/geo-replication/urd-gds-volume_urd-gds-geo-001_urd-gds-volume/gsyncd.conf<br>
> > > >>> [2018-07-17 19:32:17.542363] I [changelogagent(agent /urd-gds/gluster):72:__init__] ChangelogAgent: Agent listining...<br>
> > > >>> [2018-07-17 19:32:17.550894] I [resource(worker /urd-gds/gluster):1348:connect_remote] SSH: Initializing SSH connection between master and slave...<br>
> > > >>> [2018-07-17 19:32:19.166246] I [resource(worker /urd-gds/gluster):1395:connect_remote] SSH: SSH connection between master and slave established. duration=1.6151<br>
> > > >>> [2018-07-17 19:32:19.166806] I [resource(worker /urd-gds/gluster):1067:connect] GLUSTER: Mounting gluster volume locally...<br>
> > > >>> [2018-07-17 19:32:20.257344] I [resource(worker /urd-gds/gluster):1090:connect] GLUSTER: Mounted gluster volume duration=1.0901<br>
> > > >>> [2018-07-17 19:32:20.257921] I [subcmds(worker /urd-gds/gluster):70:subcmd_worker] <top>: Worker spawn successful. Acknowledging back to monitor<br>
> > > >>> [2018-07-17 19:32:20.274647] E [repce(agent /urd-gds/gluster):114:worker] <top>: call failed:<br>
> > > >>> Traceback (most recent call last):<br>
> > > >>> File "/usr/libexec/glusterfs/python/syncdaemon/repce.py", line 110, in worker<br>
> > > >>> res = getattr(self.obj, rmeth)(*in_data[2:])<br>
> > > >>> File "/usr/libexec/glusterfs/python/syncdaemon/changelogagent.py", line 37, in init<br>
> > > >>> return Changes.cl_init()<br>
> > > >>> File "/usr/libexec/glusterfs/python/syncdaemon/changelogagent.py", line 21, in __getattr__<br>
> > > >>> from libgfchangelog import Changes as LChanges<br>
> > > >>> File "/usr/libexec/glusterfs/python/syncdaemon/libgfchangelog.py", line 17, in <module><br>
> > > >>> class Changes(object):<br>
> > > >>> File "/usr/libexec/glusterfs/python/syncdaemon/libgfchangelog.py", line 19, in Changes<br>
> > > >>> use_errno=True)<br>
> > > >>> File "/usr/lib64/python2.7/ctypes/__init__.py", line 360, in __init__<br>
> > > >>> self._handle = _dlopen(self._name, mode)<br>
> > > >>> OSError: libgfchangelog.so: cannot open shared object file: No such file or directory<br>
> > > >>> [2018-07-17 19:32:20.275093] E [repce(worker /urd-gds/gluster):206:__call__] RepceClient: call failed call=6078:139982918485824:1531855940.27 method=init error=OSError<br>
> > > >>> [2018-07-17 19:32:20.275192] E [syncdutils(worker /urd-gds/gluster):330:log_raise_exception] <top>: FAIL:<br>
> > > >>> Traceback (most recent call last):<br>
> > > >>> File "/usr/libexec/glusterfs/python/syncdaemon/gsyncd.py", line 311, in main<br>
> > > >>> func(args)<br>
> > > >>> File "/usr/libexec/glusterfs/python/syncdaemon/subcmds.py", line 72, in subcmd_worker<br>
> > > >>> local.service_loop(remote)<br>
> > > >>> File "/usr/libexec/glusterfs/python/syncdaemon/resource.py", line 1236, in service_loop<br>
> > > >>> changelog_agent.init()<br>
> > > >>> File "/usr/libexec/glusterfs/python/syncdaemon/repce.py", line 225, in __call__<br>
> > > >>> return self.ins(self.meth, *a)<br>
> > > >>> File "/usr/libexec/glusterfs/python/syncdaemon/repce.py", line 207, in __call__<br>
> > > >>> raise res<br>
> > > >>> OSError: libgfchangelog.so: cannot open shared object file: No such file or directory<br>
> > > >>> [2018-07-17 19:32:20.286787] I [repce(agent /urd-gds/gluster):89:service_loop] RepceServer: terminating on reaching EOF.<br>
> > > >>> [2018-07-17 19:32:21.259891] I [monitor(monitor):272:monitor] Monitor: worker died in startup phase brick=/urd-gds/gluster<br>
> > > >>><br>
> > > >>><br>
> > > >>><br>
> > > >>> ________________________________<br>
> > > >>> Från: gluster-users-bounces@gluster.org <gluster-users-bounces@gluster.org> för Marcus Pedersén <marcus.pedersen@slu.se><br>
> > > >>> Skickat: den 16 juli 2018 21:59<br>
> > > >>> Till: khiremat@redhat.com<br>
> > > >>><br>
> > > >>> Kopia: gluster-users@gluster.org<br>
> > > >>> Ämne: Re: [Gluster-users] Upgrade to 4.1.1 geo-replication does not work<br>
> > > >>><br>
> > > >>><br>
> > > >>> Hi Kotresh,<br>
> > > >>><br>
> > > >>> I have been testing for a bit and as you can see from the logs I sent before permission is denied for geouser on slave node on file:<br>
> > > >>><br>
> > > >>> /var/log/glusterfs/cli.log<br>
> > > >>><br>
> > > >>> I have turned selinux off and just for testing I changed permissions on /var/log/glusterfs/cli.log so geouser can access it.<br>
> > > >>><br>
> > > >>> Starting geo-replication after that gives response successful but all nodes get status Faulty.<br>
> > > >>><br>
> > > >>><br>
> > > >>> If I run: gluster-mountbroker status<br>
> > > >>><br>
> > > >>> I get:<br>
> > > >>><br>
> > > >>> +-----------------------------+-------------+---------------------------+--------------+--------------------------+<br>
> > > >>> | NODE | NODE STATUS | MOUNT ROOT | GROUP | USERS |<br>
> > > >>> +-----------------------------+-------------+---------------------------+--------------+--------------------------+<br>
> > > >>> | urd-gds-geo-001.hgen.slu.se | UP | /var/mountbroker-root(OK) | geogroup(OK) | geouser(urd-gds-volume) |<br>
> > > >>> | urd-gds-geo-002 | UP | /var/mountbroker-root(OK) | geogroup(OK) | geouser(urd-gds-volume) |<br>
> > > >>> | localhost | UP | /var/mountbroker-root(OK) | geogroup(OK) | geouser(urd-gds-volume) |<br>
> > > >>> +-----------------------------+-------------+---------------------------+--------------+--------------------------+<br>
> > > >>><br>
> > > >>><br>
> > > >>> and that is all nodes on slave cluster, so mountbroker seems ok.<br>
> > > >>><br>
> > > >>><br>
> > > >>> gsyncd.log logs an error about /usr/local/sbin/gluster is missing.<br>
> > > >>><br>
> > > >>> That is correct cos gluster is in /sbin/gluster and /urs/sbin/gluster<br>
> > > >>><br>
> > > >>> Another error is that SSH between master and slave is broken,<br>
> > > >>><br>
> > > >>> but now when I have changed permission on /var/log/glusterfs/cli.log I can run:<br>
> > > >>><br>
> > > >>> ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-replication/secret.pem -p 22 geouser@urd-gds-geo-001 gluster --xml --remote-host=localhost volume info urd-gds-volume<br>
> > > >>><br>
> > > >>> as geouser and that works, which means that the ssh connection works.<br>
> > > >>><br>
> > > >>><br>
> > > >>> Is the permissions on /var/log/glusterfs/cli.log changed when geo-replication is setup?<br>
> > > >>><br>
> > > >>> Is gluster supposed to be in /usr/local/sbin/gluster?<br>
> > > >>><br>
> > > >>><br>
> > > >>> Do I have any options or should I remove current geo-replication and create a new?<br>
> > > >>><br>
> > > >>> How much do I need to clean up before creating a new geo-replication?<br>
> > > >>><br>
> > > >>> In that case can I pause geo-replication, mount slave cluster on master cluster and run rsync , just to speed up transfer of files?<br>
> > > >>><br>
> > > >>><br>
> > > >>> Many thanks in advance!<br>
> > > >>><br>
> > > >>> Marcus Pedersén<br>
> > > >>><br>
> > > >>><br>
> > > >>> Part from the gsyncd.log:<br>
> > > >>><br>
> > > >>> [2018-07-16 19:34:56.26287] E [syncdutils(worker /urd-gds/gluster):749:errlog] Popen: command returned error cmd=ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-replicatio\<br>
> > > >>> n/secret.pem -p 22 -oControlMaster=auto -S /tmp/gsyncd-aux-ssh-WrbZ22/bf60c68f1a195dad59573a8dbaa309f2.sock geouser@urd-gds-geo-001 /nonexistent/gsyncd slave urd-gds-volume geouser@urd-gds-geo-001::urd-gds-volu\<br>
> > > >>> me --master-node urd-gds-001 --master-node-id 912bebfd-1a7f-44dc-b0b7-f001a20d58cd --master-brick /urd-gds/gluster --local-node urd-gds-geo-000 --local-node-id 03075698-2bbf-43e4-a99a-65fe82f61794 --slave-timeo\<br>
> > > >>> ut 120 --slave-log-level INFO --slave-gluster-log-level INFO --slave-gluster-command-dir /usr/local/sbin/ error=1<br>
> > > >>> [2018-07-16 19:34:56.26583] E [syncdutils(worker /urd-gds/gluster):753:logerr] Popen: ssh> failure: execution of "/usr/local/sbin/gluster" failed with ENOENT (No such file or directory)<br>
> > > >>> [2018-07-16 19:34:56.33901] I [repce(agent /urd-gds/gluster):89:service_loop] RepceServer: terminating on reaching EOF.<br>
> > > >>> [2018-07-16 19:34:56.34307] I [monitor(monitor):262:monitor] Monitor: worker died before establishing connection brick=/urd-gds/gluster<br>
> > > >>> [2018-07-16 19:35:06.59412] I [monitor(monitor):158:monitor] Monitor: starting gsyncd worker brick=/urd-gds/gluster slave_node=urd-gds-geo-000<br>
> > > >>> [2018-07-16 19:35:06.99509] I [gsyncd(worker /urd-gds/gluster):297:main] <top>: Using session config file path=/var/lib/glusterd/geo-replication/urd-gds-volume_urd-gds-geo-001_urd-gds-volume/gsyncd.conf<br>
> > > >>> [2018-07-16 19:35:06.99561] I [gsyncd(agent /urd-gds/gluster):297:main] <top>: Using session config file path=/var/lib/glusterd/geo-replication/urd-gds-volume_urd-gds-geo-001_urd-gds-volume/gsyncd.conf<br>
> > > >>> [2018-07-16 19:35:06.100481] I [changelogagent(agent /urd-gds/gluster):72:__init__] ChangelogAgent: Agent listining...<br>
> > > >>> [2018-07-16 19:35:06.108834] I [resource(worker /urd-gds/gluster):1348:connect_remote] SSH: Initializing SSH connection between master and slave...<br>
> > > >>> [2018-07-16 19:35:06.762320] E [syncdutils(worker /urd-gds/gluster):303:log_raise_exception] <top>: connection to peer is broken<br>
> > > >>> [2018-07-16 19:35:06.763103] E [syncdutils(worker /urd-gds/gluster):749:errlog] Popen: command returned error cmd=ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-replicatio\<br>
> > > >>> n/secret.pem -p 22 -oControlMaster=auto -S /tmp/gsyncd-aux-ssh-K9mB6Q/bf60c68f1a195dad59573a8dbaa309f2.sock geouser@urd-gds-geo-001 /nonexistent/gsyncd slave urd-gds-volume geouser@urd-gds-geo-001::urd-gds-volu\<br>
> > > >>> me --master-node urd-gds-001 --master-node-id 912bebfd-1a7f-44dc-b0b7-f001a20d58cd --master-brick /urd-gds/gluster --local-node urd-gds-geo-000 --local-node-id 03075698-2bbf-43e4-a99a-65fe82f61794 --slave-timeo\<br>
> > > >>> ut 120 --slave-log-level INFO --slave-gluster-log-level INFO --slave-gluster-command-dir /usr/local/sbin/ error=1<br>
> > > >>> [2018-07-16 19:35:06.763398] E [syncdutils(worker /urd-gds/gluster):753:logerr] Popen: ssh> failure: execution of "/usr/local/sbin/gluster" failed with ENOENT (No such file or directory)<br>
> > > >>> [2018-07-16 19:35:06.771905] I [repce(agent /urd-gds/gluster):89:service_loop] RepceServer: terminating on reaching EOF.<br>
> > > >>> [2018-07-16 19:35:06.772272] I [monitor(monitor):262:monitor] Monitor: worker died before establishing connection brick=/urd-gds/gluster<br>
> > > >>> [2018-07-16 19:35:16.786387] I [monitor(monitor):158:monitor] Monitor: starting gsyncd worker brick=/urd-gds/gluster slave_node=urd-gds-geo-000<br>
> > > >>> [2018-07-16 19:35:16.828056] I [gsyncd(worker /urd-gds/gluster):297:main] <top>: Using session config file path=/var/lib/glusterd/geo-replication/urd-gds-volume_urd-gds-geo-001_urd-gds-volume/gsyncd.conf<br>
> > > >>> [2018-07-16 19:35:16.828066] I [gsyncd(agent /urd-gds/gluster):297:main] <top>: Using session config file path=/var/lib/glusterd/geo-replication/urd-gds-volume_urd-gds-geo-001_urd-gds-volume/gsyncd.conf<br>
> > > >>> [2018-07-16 19:35:16.828912] I [changelogagent(agent /urd-gds/gluster):72:__init__] ChangelogAgent: Agent listining...<br>
> > > >>> [2018-07-16 19:35:16.837100] I [resource(worker /urd-gds/gluster):1348:connect_remote] SSH: Initializing SSH connection between master and slave...<br>
> > > >>> [2018-07-16 19:35:17.260257] E [syncdutils(worker /urd-gds/gluster):303:log_raise_exception] <top>: connection to peer is broken<br>
> > > >>><br>
> > > >>> ________________________________<br>
> > > >>> Från: gluster-users-bounces@gluster.org <gluster-users-bounces@gluster.org> för Marcus Pedersén <marcus.pedersen@slu.se><br>
> > > >>> Skickat: den 13 juli 2018 14:50<br>
> > > >>> Till: Kotresh Hiremath Ravishankar<br>
> > > >>> Kopia: gluster-users@gluster.org<br>
> > > >>> Ämne: Re: [Gluster-users] Upgrade to 4.1.1 geo-replication does not work<br>
> > > >>><br>
> > > >>> Hi Kotresh,<br>
> > > >>> Yes, all nodes have the same version 4.1.1 both master and slave.<br>
> > > >>> All glusterd are crashing on the master side.<br>
> > > >>> Will send logs tonight.<br>
> > > >>><br>
> > > >>> Thanks,<br>
> > > >>> Marcus<br>
> > > >>><br>
> > > >>> ################<br>
> > > >>> Marcus Pedersén<br>
> > > >>> Systemadministrator<br>
> > > >>> Interbull Centre<br>
> > > >>> ################<br>
> > > >>> Sent from my phone<br>
> > > >>> ################<br>
> > > >>><br>
> > > >>> Den 13 juli 2018 11:28 skrev Kotresh Hiremath Ravishankar <khiremat@redhat.com>:<br>
> > > >>><br>
> > > >>> Hi Marcus,<br>
> > > >>><br>
> > > >>> Is the gluster geo-rep version is same on both master and slave?<br>
> > > >>><br>
> > > >>> Thanks,<br>
> > > >>> Kotresh HR<br>
> > > >>><br>
> > > >>> On Fri, Jul 13, 2018 at 1:26 AM, Marcus Pedersén <marcus.pedersen@slu.se> wrote:<br>
> > > >>><br>
> > > >>> Hi Kotresh,<br>
> > > >>><br>
> > > >>> i have replaced both files (gsyncdconfig.py and repce.py) in all nodes both master and slave.<br>
> > > >>><br>
> > > >>> I rebooted all servers but geo-replication status is still Stopped.<br>
> > > >>><br>
> > > >>> I tried to start geo-replication with response Successful but status still show Stopped on all nodes.<br>
> > > >>><br>
> > > >>> Nothing has been written to geo-replication logs since I sent the tail of the log.<br>
> > > >>><br>
> > > >>> So I do not know what info to provide?<br>
> > > >>><br>
> > > >>><br>
> > > >>> Please, help me to find a way to solve this.<br>
> > > >>><br>
> > > >>><br>
> > > >>> Thanks!<br>
> > > >>><br>
> > > >>><br>
> > > >>> Regards<br>
> > > >>><br>
> > > >>> Marcus<br>
> > > >>><br>
> > > >>><br>
> > > >>> ________________________________<br>
> > > >>> Från: gluster-users-bounces@gluster.org <gluster-users-bounces@gluster.org> för Marcus Pedersén <marcus.pedersen@slu.se><br>
> > > >>> Skickat: den 12 juli 2018 08:51<br>
> > > >>> Till: Kotresh Hiremath Ravishankar<br>
> > > >>> Kopia: gluster-users@gluster.org<br>
> > > >>> Ämne: Re: [Gluster-users] Upgrade to 4.1.1 geo-replication does not work<br>
> > > >>><br>
> > > >>> Thanks Kotresh,<br>
> > > >>> I installed through the official centos channel, centos-release-gluster41.<br>
> > > >>> Isn't this fix included in centos install?<br>
> > > >>> I will have a look, test it tonight and come back to you!<br>
> > > >>><br>
> > > >>> Thanks a lot!<br>
> > > >>><br>
> > > >>> Regards<br>
> > > >>> Marcus<br>
> > > >>><br>
> > > >>> ################<br>
> > > >>> Marcus Pedersén<br>
> > > >>> Systemadministrator<br>
> > > >>> Interbull Centre<br>
> > > >>> ################<br>
> > > >>> Sent from my phone<br>
> > > >>> ################<br>
> > > >>><br>
> > > >>> Den 12 juli 2018 07:41 skrev Kotresh Hiremath Ravishankar <khiremat@redhat.com>:<br>
> > > >>><br>
> > > >>> Hi Marcus,<br>
> > > >>><br>
> > > >>> I think the fix [1] is needed in 4.1<br>
> > > >>> Could you please this out and let us know if that works for you?<br>
> > > >>><br>
> > > >>> [1] <a href="https://review.gluster.org/#/c/20207/">https://review.gluster.org/#/c/20207/</a><br>
> > > >>><br>
> > > >>> Thanks,<br>
> > > >>> Kotresh HR<br>
> > > >>><br>
> > > >>> On Thu, Jul 12, 2018 at 1:49 AM, Marcus Pedersén <marcus.pedersen@slu.se> wrote:<br>
> > > >>><br>
> > > >>> Hi all,<br>
> > > >>><br>
> > > >>> I have upgraded from 3.12.9 to 4.1.1 and been following upgrade instructions for offline upgrade.<br>
> > > >>><br>
> > > >>> I upgraded geo-replication side first 1 x (2+1) and the master side after that 2 x (2+1).<br>
> > > >>><br>
> > > >>> Both clusters works the way they should on their own.<br>
> > > >>><br>
> > > >>> After upgrade on master side status for all geo-replication nodes is Stopped.<br>
> > > >>><br>
> > > >>> I tried to start the geo-replication from master node and response back was started successfully.<br>
> > > >>><br>
> > > >>> Status again .... Stopped<br>
> > > >>><br>
> > > >>> Tried to start again and get response started successfully, after that all glusterd crashed on all master nodes.<br>
> > > >>><br>
> > > >>> After a restart of all glusterd the master cluster was up again.<br>
> > > >>><br>
> > > >>> Status for geo-replication is still Stopped and every try to start it after this gives the response successful but still status Stopped.<br>
> > > >>><br>
> > > >>><br>
> > > >>> Please help me get the geo-replication up and running again.<br>
> > > >>><br>
> > > >>><br>
> > > >>> Best regards<br>
> > > >>><br>
> > > >>> Marcus Pedersén<br>
> > > >>><br>
> > > >>><br>
> > > >>> Part of geo-replication log from master node:<br>
> > > >>><br>
> > > >>> [2018-07-11 18:42:48.941760] I [changelogagent(/urd-gds/gluster):73:__init__] ChangelogAgent: Agent listining...<br>
> > > >>> [2018-07-11 18:42:48.947567] I [resource(/urd-gds/gluster):1780:connect_remote] SSH: Initializing SSH connection between master and slave...<br>
> > > >>> [2018-07-11 18:42:49.363514] E [syncdutils(/urd-gds/gluster):304:log_raise_exception] <top>: connection to peer is broken<br>
> > > >>> [2018-07-11 18:42:49.364279] E [resource(/urd-gds/gluster):210:errlog] Popen: command returned error cmd=ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-replication/secret\<br>
> > > >>> .pem -p 22 -oControlMaster=auto -S /tmp/gsyncd-aux-ssh-hjRhBo/7e5534547f3675a710a107722317484f.sock geouser@urd-gds-geo-000 /nonexistent/gsyncd --session-owner 5e94eb7d-219f-4741-a179-d4ae6b50c7ee --local-id .%\<br>
> > > >>> 2Furd-gds%2Fgluster --local-node urd-gds-001 -N --listen --timeout 120 gluster://localhost:urd-gds-volume error=2<br>
> > > >>> [2018-07-11 18:42:49.364586] E [resource(/urd-gds/gluster):214:logerr] Popen: ssh> usage: gsyncd.py [-h]<br>
> > > >>> [2018-07-11 18:42:49.364799] E [resource(/urd-gds/gluster):214:logerr] Popen: ssh><br>
> > > >>> [2018-07-11 18:42:49.364989] E [resource(/urd-gds/gluster):214:logerr] Popen: ssh> {monitor-status,monitor,worker,agent,slave,status,config-check,config-get,config-set,config-reset,voluuidget,d\<br>
> > > >>> elete}<br>
> > > >>> [2018-07-11 18:42:49.365210] E [resource(/urd-gds/gluster):214:logerr] Popen: ssh> ...<br>
> > > >>> [2018-07-11 18:42:49.365408] E [resource(/urd-gds/gluster):214:logerr] Popen: ssh> gsyncd.py: error: argument subcmd: invalid choice: '5e94eb7d-219f-4741-a179-d4ae6b50c7ee' (choose from 'monitor-status', 'monit\<br>
> > > >>> or', 'worker', 'agent', 'slave', 'status', 'config-check', 'config-get', 'config-set', 'config-reset', 'voluuidget', 'delete')<br>
> > > >>> [2018-07-11 18:42:49.365919] I [syncdutils(/urd-gds/gluster):271:finalize] <top>: exiting.<br>
> > > >>> [2018-07-11 18:42:49.369316] I [repce(/urd-gds/gluster):92:service_loop] RepceServer: terminating on reaching EOF.<br>
> > > >>> [2018-07-11 18:42:49.369921] I [syncdutils(/urd-gds/gluster):271:finalize] <top>: exiting.<br>
> > > >>> [2018-07-11 18:42:49.369694] I [monitor(monitor):353:monitor] Monitor: worker died before establishing connection brick=/urd-gds/gluster<br>
> > > >>> [2018-07-11 18:42:59.492762] I [monitor(monitor):280:monitor] Monitor: starting gsyncd worker brick=/urd-gds/gluster slave_node=ssh://geouser@urd-gds-geo-000:gluster://localhost:urd-gds-volume<br>
> > > >>> [2018-07-11 18:42:59.558491] I [resource(/urd-gds/gluster):1780:connect_remote] SSH: Initializing SSH connection between master and slave...<br>
> > > >>> [2018-07-11 18:42:59.559056] I [changelogagent(/urd-gds/gluster):73:__init__] ChangelogAgent: Agent listining...<br>
> > > >>> [2018-07-11 18:42:59.945693] E [syncdutils(/urd-gds/gluster):304:log_raise_exception] <top>: connection to peer is broken<br>
> > > >>> [2018-07-11 18:42:59.946439] E [resource(/urd-gds/gluster):210:errlog] Popen: command returned error cmd=ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-replication/secret\<br>
> > > >>> .pem -p 22 -oControlMaster=auto -S /tmp/gsyncd-aux-ssh-992bk7/7e5534547f3675a710a107722317484f.sock geouser@urd-gds-geo-000 /nonexistent/gsyncd --session-owner 5e94eb7d-219f-4741-a179-d4ae6b50c7ee --local-id .%\<br>
> > > >>> 2Furd-gds%2Fgluster --local-node urd-gds-001 -N --listen --timeout 120 gluster://localhost:urd-gds-volume error=2<br>
> > > >>> [2018-07-11 18:42:59.946748] E [resource(/urd-gds/gluster):214:logerr] Popen: ssh> usage: gsyncd.py [-h]<br>
> > > >>> [2018-07-11 18:42:59.946962] E [resource(/urd-gds/gluster):214:logerr] Popen: ssh><br>
> > > >>> [2018-07-11 18:42:59.947150] E [resource(/urd-gds/gluster):214:logerr] Popen: ssh> {monitor-status,monitor,worker,agent,slave,status,config-check,config-get,config-set,config-reset,voluuidget,d\<br>
> > > >>> elete}<br>
> > > >>> [2018-07-11 18:42:59.947369] E [resource(/urd-gds/gluster):214:logerr] Popen: ssh> ...<br>
> > > >>> [2018-07-11 18:42:59.947552] E [resource(/urd-gds/gluster):214:logerr] Popen: ssh> gsyncd.py: error: argument subcmd: invalid choice: '5e94eb7d-219f-4741-a179-d4ae6b50c7ee' (choose from 'monitor-status', 'monit\<br>
> > > >>> or', 'worker', 'agent', 'slave', 'status', 'config-check', 'config-get', 'config-set', 'config-reset', 'voluuidget', 'delete')<br>
> > > >>> [2018-07-11 18:42:59.948046] I [syncdutils(/urd-gds/gluster):271:finalize] <top>: exiting.<br>
> > > >>> [2018-07-11 18:42:59.951392] I [repce(/urd-gds/gluster):92:service_loop] RepceServer: terminating on reaching EOF.<br>
> > > >>> [2018-07-11 18:42:59.951760] I [syncdutils(/urd-gds/gluster):271:finalize] <top>: exiting.<br>
> > > >>> [2018-07-11 18:42:59.951817] I [monitor(monitor):353:monitor] Monitor: worker died before establishing connection brick=/urd-gds/gluster<br>
> > > >>> [2018-07-11 18:43:10.54580] I [monitor(monitor):280:monitor] Monitor: starting gsyncd worker brick=/urd-gds/gluster slave_node=ssh://geouser@urd-gds-geo-000:gluster://localhost:urd-gds-volume<br>
> > > >>> [2018-07-11 18:43:10.88356] I [monitor(monitor):345:monitor] Monitor: Changelog Agent died, Aborting Worker brick=/urd-gds/gluster<br>
> > > >>> [2018-07-11 18:43:10.88613] I [monitor(monitor):353:monitor] Monitor: worker died before establishing connection brick=/urd-gds/gluster<br>
> > > >>> [2018-07-11 18:43:20.112435] I [gsyncdstatus(monitor):242:set_worker_status] GeorepStatus: Worker Status Change status=inconsistent<br>
> > > >>> [2018-07-11 18:43:20.112885] E [syncdutils(monitor):331:log_raise_exception] <top>: FAIL:<br>
> > > >>> Traceback (most recent call last):<br>
> > > >>> File "/usr/libexec/glusterfs/python/syncdaemon/syncdutils.py", line 361, in twrap<br>
> > > >>> except:<br>
> > > >>> File "/usr/libexec/glusterfs/python/syncdaemon/monitor.py", line 428, in wmon<br>
> > > >>> sys.exit()<br>
> > > >>> TypeError: 'int' object is not iterable<br>
> > > >>> [2018-07-11 18:43:20.114610] I [syncdutils(monitor):271:finalize] <top>: exiting.<br>
> > > >>><br>
> > > >>> ---<br>
> > > >>> När du skickar e-post till SLU så innebär detta att SLU behandlar dina personuppgifter. För att läsa mer om hur detta går till, klicka här<br>
> > > >>> E-mailing SLU will result in SLU processing your personal data. For more information on how this is done, click here<br>
> > > >>><br>
> > > >>><br>
> > > >>> _______________________________________________<br>
> > > >>> Gluster-users mailing list<br>
> > > >>> Gluster-users@gluster.org<br>
> > > >>> <a href="https://lists.gluster.org/mailman/listinfo/gluster-users">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
> > > >>><br>
> > > >>><br>
> > > >>><br>
> > > >>><br>
> > > >>> --<br>
> > > >>> Thanks and Regards,<br>
> > > >>> Kotresh H R<br>
> > > >>><br>
> > > >>><br>
> > > >>> ---<br>
> > > >>> När du skickar e-post till SLU så innebär detta att SLU behandlar dina personuppgifter. För att läsa mer om hur detta går till, klicka här<br>
> > > >>> E-mailing SLU will result in SLU processing your personal data. For more information on how this is done, click here<br>
> > > >>><br>
> > > >>> ---<br>
> > > >>> När du skickar e-post till SLU så innebär detta att SLU behandlar dina personuppgifter. För att läsa mer om hur detta går till, klicka här<br>
> > > >>> E-mailing SLU will result in SLU processing your personal data. For more information on how this is done, click here<br>
> > > >>><br>
> > > >>><br>
> > > >>><br>
> > > >>><br>
> > > >>> --<br>
> > > >>> Thanks and Regards,<br>
> > > >>> Kotresh H R<br>
> > > >>><br>
> > > >>><br>
> > > >>> ---<br>
> > > >>> När du skickar e-post till SLU så innebär detta att SLU behandlar dina personuppgifter. För att läsa mer om hur detta går till, klicka här<br>
> > > >>> E-mailing SLU will result in SLU processing your personal data. For more information on how this is done, click here<br>
> > > >>><br>
> > > >>> ---<br>
> > > >>> När du skickar e-post till SLU så innebär detta att SLU behandlar dina personuppgifter. För att läsa mer om hur detta går till, klicka här<br>
> > > >>> E-mailing SLU will result in SLU processing your personal data. For more information on how this is done, click here<br>
> > > >>><br>
> > > >>> ---<br>
> > > >>> När du skickar e-post till SLU så innebär detta att SLU behandlar dina personuppgifter. För att läsa mer om hur detta går till, klicka här<br>
> > > >>> E-mailing SLU will result in SLU processing your personal data. For more information on how this is done, click here<br>
> > > >><br>
> > > >><br>
> > > >><br>
> > > >><br>
> > > >> --<br>
> > > >> Thanks and Regards,<br>
> > > >> Kotresh H R<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > --<br>
> > > > Thanks and Regards,<br>
> > > > Kotresh H R<br>
> > > ><br>
> > > > ---<br>
> > > > När du skickar e-post till SLU så innebär detta att SLU behandlar dina personuppgifter. För att läsa mer om hur detta går till, klicka här<br>
> > > > E-mailing SLU will result in SLU processing your personal data. For more information on how this is done, click here<br>
> > > ><br>
> > > > _______________________________________________<br>
> > > > Gluster-users mailing list<br>
> > > > Gluster-users@gluster.org<br>
> > > > <a href="https://lists.gluster.org/mailman/listinfo/gluster-users">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
> > ><br>
> > ><br>
> > > ---<br>
> > > När du skickar e-post till SLU så innebär detta att SLU behandlar dina personuppgifter. För att läsa mer om hur detta går till, klicka här<br>
> > > E-mailing SLU will result in SLU processing your personal data. For more information on how this is done, click here<br>
> ><br>
> > - Sunny<br>
> > ---<br>
> > När du skickar e-post till SLU så innebär detta att SLU behandlar dina personuppgifter. För att läsa mer om hur detta går till, klicka här <<a href="https://www.slu.se/om-slu/kontakta-slu/personuppgifter/">https://www.slu.se/om-slu/kontakta-slu/personuppgifter/</a>><br>
> > E-mailing SLU will result in SLU processing your personal data. For more information on how this is done, click here <<a href="https://www.slu.se/en/about-slu/contact-slu/personal-data/">https://www.slu.se/en/about-slu/contact-slu/personal-data/</a>><br>
><br>
><br>
> ---<br>
> När du skickar e-post till SLU så innebär detta att SLU behandlar dina personuppgifter. För att läsa mer om hur detta går till, klicka här<br>
> E-mailing SLU will result in SLU processing your personal data. For more information on how this is done, click here<br>
</div>
</span></font></div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<p>---<br>
När du skickar e-post till SLU så innebär detta att SLU behandlar dina personuppgifter. För att läsa mer om hur detta går till, klicka
<a href="https://www.slu.se/om-slu/kontakta-slu/personuppgifter/">här </a><br>
E-mailing SLU will result in SLU processing your personal data. For more information on how this is done, click
<a href="https://www.slu.se/en/about-slu/contact-slu/personal-data/">here </a></p>
</div>
<p>---<br>
När du skickar e-post till SLU så innebär detta att SLU behandlar dina personuppgifter. För att läsa mer om hur detta går till, klicka
<a href="https://www.slu.se/om-slu/kontakta-slu/personuppgifter/">här </a><br>
E-mailing SLU will result in SLU processing your personal data. For more information on how this is done, click
<a href="https://www.slu.se/en/about-slu/contact-slu/personal-data/">here </a></p>
</body>
</html>