I don't remember how far back firewalld goes, but from at least Fedora
17 on, iptables is managed by the firewalld service, not iptables.
Perhaps that's what you were running in to.
On 05/20/2013 04:11 PM, Jay Vyas wrote:
Ahhh iptables strikes back ! You were right. Ive now got Peer probe
su
Ahhh iptables strikes back ! You were right. Ive now got Peer probe
success. :)
*** Lesson Learned In killing IPTables on Fedora16 ?***
Im on Fedora 16, so this might not be relevant to everyone.. but... Rather
than "service iptables stop" (maybe this wasnt really killing all the ip
rules), I j
Looks like there might be a firewall (iptables) in the way? Can you flush
all iptables rules and retry - just to confirm?
Avati
On Mon, May 20, 2013 at 3:45 PM, Jay Vyas wrote:
> Hi gluster:
>
> Im getting the cryptic 107 error, (I guess this means gluster can't see a
> peer)...
>
> gluster p
Hi gluster:
Im getting the cryptic 107 error, (I guess this means gluster can't see a
peer)...
gluster peer probe vm-2
peer probe: failed: Probe returned with unknown errno 107
When I can effectively ssh and ping a given server.
I've seen other threads regarding this, some of them to deal with
