<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 11, 2016 at 11:52 AM, Abeer Mahendroo <span dir="ltr"><<a href="mailto:abeerm@gmail.com" target="_blank">abeerm@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><p class="MsoNormal">Hi all.<span></span></p>
<p class="MsoNormal">We had a strange issue with Gluster 3.8.4 under RHEL 7.2. <span></span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal">Initially, the partition storing the Gluster bricks ran out
of space. We tried recovering after expanding the underlying partition.
Eventually we decided to ‘reset’ Gluster, create the volume again from scratch.
I tried purging gluster by running something like:<span></span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal">yum remove –y ‘glusterfs*’<span></span></p>
<p class="MsoNormal">rm -rf /var/lib/glusterd<span></span></p>
<p class="MsoNormal">rm –rf /etc/gluster*<span></span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal">Reinstalling gluster:<span></span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal">yum install –y glusterfs-server<span></span></p>
<p class="MsoNormal">systemctl start glusterd<span></span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal">Now a simple peer probe operation crashes the daemon:<span></span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal">$ gluster peer probe <any-valid-hostname><span></span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal">Connection failed. Please check if gluster daemon is
operational.</p></div></blockquote><div><br></div><div>This typically indicates that glusterd is not running. Could you check if glusterd instance is running on this node? If not any error message on glusterd log file?<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><p class="MsoNormal"><span></span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal">Looks like there is something I missed in the filesystem.<span></span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal">On a clean gluster install on another host,<span></span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal">$ gluster peer probe <any-valid-hostname><span></span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal">peer probe: failed: Probe returned with Transport endpoint
is not connected</p></div></blockquote><div><br></div><div>Same question here, is glusterd running on the host which you are trying to probe? Are the firewalld/iptables rules clean?<br><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><p class="MsoNormal"><span></span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal">Which is expected.<span></span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal">So somehow my clean install is not clean any more. This host
I can rebuild, but would be good to know the issue if this occurs on a host
that cannot easily be rebuilt.<span></span></p></div>
<br>______________________________<wbr>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://www.gluster.org/<wbr>mailman/listinfo/gluster-users</a><br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><br></div>--Atin<br></div></div>
</div></div>