[Bugs] [Bug 1210557] gluster peer probe with selinux enables throws error
bugzilla at redhat.com
bugzilla at redhat.com
Fri Apr 10 05:36:22 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1210557
Bhaskarakiran <byarlaga at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(byarlaga at redhat.c |
|om) |
--- Comment #2 from Bhaskarakiran <byarlaga at redhat.com> ---
I have flushed the iptables and ping is working..
[root at transformers glusterfs]# ping ninja
PING ninja.lab.eng.blr.redhat.com (10.70.34.68) 56(84) bytes of data.
64 bytes from ninja.lab.eng.blr.redhat.com (10.70.34.68): icmp_seq=1 ttl=64
time=0.435 ms
64 bytes from ninja.lab.eng.blr.redhat.com (10.70.34.68): icmp_seq=2 ttl=64
time=0.206 ms
^C
--- ninja.lab.eng.blr.redhat.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1558ms
rtt min/avg/max/mdev = 0.206/0.320/0.435/0.115 ms
[root at transformers glusterfs]# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
[root at transformers glusterfs]#
[root at ninja ~]# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
[root at ninja ~]# ping transformers
PING transformers.lab.eng.blr.redhat.com (10.70.34.44) 56(84) bytes of data.
64 bytes from transformers.lab.eng.blr.redhat.com (10.70.34.44): icmp_seq=1
ttl=64 time=0.230 ms
64 bytes from transformers.lab.eng.blr.redhat.com (10.70.34.44): icmp_seq=2
ttl=64 time=0.174 ms
^C
--- transformers.lab.eng.blr.redhat.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1726ms
rtt min/avg/max/mdev = 0.174/0.202/0.230/0.028 ms
[root at ninja ~]#
--
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