<div dir="ltr">I was wondering if "Transport endpoint is not connected" was a problem or if that was normal since it is an arbiter node. Since it wasn't normal, I took a look around on that server and found firewalld had kicked in. I disabled it and now I'm back in business.<div><br></div><div>Thank you.</div><div><br></div><div><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 7, 2016 at 7:01 PM, Ravishankar N <span dir="ltr"><<a href="mailto:ravishankar@redhat.com" target="_blank">ravishankar@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 01/08/2016 04:08 AM, Kyle Harris wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Brick kvm:/export/brick1<br>
<br>
Status: Transport endpoint is not connected<br>
<br>
</blockquote></span>
This seems to indicate that this brick is down. I don't see it being shown in the output of 'gluster volume status` either. Could you check that? In all probability those 12 entries need to be healed to this (arbiter) brick.<br>
<br>
-Ravi<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div><br></div><div><br></div></div></div></div>
</div></div></div>