[Gluster-users] peer probe fails (107)
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 the net.ipv4.ip_nonlocal_bind parameter, and also a bug https://bugzilla.redhat.com/show_bug.cgi?id=890587 ... But I'm still not sure what the nature of this error is - any thoughts? -- Jay Vyas http://jayunit100.blogspot.com ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] peer probe fails (107)
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 jayunit...@gmail.com wrote: 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 the net.ipv4.ip_nonlocal_bind parameter, and also a bug https://bugzilla.redhat.com/show_bug.cgi?id=890587 ... But I'm still not sure what the nature of this error is - any thoughts? -- Jay Vyas http://jayunit100.blogspot.com ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] peer probe fails (107)
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 just manually flushed them according to the script below stolen from http://www.cyberciti.biz/tips/linux-iptables-how-to-flush-all-rules.html #!/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 On Mon, May 20, 2013 at 7:00 PM, Anand Avati anand.av...@gmail.com wrote: 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 jayunit...@gmail.com wrote: 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 the net.ipv4.ip_nonlocal_bind parameter, and also a bug https://bugzilla.redhat.com/show_bug.cgi?id=890587 ... But I'm still not sure what the nature of this error is - any thoughts? -- Jay Vyas http://jayunit100.blogspot.com ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users -- Jay Vyas http://jayunit100.blogspot.com ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] peer probe fails (107)
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 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 just manually flushed them according to the script below stolen from http://www.cyberciti.biz/tips/linux-iptables-how-to-flush-all-rules.html #!/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 On Mon, May 20, 2013 at 7:00 PM, Anand Avati anand.av...@gmail.com mailto:anand.av...@gmail.com wrote: 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 jayunit...@gmail.com mailto:jayunit...@gmail.com wrote: 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 the net.ipv4.ip_nonlocal_bind parameter, and also a bug https://bugzilla.redhat.com/show_bug.cgi?id=890587 ... But I'm still not sure what the nature of this error is - any thoughts? -- Jay Vyas http://jayunit100.blogspot.com ___ Gluster-users mailing list Gluster-users@gluster.org mailto:Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users -- Jay Vyas http://jayunit100.blogspot.com ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] peer probe fails
Per Raghav on #gluster, i started with -LDEBUG and captured the logs. Logs are at ... http://pastie.org/3496176 It also has the glusterd and glustefs version info. thanx, deepak On 03/01/2012 10:43 AM, Deepak C Shetty wrote: On 02/29/2012 10:11 PM, Vijay Bellur wrote: On 02/29/2012 07:38 PM, Deepak C Shetty wrote: Latest cli.log ... [2012-02-01 03:39:33.096303] W [rpc-transport.c:183:rpc_transport_load] 0-rpc-transport: missing 'option transport-type'. defaulting to socket [2012-02-01 03:39:33.220545] E [socket.c:1713:socket_connect_finish] 0-glusterfs: connection to failed (Connection refused) [2012-02-01 03:41:40.198853] I [cli-cmd.c:142:cli_cmd_process] 0-: Exiting with: 110 [2012-02-01 21:04:39.178904] W [rpc-transport.c:183:rpc_transport_load] 0-rpc-transport: missing 'option transport-type'. defaulting to socket [2012-02-01 21:04:39.303686] E [socket.c:1713:socket_connect_finish] 0-glusterfs: connection to failed (Connection refused) Do you have firewalling on? Can you telnet to port 24007 on the machine being probed? Yes I am able to. Pls see the below output... tried using both hostname and IP, 24007 is not blocked. [root@llm65 ~]# telnet llm19.in.ibm.com 24007 Trying 9.124.111.25... Connected to llm19.in.ibm.com. Escape character is '^]'. ^] telnet q Connection closed. [root@llm65 ~]# [root@llm65 ~]# telnet 9.124.111.25 24007 Trying 9.124.111.25... Connected to 9.124.111.25. Escape character is '^]'. ^] telnet q Connection closed. What else can I do to debug further ? I looked up errno 107 - it stands for transport endpoint not connected. Do i need to do anything special on the destination / peer for the host / src to connect ? thanx, deepak ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] peer probe fails
On 02/29/2012 10:11 PM, Vijay Bellur wrote: On 02/29/2012 07:38 PM, Deepak C Shetty wrote: Latest cli.log ... [2012-02-01 03:39:33.096303] W [rpc-transport.c:183:rpc_transport_load] 0-rpc-transport: missing 'option transport-type'. defaulting to socket [2012-02-01 03:39:33.220545] E [socket.c:1713:socket_connect_finish] 0-glusterfs: connection to failed (Connection refused) [2012-02-01 03:41:40.198853] I [cli-cmd.c:142:cli_cmd_process] 0-: Exiting with: 110 [2012-02-01 21:04:39.178904] W [rpc-transport.c:183:rpc_transport_load] 0-rpc-transport: missing 'option transport-type'. defaulting to socket [2012-02-01 21:04:39.303686] E [socket.c:1713:socket_connect_finish] 0-glusterfs: connection to failed (Connection refused) Do you have firewalling on? Can you telnet to port 24007 on the machine being probed? Yes I am able to. Pls see the below output... tried using both hostname and IP, 24007 is not blocked. [root@llm65 ~]# telnet llm19.in.ibm.com 24007 Trying 9.124.111.25... Connected to llm19.in.ibm.com. Escape character is '^]'. ^] telnet q Connection closed. [root@llm65 ~]# [root@llm65 ~]# telnet 9.124.111.25 24007 Trying 9.124.111.25... Connected to 9.124.111.25. Escape character is '^]'. ^] telnet q Connection closed. What else can I do to debug further ? I looked up errno 107 - it stands for transport endpoint not connected. Do i need to do anything special on the destination / peer for the host / src to connect ? thanx, deepak ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
