<div dir="ltr">Ahhh iptables strikes back ! You were right. Ive now got Peer probe success. :) <br><br><div>*** Lesson Learned In killing IPTables on Fedora16 ?***<br>
</div><br>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 just manually flushed them according
to the script below stolen from <a href="http://www.cyberciti.biz/tips/linux-iptables-how-to-flush-all-rules.html.." target="_blank">http://www.cyberciti.biz/tips/linux-iptables-how-to-flush-all-rules.html..</a>.. <br>
<br><pre>#!/bin/sh
echo "Stopping firewall and allowing everyone..."
iptables -F
iptables -X
iptables -t nat -F
iptables -t nat -X
iptables -t mangle -F
iptables -t mangle -X
iptables -P INPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPT</pre></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, May 20, 2013 at 7:00 PM, Anand Avati <span dir="ltr"><<a href="mailto:anand.avati@gmail.com" target="_blank">anand.avati@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Looks like there might be a firewall (iptables) in the way? Can you flush all iptables rules and retry - just to confirm?<div>
<br></div><div>Avati</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">
On Mon, May 20, 2013 at 3:45 PM, Jay Vyas <span dir="ltr"><<a href="mailto:jayunit100@gmail.com" target="_blank">jayunit100@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div class="h5">
<div dir="ltr"><div>Hi gluster: <br></div><div><br></div>Im getting the cryptic 107 error, (I guess this means gluster can't see a peer)... <br><br><div><div>gluster peer probe vm-2<br>peer probe: failed: Probe returned with unknown errno 107<br>
<br></div><div>When I can effectively ssh and ping a given server. </div><div><br></div><div>I've seen other threads regarding this, some of them to deal with the "net.ipv4.ip_nonlocal_bind" parameter, and also a bug <a href="https://bugzilla.redhat.com/show_bug.cgi?id=890587" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=890587</a> ... <br>
<br></div><div>But I'm still not sure what the nature of this error is - any thoughts?<span><font color="#888888"><br clear="all"></font></span></div><span><font color="#888888"><div><br>
<br>-- <br>Jay Vyas<br><a href="http://jayunit100.blogspot.com" target="_blank">http://jayunit100.blogspot.com</a>
</div></font></span></div></div>
<br></div></div>_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a><br></blockquote></div><br></div>
</blockquote></div><br><br clear="all"><br>-- <br>Jay Vyas<br><a href="http://jayunit100.blogspot.com" target="_blank">http://jayunit100.blogspot.com</a>
</div>