Re: Unable To Heal On 3.7 Branch With Arbiter

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

Thank you.



On Thu, Jan 7, 2016 at 7:01 PM, Ravishankar N <ravishankar@xxxxxxxxxx> wrote:
On 01/08/2016 04:08 AM, Kyle Harris wrote:

Brick kvm:/export/brick1

Status: Transport endpoint is not connected

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.

-Ravi



--


_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux