<div dir="ltr">The flood is indeed fixed for us on 5.5. However, the crashes are not.<br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><br>Sincerely,<br>Artem<br><br>--<br>Founder, <a href="http://www.androidpolice.com" target="_blank">Android Police</a>, <a href="http://www.apkmirror.com/" style="font-size:12.8000001907349px" target="_blank">APK Mirror</a><span style="font-size:12.8000001907349px">, Illogical Robot LLC</span></div><div dir="ltr"><a href="http://beerpla.net/" target="_blank">beerpla.net</a> | <a href="https://plus.google.com/+ArtemRussakovskii" target="_blank">+ArtemRussakovskii</a> | <a href="http://twitter.com/ArtemR" target="_blank">@ArtemR</a><br></div></div></div></div></div></div></div></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Mar 18, 2019 at 5:41 AM Hu Bert <<a href="mailto:revirii@googlemail.com">revirii@googlemail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Amar,<br>
<br>
if you refer to this bug:<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1674225" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1674225</a> : in the test<br>
setup i haven't seen those entries, while copying & deleting a few GBs<br>
of data. For a final statement we have to wait until i updated our<br>
live gluster servers - could take place on tuesday or wednesday.<br>
<br>
Maybe other users can do an update to 5.4 as well and report back here.<br>
<br>
<br>
Hubert<br>
<br>
<br>
<br>
Am Mo., 18. März 2019 um 11:36 Uhr schrieb Amar Tumballi Suryanarayan<br>
<<a href="mailto:atumball@redhat.com" target="_blank">atumball@redhat.com</a>>:<br>
><br>
> Hi Hu Bert,<br>
><br>
> Appreciate the feedback. Also are the other boiling issues related to logs fixed now?<br>
><br>
> -Amar<br>
><br>
> On Mon, Mar 18, 2019 at 3:54 PM Hu Bert <<a href="mailto:revirii@googlemail.com" target="_blank">revirii@googlemail.com</a>> wrote:<br>
>><br>
>> update: upgrade from 5.3 -> 5.5 in a replicate 3 test setup with 2<br>
>> volumes done. In 'gluster peer status' the peers stay connected during<br>
>> the upgrade, no 'peer rejected' messages. No cksum mismatches in the<br>
>> logs. Looks good :-)<br>
>><br>
>> Am Mo., 18. März 2019 um 09:54 Uhr schrieb Hu Bert <<a href="mailto:revirii@googlemail.com" target="_blank">revirii@googlemail.com</a>>:<br>
>> ><br>
>> > Good morning :-)<br>
>> ><br>
>> > for debian the packages are there:<br>
>> > <a href="https://download.gluster.org/pub/gluster/glusterfs/5/5.5/Debian/stretch/amd64/apt/pool/main/g/glusterfs/" rel="noreferrer" target="_blank">https://download.gluster.org/pub/gluster/glusterfs/5/5.5/Debian/stretch/amd64/apt/pool/main/g/glusterfs/</a><br>
>> ><br>
>> > I'll do an upgrade of a test installation 5.3 -> 5.5 and see if there<br>
>> > are some errors etc. and report back.<br>
>> ><br>
>> > btw: no release notes for 5.4 and 5.5 so far?<br>
>> > <a href="https://docs.gluster.org/en/latest/release-notes/" rel="noreferrer" target="_blank">https://docs.gluster.org/en/latest/release-notes/</a> ?<br>
>> ><br>
>> > Am Fr., 15. März 2019 um 14:28 Uhr schrieb Shyam Ranganathan<br>
>> > <<a href="mailto:srangana@redhat.com" target="_blank">srangana@redhat.com</a>>:<br>
>> > ><br>
>> > > We created a 5.5 release tag, and it is under packaging now. It should<br>
>> > > be packaged and ready for testing early next week and should be released<br>
>> > > close to mid-week next week.<br>
>> > ><br>
>> > > Thanks,<br>
>> > > Shyam<br>
>> > > On 3/13/19 12:34 PM, Artem Russakovskii wrote:<br>
>> > > > Wednesday now with no update :-/<br>
>> > > ><br>
>> > > > Sincerely,<br>
>> > > > Artem<br>
>> > > ><br>
>> > > > --<br>
>> > > > Founder, Android Police <<a href="http://www.androidpolice.com" rel="noreferrer" target="_blank">http://www.androidpolice.com</a>>, APK Mirror<br>
>> > > > <<a href="http://www.apkmirror.com/" rel="noreferrer" target="_blank">http://www.apkmirror.com/</a>>, Illogical Robot LLC<br>
>> > > > <a href="http://beerpla.net" rel="noreferrer" target="_blank">beerpla.net</a> <<a href="http://beerpla.net/" rel="noreferrer" target="_blank">http://beerpla.net/</a>> | +ArtemRussakovskii<br>
>> > > > <<a href="https://plus.google.com/+ArtemRussakovskii" rel="noreferrer" target="_blank">https://plus.google.com/+ArtemRussakovskii</a>> | @ArtemR<br>
>> > > > <<a href="http://twitter.com/ArtemR" rel="noreferrer" target="_blank">http://twitter.com/ArtemR</a>><br>
>> > > ><br>
>> > > ><br>
>> > > > On Tue, Mar 12, 2019 at 10:28 AM Artem Russakovskii <<a href="mailto:archon810@gmail.com" target="_blank">archon810@gmail.com</a><br>
>> > > > <mailto:<a href="mailto:archon810@gmail.com" target="_blank">archon810@gmail.com</a>>> wrote:<br>
>> > > ><br>
>> > > > Hi Amar,<br>
>> > > ><br>
>> > > > Any updates on this? I'm still not seeing it in OpenSUSE build<br>
>> > > > repos. Maybe later today?<br>
>> > > ><br>
>> > > > Thanks.<br>
>> > > ><br>
>> > > > Sincerely,<br>
>> > > > Artem<br>
>> > > ><br>
>> > > > --<br>
>> > > > Founder, Android Police <<a href="http://www.androidpolice.com" rel="noreferrer" target="_blank">http://www.androidpolice.com</a>>, APK Mirror<br>
>> > > > <<a href="http://www.apkmirror.com/" rel="noreferrer" target="_blank">http://www.apkmirror.com/</a>>, Illogical Robot LLC<br>
>> > > > <a href="http://beerpla.net" rel="noreferrer" target="_blank">beerpla.net</a> <<a href="http://beerpla.net/" rel="noreferrer" target="_blank">http://beerpla.net/</a>> | +ArtemRussakovskii<br>
>> > > > <<a href="https://plus.google.com/+ArtemRussakovskii" rel="noreferrer" target="_blank">https://plus.google.com/+ArtemRussakovskii</a>> | @ArtemR<br>
>> > > > <<a href="http://twitter.com/ArtemR" rel="noreferrer" target="_blank">http://twitter.com/ArtemR</a>><br>
>> > > ><br>
>> > > ><br>
>> > > > On Wed, Mar 6, 2019 at 10:30 PM Amar Tumballi Suryanarayan<br>
>> > > > <<a href="mailto:atumball@redhat.com" target="_blank">atumball@redhat.com</a> <mailto:<a href="mailto:atumball@redhat.com" target="_blank">atumball@redhat.com</a>>> wrote:<br>
>> > > ><br>
>> > > > We are talking days. Not weeks. Considering already it is<br>
>> > > > Thursday here. 1 more day for tagging, and packaging. May be ok<br>
>> > > > to expect it on Monday.<br>
>> > > ><br>
>> > > > -Amar<br>
>> > > ><br>
>> > > > On Thu, Mar 7, 2019 at 11:54 AM Artem Russakovskii<br>
>> > > > <<a href="mailto:archon810@gmail.com" target="_blank">archon810@gmail.com</a> <mailto:<a href="mailto:archon810@gmail.com" target="_blank">archon810@gmail.com</a>>> wrote:<br>
>> > > ><br>
>> > > > Is the next release going to be an imminent hotfix, i.e.<br>
>> > > > something like today/tomorrow, or are we talking weeks?<br>
>> > > ><br>
>> > > > Sincerely,<br>
>> > > > Artem<br>
>> > > ><br>
>> > > > --<br>
>> > > > Founder, Android Police <<a href="http://www.androidpolice.com" rel="noreferrer" target="_blank">http://www.androidpolice.com</a>>, APK<br>
>> > > > Mirror <<a href="http://www.apkmirror.com/" rel="noreferrer" target="_blank">http://www.apkmirror.com/</a>>, Illogical Robot LLC<br>
>> > > > <a href="http://beerpla.net" rel="noreferrer" target="_blank">beerpla.net</a> <<a href="http://beerpla.net/" rel="noreferrer" target="_blank">http://beerpla.net/</a>> | +ArtemRussakovskii<br>
>> > > > <<a href="https://plus.google.com/+ArtemRussakovskii" rel="noreferrer" target="_blank">https://plus.google.com/+ArtemRussakovskii</a>> | @ArtemR<br>
>> > > > <<a href="http://twitter.com/ArtemR" rel="noreferrer" target="_blank">http://twitter.com/ArtemR</a>><br>
>> > > ><br>
>> > > ><br>
>> > > > On Tue, Mar 5, 2019 at 11:09 AM Artem Russakovskii<br>
>> > > > <<a href="mailto:archon810@gmail.com" target="_blank">archon810@gmail.com</a> <mailto:<a href="mailto:archon810@gmail.com" target="_blank">archon810@gmail.com</a>>> wrote:<br>
>> > > ><br>
>> > > > Ended up downgrading to 5.3 just in case. Peer status<br>
>> > > > and volume status are OK now.<br>
>> > > ><br>
>> > > > zypper install --oldpackage glusterfs-5.3-lp150.100.1<br>
>> > > > Loading repository data...<br>
>> > > > Reading installed packages...<br>
>> > > > Resolving package dependencies...<br>
>> > > ><br>
>> > > > Problem: glusterfs-5.3-lp150.100.1.x86_64 requires<br>
>> > > > libgfapi0 = 5.3, but this requirement cannot be provided<br>
>> > > > not installable providers:<br>
>> > > > libgfapi0-5.3-lp150.100.1.x86_64[glusterfs]<br>
>> > > > Solution 1: Following actions will be done:<br>
>> > > > downgrade of libgfapi0-5.4-lp150.100.1.x86_64 to<br>
>> > > > libgfapi0-5.3-lp150.100.1.x86_64<br>
>> > > > downgrade of libgfchangelog0-5.4-lp150.100.1.x86_64 to<br>
>> > > > libgfchangelog0-5.3-lp150.100.1.x86_64<br>
>> > > > downgrade of libgfrpc0-5.4-lp150.100.1.x86_64 to<br>
>> > > > libgfrpc0-5.3-lp150.100.1.x86_64<br>
>> > > > downgrade of libgfxdr0-5.4-lp150.100.1.x86_64 to<br>
>> > > > libgfxdr0-5.3-lp150.100.1.x86_64<br>
>> > > > downgrade of libglusterfs0-5.4-lp150.100.1.x86_64 to<br>
>> > > > libglusterfs0-5.3-lp150.100.1.x86_64<br>
>> > > > Solution 2: do not install glusterfs-5.3-lp150.100.1.x86_64<br>
>> > > > Solution 3: break glusterfs-5.3-lp150.100.1.x86_64 by<br>
>> > > > ignoring some of its dependencies<br>
>> > > ><br>
>> > > > Choose from above solutions by number or cancel<br>
>> > > > [1/2/3/c] (c): 1<br>
>> > > > Resolving dependencies...<br>
>> > > > Resolving package dependencies...<br>
>> > > ><br>
>> > > > The following 6 packages are going to be downgraded:<br>
>> > > > glusterfs libgfapi0 libgfchangelog0 libgfrpc0<br>
>> > > > libgfxdr0 libglusterfs0<br>
>> > > ><br>
>> > > > 6 packages to downgrade.<br>
>> > > ><br>
>> > > > Sincerely,<br>
>> > > > Artem<br>
>> > > ><br>
>> > > > --<br>
>> > > > Founder, Android Police<br>
>> > > > <<a href="http://www.androidpolice.com" rel="noreferrer" target="_blank">http://www.androidpolice.com</a>>, APK Mirror<br>
>> > > > <<a href="http://www.apkmirror.com/" rel="noreferrer" target="_blank">http://www.apkmirror.com/</a>>, Illogical Robot LLC<br>
>> > > > <a href="http://beerpla.net" rel="noreferrer" target="_blank">beerpla.net</a> <<a href="http://beerpla.net/" rel="noreferrer" target="_blank">http://beerpla.net/</a>> | +ArtemRussakovskii<br>
>> > > > <<a href="https://plus.google.com/+ArtemRussakovskii" rel="noreferrer" target="_blank">https://plus.google.com/+ArtemRussakovskii</a>> | @ArtemR<br>
>> > > > <<a href="http://twitter.com/ArtemR" rel="noreferrer" target="_blank">http://twitter.com/ArtemR</a>><br>
>> > > ><br>
>> > > ><br>
>> > > > On Tue, Mar 5, 2019 at 10:57 AM Artem Russakovskii<br>
>> > > > <<a href="mailto:archon810@gmail.com" target="_blank">archon810@gmail.com</a> <mailto:<a href="mailto:archon810@gmail.com" target="_blank">archon810@gmail.com</a>>> wrote:<br>
>> > > ><br>
>> > > > Noticed the same when upgrading from 5.3 to 5.4, as<br>
>> > > > mentioned.<br>
>> > > ><br>
>> > > > I'm confused though. Is actual replication affected,<br>
>> > > > because the 5.4 server and the 3x 5.3 servers still<br>
>> > > > show heal info as all 4 connected, and the files<br>
>> > > > seem to be replicating correctly as well.<br>
>> > > ><br>
>> > > > So what's actually affected - just the status<br>
>> > > > command, or leaving 5.4 on one of the nodes is doing<br>
>> > > > some damage to the underlying fs? Is it fixable by<br>
>> > > > tweaking transport.socket.ssl-enabled? Does<br>
>> > > > upgrading all servers to 5.4 resolve it, or should<br>
>> > > > we revert back to 5.3?<br>
>> > > ><br>
>> > > > Sincerely,<br>
>> > > > Artem<br>
>> > > ><br>
>> > > > --<br>
>> > > > Founder, Android Police<br>
>> > > > <<a href="http://www.androidpolice.com" rel="noreferrer" target="_blank">http://www.androidpolice.com</a>>, APK Mirror<br>
>> > > > <<a href="http://www.apkmirror.com/" rel="noreferrer" target="_blank">http://www.apkmirror.com/</a>>, Illogical Robot LLC<br>
>> > > > <a href="http://beerpla.net" rel="noreferrer" target="_blank">beerpla.net</a> <<a href="http://beerpla.net/" rel="noreferrer" target="_blank">http://beerpla.net/</a>> |<br>
>> > > > +ArtemRussakovskii<br>
>> > > > <<a href="https://plus.google.com/+ArtemRussakovskii" rel="noreferrer" target="_blank">https://plus.google.com/+ArtemRussakovskii</a>><br>
>> > > > | @ArtemR <<a href="http://twitter.com/ArtemR" rel="noreferrer" target="_blank">http://twitter.com/ArtemR</a>><br>
>> > > ><br>
>> > > ><br>
>> > > > On Tue, Mar 5, 2019 at 2:02 AM Hu Bert<br>
>> > > > <<a href="mailto:revirii@googlemail.com" target="_blank">revirii@googlemail.com</a><br>
>> > > > <mailto:<a href="mailto:revirii@googlemail.com" target="_blank">revirii@googlemail.com</a>>> wrote:<br>
>> > > ><br>
>> > > > fyi: did a downgrade 5.4 -> 5.3 and it worked.<br>
>> > > > all replicas are up and<br>
>> > > > running. Awaiting updated v5.4.<br>
>> > > ><br>
>> > > > thx :-)<br>
>> > > ><br>
>> > > > Am Di., 5. März 2019 um 09:26 Uhr schrieb Hari<br>
>> > > > Gowtham <<a href="mailto:hgowtham@redhat.com" target="_blank">hgowtham@redhat.com</a><br>
>> > > > <mailto:<a href="mailto:hgowtham@redhat.com" target="_blank">hgowtham@redhat.com</a>>>:<br>
>> > > > ><br>
>> > > > > There are plans to revert the patch causing<br>
>> > > > this error and rebuilt 5.4.<br>
>> > > > > This should happen faster. the rebuilt 5.4<br>
>> > > > should be void of this upgrade issue.<br>
>> > > > ><br>
>> > > > > In the meantime, you can use 5.3 for this cluster.<br>
>> > > > > Downgrading to 5.3 will work if it was just<br>
>> > > > one node that was upgrade to 5.4<br>
>> > > > > and the other nodes are still in 5.3.<br>
>> > > > ><br>
>> > > > > On Tue, Mar 5, 2019 at 1:07 PM Hu Bert<br>
>> > > > <<a href="mailto:revirii@googlemail.com" target="_blank">revirii@googlemail.com</a><br>
>> > > > <mailto:<a href="mailto:revirii@googlemail.com" target="_blank">revirii@googlemail.com</a>>> wrote:<br>
>> > > > > ><br>
>> > > > > > Hi Hari,<br>
>> > > > > ><br>
>> > > > > > thx for the hint. Do you know when this will<br>
>> > > > be fixed? Is a downgrade<br>
>> > > > > > 5.4 -> 5.3 a possibility to fix this?<br>
>> > > > > ><br>
>> > > > > > Hubert<br>
>> > > > > ><br>
>> > > > > > Am Di., 5. März 2019 um 08:32 Uhr schrieb<br>
>> > > > Hari Gowtham <<a href="mailto:hgowtham@redhat.com" target="_blank">hgowtham@redhat.com</a><br>
>> > > > <mailto:<a href="mailto:hgowtham@redhat.com" target="_blank">hgowtham@redhat.com</a>>>:<br>
>> > > > > > ><br>
>> > > > > > > Hi,<br>
>> > > > > > ><br>
>> > > > > > > This is a known issue we are working on.<br>
>> > > > > > > As the checksum differs between the<br>
>> > > > updated and non updated node, the<br>
>> > > > > > > peers are getting rejected.<br>
>> > > > > > > The bricks aren't coming because of the<br>
>> > > > same issue.<br>
>> > > > > > ><br>
>> > > > > > > More about the issue:<br>
>> > > > <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1685120" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1685120</a><br>
>> > > > > > ><br>
>> > > > > > > On Tue, Mar 5, 2019 at 12:56 PM Hu Bert<br>
>> > > > <<a href="mailto:revirii@googlemail.com" target="_blank">revirii@googlemail.com</a><br>
>> > > > <mailto:<a href="mailto:revirii@googlemail.com" target="_blank">revirii@googlemail.com</a>>> wrote:<br>
>> > > > > > > ><br>
>> > > > > > > > Interestingly: gluster volume status<br>
>> > > > misses gluster1, while heal<br>
>> > > > > > > > statistics show gluster1:<br>
>> > > > > > > ><br>
>> > > > > > > > gluster volume status workdata<br>
>> > > > > > > > Status of volume: workdata<br>
>> > > > > > > > Gluster process<br>
>> > > > TCP Port RDMA Port Online Pid<br>
>> > > > > > > ><br>
>> > > > ------------------------------------------------------------------------------<br>
>> > > > > > > > Brick gluster2:/gluster/md4/workdata<br>
>> > > > 49153 0 Y 1723<br>
>> > > > > > > > Brick gluster3:/gluster/md4/workdata<br>
>> > > > 49153 0 Y 2068<br>
>> > > > > > > > Self-heal Daemon on localhost<br>
>> > > > N/A N/A Y 1732<br>
>> > > > > > > > Self-heal Daemon on gluster3<br>
>> > > > N/A N/A Y 2077<br>
>> > > > > > > ><br>
>> > > > > > > > vs.<br>
>> > > > > > > ><br>
>> > > > > > > > gluster volume heal workdata statistics<br>
>> > > > heal-count<br>
>> > > > > > > > Gathering count of entries to be healed<br>
>> > > > on volume workdata has been successful<br>
>> > > > > > > ><br>
>> > > > > > > > Brick gluster1:/gluster/md4/workdata<br>
>> > > > > > > > Number of entries: 0<br>
>> > > > > > > ><br>
>> > > > > > > > Brick gluster2:/gluster/md4/workdata<br>
>> > > > > > > > Number of entries: 10745<br>
>> > > > > > > ><br>
>> > > > > > > > Brick gluster3:/gluster/md4/workdata<br>
>> > > > > > > > Number of entries: 10744<br>
>> > > > > > > ><br>
>> > > > > > > > Am Di., 5. März 2019 um 08:18 Uhr<br>
>> > > > schrieb Hu Bert <<a href="mailto:revirii@googlemail.com" target="_blank">revirii@googlemail.com</a><br>
>> > > > <mailto:<a href="mailto:revirii@googlemail.com" target="_blank">revirii@googlemail.com</a>>>:<br>
>> > > > > > > > ><br>
>> > > > > > > > > Hi Miling,<br>
>> > > > > > > > ><br>
>> > > > > > > > > well, there are such entries, but<br>
>> > > > those haven't been a problem during<br>
>> > > > > > > > > install and the last kernel<br>
>> > > > update+reboot. The entries look like:<br>
>> > > > > > > > ><br>
>> > > > > > > > > PUBLIC_IP <a href="http://gluster2.alpserver.de" rel="noreferrer" target="_blank">gluster2.alpserver.de</a><br>
>> > > > <<a href="http://gluster2.alpserver.de" rel="noreferrer" target="_blank">http://gluster2.alpserver.de</a>> gluster2<br>
>> > > > > > > > ><br>
>> > > > > > > > > 192.168.0.50 gluster1<br>
>> > > > > > > > > 192.168.0.51 gluster2<br>
>> > > > > > > > > 192.168.0.52 gluster3<br>
>> > > > > > > > ><br>
>> > > > > > > > > 'ping gluster2' resolves to LAN IP; I<br>
>> > > > removed the last entry in the<br>
>> > > > > > > > > 1st line, did a reboot ... no, didn't<br>
>> > > > help. From<br>
>> > > > > > > > > /var/log/glusterfs/glusterd.log<br>
>> > > > > > > > > on gluster 2:<br>
>> > > > > > > > ><br>
>> > > > > > > > > [2019-03-05 07:04:36.188128] E [MSGID:<br>
>> > > > 106010]<br>
>> > > > > > > > ><br>
>> > > > [glusterd-utils.c:3483:glusterd_compare_friend_volume]<br>
>> > > > 0-management:<br>
>> > > > > > > > > Version of Cksums persistent differ.<br>
>> > > > local cksum = 3950307018, remote<br>
>> > > > > > > > > cksum = 455409345 on peer gluster1<br>
>> > > > > > > > > [2019-03-05 07:04:36.188314] I [MSGID:<br>
>> > > > 106493]<br>
>> > > > > > > > ><br>
>> > > > [glusterd-handler.c:3843:glusterd_xfer_friend_add_resp]<br>
>> > > > 0-glusterd:<br>
>> > > > > > > > > Responded to gluster1 (0), ret: 0,<br>
>> > > > op_ret: -1<br>
>> > > > > > > > ><br>
>> > > > > > > > > Interestingly there are no entries in<br>
>> > > > the brick logs of the rejected<br>
>> > > > > > > > > server. Well, not surprising as no<br>
>> > > > brick process is running. The<br>
>> > > > > > > > > server gluster1 is still in rejected<br>
>> > > > state.<br>
>> > > > > > > > ><br>
>> > > > > > > > > 'gluster volume start workdata force'<br>
>> > > > starts the brick process on<br>
>> > > > > > > > > gluster1, and some heals are happening<br>
>> > > > on gluster2+3, but via 'gluster<br>
>> > > > > > > > > volume status workdata' the volumes<br>
>> > > > still aren't complete.<br>
>> > > > > > > > ><br>
>> > > > > > > > > gluster1:<br>
>> > > > > > > > ><br>
>> > > > ------------------------------------------------------------------------------<br>
>> > > > > > > > > Brick gluster1:/gluster/md4/workdata<br>
>> > > > 49152 0 Y 2523<br>
>> > > > > > > > > Self-heal Daemon on localhost<br>
>> > > > N/A N/A Y 2549<br>
>> > > > > > > > ><br>
>> > > > > > > > > gluster2:<br>
>> > > > > > > > > Gluster process<br>
>> > > > TCP Port RDMA Port Online Pid<br>
>> > > > > > > > ><br>
>> > > > ------------------------------------------------------------------------------<br>
>> > > > > > > > > Brick gluster2:/gluster/md4/workdata<br>
>> > > > 49153 0 Y 1723<br>
>> > > > > > > > > Brick gluster3:/gluster/md4/workdata<br>
>> > > > 49153 0 Y 2068<br>
>> > > > > > > > > Self-heal Daemon on localhost<br>
>> > > > N/A N/A Y 1732<br>
>> > > > > > > > > Self-heal Daemon on gluster3<br>
>> > > > N/A N/A Y 2077<br>
>> > > > > > > > ><br>
>> > > > > > > > ><br>
>> > > > > > > > > Hubert<br>
>> > > > > > > > ><br>
>> > > > > > > > > Am Di., 5. März 2019 um 07:58 Uhr<br>
>> > > > schrieb Milind Changire <<a href="mailto:mchangir@redhat.com" target="_blank">mchangir@redhat.com</a><br>
>> > > > <mailto:<a href="mailto:mchangir@redhat.com" target="_blank">mchangir@redhat.com</a>>>:<br>
>> > > > > > > > > ><br>
>> > > > > > > > > > There are probably DNS entries or<br>
>> > > > /etc/hosts entries with the public IP Addresses<br>
>> > > > that the host names (gluster1, gluster2,<br>
>> > > > gluster3) are getting resolved to.<br>
>> > > > > > > > > > /etc/resolv.conf would tell which is<br>
>> > > > the default domain searched for the node names<br>
>> > > > and the DNS servers which respond to the queries.<br>
>> > > > > > > > > ><br>
>> > > > > > > > > ><br>
>> > > > > > > > > > On Tue, Mar 5, 2019 at 12:14 PM Hu<br>
>> > > > Bert <<a href="mailto:revirii@googlemail.com" target="_blank">revirii@googlemail.com</a><br>
>> > > > <mailto:<a href="mailto:revirii@googlemail.com" target="_blank">revirii@googlemail.com</a>>> wrote:<br>
>> > > > > > > > > >><br>
>> > > > > > > > > >> Good morning,<br>
>> > > > > > > > > >><br>
>> > > > > > > > > >> i have a replicate 3 setup with 2<br>
>> > > > volumes, running on version 5.3 on<br>
>> > > > > > > > > >> debian stretch. This morning i<br>
>> > > > upgraded one server to version 5.4 and<br>
>> > > > > > > > > >> rebooted the machine; after the<br>
>> > > > restart i noticed that:<br>
>> > > > > > > > > >><br>
>> > > > > > > > > >> - no brick process is running<br>
>> > > > > > > > > >> - gluster volume status only shows<br>
>> > > > the server itself:<br>
>> > > > > > > > > >> gluster volume status workdata<br>
>> > > > > > > > > >> Status of volume: workdata<br>
>> > > > > > > > > >> Gluster process<br>
>> > > > TCP Port RDMA Port Online Pid<br>
>> > > > > > > > > >><br>
>> > > > ------------------------------------------------------------------------------<br>
>> > > > > > > > > >> Brick<br>
>> > > > gluster1:/gluster/md4/workdata N/A<br>
>> > > > N/A N N/A<br>
>> > > > > > > > > >> NFS Server on localhost<br>
>> > > > N/A N/A N N/A<br>
>> > > > > > > > > >><br>
>> > > > > > > > > >> - gluster peer status on the server<br>
>> > > > > > > > > >> gluster peer status<br>
>> > > > > > > > > >> Number of Peers: 2<br>
>> > > > > > > > > >><br>
>> > > > > > > > > >> Hostname: gluster3<br>
>> > > > > > > > > >> Uuid:<br>
>> > > > c7b4a448-ca6a-4051-877f-788f9ee9bc4a<br>
>> > > > > > > > > >> State: Peer Rejected (Connected)<br>
>> > > > > > > > > >><br>
>> > > > > > > > > >> Hostname: gluster2<br>
>> > > > > > > > > >> Uuid:<br>
>> > > > 162fea82-406a-4f51-81a3-e90235d8da27<br>
>> > > > > > > > > >> State: Peer Rejected (Connected)<br>
>> > > > > > > > > >><br>
>> > > > > > > > > >> - gluster peer status on the other<br>
>> > > > 2 servers:<br>
>> > > > > > > > > >> gluster peer status<br>
>> > > > > > > > > >> Number of Peers: 2<br>
>> > > > > > > > > >><br>
>> > > > > > > > > >> Hostname: gluster1<br>
>> > > > > > > > > >> Uuid:<br>
>> > > > 9a360776-7b58-49ae-831e-a0ce4e4afbef<br>
>> > > > > > > > > >> State: Peer Rejected (Connected)<br>
>> > > > > > > > > >><br>
>> > > > > > > > > >> Hostname: gluster3<br>
>> > > > > > > > > >> Uuid:<br>
>> > > > c7b4a448-ca6a-4051-877f-788f9ee9bc4a<br>
>> > > > > > > > > >> State: Peer in Cluster (Connected)<br>
>> > > > > > > > > >><br>
>> > > > > > > > > >> I noticed that, in the brick logs,<br>
>> > > > i see that the public IP is used<br>
>> > > > > > > > > >> instead of the LAN IP. brick logs<br>
>> > > > from one of the volumes:<br>
>> > > > > > > > > >><br>
>> > > > > > > > > >> rejected node:<br>
>> > > > <a href="https://pastebin.com/qkpj10Sd" rel="noreferrer" target="_blank">https://pastebin.com/qkpj10Sd</a><br>
>> > > > > > > > > >> connected nodes:<br>
>> > > > <a href="https://pastebin.com/8SxVVYFV" rel="noreferrer" target="_blank">https://pastebin.com/8SxVVYFV</a><br>
>> > > > > > > > > >><br>
>> > > > > > > > > >> Why is the public IP suddenly used<br>
>> > > > instead of the LAN IP? Killing all<br>
>> > > > > > > > > >> gluster processes and rebooting<br>
>> > > > (again) didn't help.<br>
>> > > > > > > > > >><br>
>> > > > > > > > > >><br>
>> > > > > > > > > >> Thx,<br>
>> > > > > > > > > >> Hubert<br>
>> > > > > > > > > >><br>
>> > > > _______________________________________________<br>
>> > > > > > > > > >> Gluster-users mailing list<br>
>> > > > > > > > > >> <a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
>> > > > <mailto:<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a>><br>
>> > > > > > > > > >><br>
>> > > > <a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
>> > > > > > > > > ><br>
>> > > > > > > > > ><br>
>> > > > > > > > > ><br>
>> > > > > > > > > > --<br>
>> > > > > > > > > > Milind<br>
>> > > > > > > > > ><br>
>> > > > > > > ><br>
>> > > > _______________________________________________<br>
>> > > > > > > > Gluster-users mailing list<br>
>> > > > > > > > <a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
>> > > > <mailto:<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a>><br>
>> > > > > > > ><br>
>> > > > <a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
>> > > > > > ><br>
>> > > > > > ><br>
>> > > > > > ><br>
>> > > > > > > --<br>
>> > > > > > > Regards,<br>
>> > > > > > > Hari Gowtham.<br>
>> > > > ><br>
>> > > > ><br>
>> > > > ><br>
>> > > > > --<br>
>> > > > > Regards,<br>
>> > > > > Hari Gowtham.<br>
>> > > > _______________________________________________<br>
>> > > > Gluster-users mailing list<br>
>> > > > <a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
>> > > > <mailto:<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a>><br>
>> > > > <a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
>> > > ><br>
>> > > > _______________________________________________<br>
>> > > > Gluster-users mailing list<br>
>> > > > <a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a> <mailto:<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a>><br>
>> > > > <a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
>> > > ><br>
>> > > ><br>
>> > > ><br>
>> > > > --<br>
>> > > > Amar Tumballi (amarts)<br>
>> > > ><br>
>> > > ><br>
>> > > > _______________________________________________<br>
>> > > > Gluster-users mailing list<br>
>> > > > <a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
>> > > > <a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
>> > > ><br>
>> > > _______________________________________________<br>
>> > > Gluster-users mailing list<br>
>> > > <a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
>> > > <a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
><br>
><br>
><br>
> --<br>
> Amar Tumballi (amarts)<br>
</blockquote></div>