[Bugs] [Bug 1271545] New: unable to peer nodes, without flushing iptables. Getting error "Probe returned with Transport endpoint is not connected"
bugzilla at redhat.com
bugzilla at redhat.com
Wed Oct 14 09:18:53 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1271545
Bug ID: 1271545
Summary: unable to peer nodes,without flushing iptables.
Getting error "Probe returned with Transport endpoint
is not connected"
Product: GlusterFS
Version: 3.7.5
Component: glusterd
Assignee: bugs at gluster.org
Reporter: nchilaka at redhat.com
CC: bugs at gluster.org, gluster-bugs at redhat.com
If I try to peer probe another gluster node, "I am getting Probe returned with
Transport endpoint is not connected" error.
Only when i flush iptables using iptables -F on both the nodes, I am able to
peer nodes.
[root at dhcp37-165 ~]# rpm -qa|grep gluster
glusterfs-libs-3.7.5-0.19.git0f5c3e8.el7.centos.x86_64
glusterfs-client-xlators-3.7.5-0.19.git0f5c3e8.el7.centos.x86_64
glusterfs-extra-xlators-3.7.5-0.19.git0f5c3e8.el7.centos.x86_64
glusterfs-server-3.7.5-0.19.git0f5c3e8.el7.centos.x86_64
glusterfs-api-devel-3.7.5-0.19.git0f5c3e8.el7.centos.x86_64
glusterfs-debuginfo-3.7.5-0.19.git0f5c3e8.el7.centos.x86_64
glusterfs-3.7.5-0.19.git0f5c3e8.el7.centos.x86_64
glusterfs-api-3.7.5-0.19.git0f5c3e8.el7.centos.x86_64
glusterfs-cli-3.7.5-0.19.git0f5c3e8.el7.centos.x86_64
glusterfs-fuse-3.7.5-0.19.git0f5c3e8.el7.centos.x86_64
python-gluster-3.7.5-0.19.git0f5c3e8.el7.centos.noarch
glusterfs-devel-3.7.5-0.19.git0f5c3e8.el7.centos.x86_64
glusterfs-geo-replication-3.7.5-0.19.git0f5c3e8.el7.centos.x86_64
[root at dhcp37-165 ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.2 Beta (Maipo)
[root at dhcp37-165 ~]# sestatus
SELinux status: enabled
SELinuxfs mount: /sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: targeted
Current mode: enforcing
Mode from config file: enforcing
Policy MLS status: enabled
Policy deny_unknown status: allowed
Max kernel policy version: 28
[root at dhcp37-165 ~]#
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list