<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>
<div>Hi all,<br/>
<br/>
I can confirm that a downgrade works. Gfs 3.13.2 with rsync 3.1.3 and Ubuntu 16.04.3 amd64. <br/>
>From my point of view, rsync fails because the gsyncd process is already exited which leads to a non existing target path for rsync. But it don't really see the connection to the libc-changelog.</div>
<div>http://changelogs.ubuntu.com/changelogs/pool/main/g/glibc/glibc_2.23-0ubuntu10/changelog</div>
<div><br/>
Best regards,<br/>
Tino</div>
<div>
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin:0 0 10px 0;"><b>Gesendet:</b> Montag, 29. Januar 2018 um 20:56 Uhr<br/>
<b>Von:</b> "Dietmar Putz" <dietmar.putz@3qsdn.com><br/>
<b>An:</b> "Gluster Users" <gluster-users@gluster.org><br/>
<b>Betreff:</b> Re: [Gluster-users] geo-replication command rsync returned with 3</div>
<div name="quoted-content">
<div style="background-color: rgb(255,255,255);">
<p>Hi all,</p>
by downgrade of<br/>
ii libc6:amd64 2.23-0ubuntu10<br/>
<br/>
to<br/>
<br/>
ii libc6:amd64 2.23-0ubuntu3<br/>
<br/>
the problem was solved. at least in gfs testenvironment running gfs 3.13.2 and 3.7.20 and on our productive environment with 3.7.18.<br/>
possibly it helps someone...<br/>
<br/>
best regards<br/>
Dietmar<br/>
<br/>
<p> </p>
<div class="moz-cite-prefix">Am 25.01.2018 um 14:06 schrieb Dietmar Putz:</div>
<blockquote>
<p>Hi Kotresh,</p>
<p>thanks for your response...</p>
<p>i have made further tests based on ubuntu 16.04.3 (latest upgrades) and gfs 3.12.5 with following rsync version :</p>
<tt>1. ii rsync 3.1.1-3ubuntu1<br/>
2. ii rsync 3.1.1-3ubuntu1.2<br/>
3. ii rsync 3.1.2-2ubuntu0.1</tt><br/>
<br/>
in each test all nodes had the same rsync version installed. all tests failed with the below shown error.<br/>
then i started a test with the same setup. this time upgrades for ubuntu 16.04.3 were disabled.<br/>
again i have tested the above shown rsync versions on all nodes. the geo replication works fine in any case.<br/>
then i have installed 3.1.1-3ubuntu1.2 on each node as it is installed with latest ubuntu upgrade.<br/>
afterwards i have just upgraded all slave nodes with the latest ubuntu upgrades, reboot...the geo-replication still works fine.<br/>
after upgrade and reboot of the master nodes with the latest ubuntu upgrades the below shown error appeared again... geo rep is broken.<br/>
<br/>
i believe one of the below shown packages caused the error because directly after upgrade of these packages the error appeared<br/>
on the corresponding master node....<br/>
anyone else who has experienced this issue...?<br/>
any help would be appreciated.<br/>
<br/>
best regards<br/>
Dietmar<br/>
<br/>
<br/>
<br/>
<div class="moz-cite-prefix">Am 25.01.2018 um 04:14 schrieb Kotresh Hiremath Ravishankar:</div>
<blockquote>
<div>
<div>
<div>It is clear that rsync is failing. Are the rsync versions on all masters and slave nodes same?</div>
I have seen that has caused problems sometimes.<br/>
</div>
-Kotresh HR</div>
<div class="gmail_extra">
<div class="gmail_quote">On Wed, Jan 24, 2018 at 10:29 PM, Dietmar Putz <span><<a href="mailto:dietmar.putz@3qsdn.com" onclick="parent.window.location.href='dietmar.putz@3qsdn.com'; return false;" target="_blank">dietmar.putz@3qsdn.com</a>></span> wrote:
<blockquote class="gmail_quote" style="margin: 0 0 0 0.8ex;border-left: 1.0px rgb(204,204,204) solid;padding-left: 1.0ex;">
<div>
<p>Hi all,</p>
i have made some tests on the latest Ubuntu 16.04.3 server image. Upgrades were disabled...<br/>
the configuration was always the same...a distributed replicated volume on 4 VM's with geo-replication to a dist. repl .volume on 4 VM's.<br/>
i started with 3.7.20, upgrade to 3.8.15, to 3.10.9 to 3.12.5. After each upgrade i have tested the geo-replication which worked well anytime.<br/>
then i have made an update / upgrade on the first master node. directly after upgrade the below shown error appeared on that node.<br/>
after upgrade on the second master node the error appeared there also... geo replication is faulty. <br/>
<br/>
this error affects gfs 3.7.20, 3.8.15, 3.10.9 and 3.12.5 on Ubuntu 16.04.3<br/>
in one test i have updated rsync from 3.1.1 to 3.1.2 but with no effect.<br/>
<br/>
does anyone else experienced this behavior...any idea ?<br/>
<br/>
best regards<br/>
Dietmar<br/>
<p> </p>
<p><tt>gfs 3.12.5 geo-rep log on master :</tt></p>
<p><tt>[2018-01-24 15:50:35.347959] I [master(/brick1/mvol1):1385:crawl] _GMaster: slave's time stime=(1516808792, 0) </tt><br/>
<tt>[2018-01-24 15:50:35.604094] I [master(/brick1/mvol1):1863:syncjob] Syncer: Sync Time Taken duration=0.0294 num_files=1 job=2 return_code=3 </tt><br/>
<tt>[2018-01-24 15:50:35.605490] E [resource(/brick1/mvol1):210:errlog] Popen: command returned error cmd=rsync -aR0 --inplace --files-from=- --super --stats --numeric-ids --no-implied-dirs --existing --xattrs --acls --ignore-missing-args . -e ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-replication/secret.pem -p 22 -oControlMaster=auto -S /tmp/gsyncd-aux-ssh-MZwEp2/cbad1c5f88978ecd713bdb1478fbabbe.sock --compress root@gl-node5-int:/proc/2013/cwd error=3 </tt><br/>
<tt>[2018-01-24 15:50:35.628978] I [syncdutils(/brick1/mvol1):271:finalize] <top>: exiting.</tt></p>
<p> </p>
<p> </p>
<p>after this upgrade one server fails :<br/>
<tt>Start-Date: 2018-01-18 04:33:52<br/>
Commandline: /usr/bin/unattended-upgrade<br/>
Upgrade:<br/>
libdns-export162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.8, 1:9.10.3.dfsg.P4-8ubuntu1.10),<br/>
libisccfg140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.8, 1:9.10.3.dfsg.P4-8ubuntu1.10),<br/>
bind9-host:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.8, 1:9.10.3.dfsg.P4-8ubuntu1.10),<br/>
dnsutils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.8, 1:9.10.3.dfsg.P4-8ubuntu1.10),<br/>
libc6:amd64 (2.23-0ubuntu9, 2.23-0ubuntu10),<br/>
libisc160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.8, 1:9.10.3.dfsg.P4-8ubuntu1.10),<br/>
locales:amd64 (2.23-0ubuntu9, 2.23-0ubuntu10),<br/>
libisc-export160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.8, 1:9.10.3.dfsg.P4-8ubuntu1.10),<br/>
libc-bin:amd64 (2.23-0ubuntu9, 2.23-0ubuntu10),<br/>
liblwres141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.8, 1:9.10.3.dfsg.P4-8ubuntu1.10),<br/>
libdns162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.8, 1:9.10.3.dfsg.P4-8ubuntu1.10),<br/>
multiarch-support:amd64 (2.23-0ubuntu9, 2.23-0ubuntu10),<br/>
libisccc140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.8, 1:9.10.3.dfsg.P4-8ubuntu1.10),<br/>
libbind9-140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.8, 1:9.10.3.dfsg.P4-8ubuntu1.10)<br/>
End-Date: 2018-01-18 04:34:32 </tt></p>
<p> </p>
<p><br/>
<tt><tt>strace rsync :</tt></tt></p>
<p><tt><tt>30743 23:34:47 newfstatat(3, "6737", {st_mode=S_IFDIR|0755, st_size=4096, ...}, AT_SYMLINK_NOFOLLOW) = 0<br/>
30743 23:34:47 newfstatat(3, "6741", {st_mode=S_IFDIR|0755, st_size=4096, ...}, AT_SYMLINK_NOFOLLOW) = 0<br/>
30743 23:34:47 getdents(3, /* 0 entries */, 131072) = 0<br/>
30743 23:34:47 munmap(0x7fa4feae7000, 135168) = 0<br/>
30743 23:34:47 close(3) = 0<br/>
30743 23:34:47 write(2, "rsync: getcwd(): No such file or directory (2)", 46) = 46<br/>
30743 23:34:47 write(2, "\n", 1) = 1<br/>
30743 23:34:47 rt_sigaction(SIGUSR1, {SIG_IGN, [], SA_RESTORER, 0x7fa4fdf404b0}, NULL, 8) = 0<br/>
30743 23:34:47 rt_sigaction(SIGUSR2, {SIG_IGN, [], SA_RESTORER, 0x7fa4fdf404b0}, NULL, 8) = 0<br/>
30743 23:34:47 write(2, "rsync error: errors selecting input/output files, dirs (code 3) at util.c(1056) [Receiver=3.1.1]", 96) = 96<br/>
30743 23:34:47 write(2, "\n", 1) = 1<br/>
30743 23:34:47 exit_group(3) = ?<br/>
30743 23:34:47 +++ exited with 3 +++</tt> </tt></p>
<p> </p>
<p> </p>
<div class="m_3318466771008572220moz-cite-prefix">Am 19.01.2018 um 17:27 schrieb Joe Julian:</div>
<blockquote>
<pre class="m_3318466771008572220k9mail">ubuntu 16.04</pre>
</blockquote>
</div>
<br/>
_______________________________________________<br/>
Gluster-users mailing list<br/>
<a href="mailto:Gluster-users@gluster.org" onclick="parent.window.location.href='Gluster-users@gluster.org'; return false;" target="_blank">Gluster-users@gluster.org</a><br/>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://lists.gluster.org/mailman/listinfo/gluster-users</a></blockquote>
</div>
<br/>
<br clear="all"/>
<br/>
--
<div class="gmail_signature">
<div>
<div>Thanks and Regards,</div>
Kotresh H R</div>
</div>
</div>
</blockquote>
<fieldset class="mimeAttachmentHeader"> </fieldset>
<pre>_______________________________________________
Gluster-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org" onclick="parent.window.location.href='Gluster-users@gluster.org'; return false;" target="_blank">Gluster-users@gluster.org</a>
<a class="moz-txt-link-freetext" href="http://lists.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://lists.gluster.org/mailman/listinfo/gluster-users</a></pre>
</blockquote>
<pre class="moz-signature">--
Dietmar Putz
3Q GmbH
Kurfürstendamm 102
D-10711 Berlin
Mobile: +49 171 / 90 160 39
Mail: <a class="moz-txt-link-abbreviated" href="mailto:dietmar.putz@3qsdn.com" onclick="parent.window.location.href='dietmar.putz@3qsdn.com'; return false;" target="_blank">dietmar.putz@3qsdn.com</a></pre>
_______________________________________________ Gluster-users mailing list Gluster-users@gluster.org <a href="http://lists.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://lists.gluster.org/mailman/listinfo/gluster-users</a></div>
</div>
</div>
</div>
</div></div></body></html>