Hi,
Unable to do peer probe... and unable to figure out whats the
reason from the gluster log.
can someone help ?
1) This is what i was trying...
gluster> peer probe llm19.in.ibm.com
Probe unsuccessful
Probe returned with unknown errno 107
gluster> peer probe 9.124.111.25
Probe unsuccessful
Probe returned with unknown errno 107
gluster> peer status
Number of Peers: 1
Hostname: 9.126.89.241
Uuid: 4eae4c67-f063-45d5-b10c-0381d258d3e7
State: Probe Sent to Peer (Connected)
gluster> quit
2) System I am trying to probe, is pingable from the host...
[root at llm65 glusterfs]# ping llm19.in.ibm.com
PING llm19.in.ibm.com (9.124.111.25) 56(84) bytes of data.
64 bytes from llm19.in.ibm.com (9.124.111.25): icmp_req=1 ttl=64
time=0.133 ms
64 bytes from llm19.in.ibm.com (9.124.111.25): icmp_req=2 ttl=64
time=0.124 ms
3) The system I am trying to probe, also has the gluster service running...
[root at llm19 ~]# ps -ef| grep gluster
root 31514 1 0 23:29 ? 00:00:01 /usr/sbin/glusterd -p
/var/run/glusterd.pid
root 31525 1 0 23:29 ? 00:00:00 /usr/sbin/glusterfs -f
/var/lib/glusterd/nfs/nfs-server.vol -p
/var/lib/glusterd/nfs/run/nfs.pid -l /var/log/glusterfs/nfs.log
4) From the gluster cli.log... on the host(llm65)...
[2012-02-29 23:27:43.261273] W [rpc-transport.c:183:rpc_transport_load]
0-rpc-transport: missing 'option transport-type'. defaulting to
"socket"
[2012-02-29 23:27:53.558575] I [cli-rpc-ops.c:114:gf_cli3_1_probe_cbk]
0-cli: Received resp to probe
[2012-02-29 23:27:53.558675] E [cli-rpc-ops.c:162:gf_cli3_1_probe_cbk]
0-glusterd: Probe failed with op_ret -1 and op_errno 107
[2012-02-29 23:27:53.558720] W [cli-rl.c:94:cli_rl_process_line]
0-glusterfs: failed to process line
[2012-02-29 23:28:10.161658] I [cli-rpc-ops.c:114:gf_cli3_1_probe_cbk]
0-cli: Received resp to probe
[2012-02-29 23:28:10.161713] E [cli-rpc-ops.c:162:gf_cli3_1_probe_cbk]
0-glusterd: Probe failed with op_ret -1 and op_errno 107
[2012-02-29 23:28:10.161757] W [cli-rl.c:94:cli_rl_process_line]
0-glusterfs: failed to process line
Appreciate a response.
thanx,
deepak
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) On 02/29/2012 06:06 PM, Deepak C Shetty wrote:> Hi, > Unable to do peer probe... and unable to figure out whats the > reason from the gluster log. > can someone help ? > > 1) This is what i was trying... > > gluster> peer probe llm19.in.ibm.com > Probe unsuccessful > Probe returned with unknown errno 107 > > gluster> peer probe 9.124.111.25 > Probe unsuccessful > Probe returned with unknown errno 107 > > gluster> peer status > Number of Peers: 1 > > Hostname: 9.126.89.241 > Uuid: 4eae4c67-f063-45d5-b10c-0381d258d3e7 > State: Probe Sent to Peer (Connected) > > gluster> quit > > 2) System I am trying to probe, is pingable from the host... > > [root at llm65 glusterfs]# ping llm19.in.ibm.com > PING llm19.in.ibm.com (9.124.111.25) 56(84) bytes of data. > 64 bytes from llm19.in.ibm.com (9.124.111.25): icmp_req=1 ttl=64 > time=0.133 ms > 64 bytes from llm19.in.ibm.com (9.124.111.25): icmp_req=2 ttl=64 > time=0.124 ms > > 3) The system I am trying to probe, also has the gluster service > running... > > [root at llm19 ~]# ps -ef| grep gluster > root 31514 1 0 23:29 ? 00:00:01 /usr/sbin/glusterd -p > /var/run/glusterd.pid > root 31525 1 0 23:29 ? 00:00:00 /usr/sbin/glusterfs -f > /var/lib/glusterd/nfs/nfs-server.vol -p > /var/lib/glusterd/nfs/run/nfs.pid -l /var/log/glusterfs/nfs.log > > > 4) From the gluster cli.log... on the host(llm65)... > > [2012-02-29 23:27:43.261273] W > [rpc-transport.c:183:rpc_transport_load] 0-rpc-transport: missing > 'option transport-type'. defaulting to "socket" > [2012-02-29 23:27:53.558575] I [cli-rpc-ops.c:114:gf_cli3_1_probe_cbk] > 0-cli: Received resp to probe > [2012-02-29 23:27:53.558675] E [cli-rpc-ops.c:162:gf_cli3_1_probe_cbk] > 0-glusterd: Probe failed with op_ret -1 and op_errno 107 > [2012-02-29 23:27:53.558720] W [cli-rl.c:94:cli_rl_process_line] > 0-glusterfs: failed to process line > [2012-02-29 23:28:10.161658] I [cli-rpc-ops.c:114:gf_cli3_1_probe_cbk] > 0-cli: Received resp to probe > [2012-02-29 23:28:10.161713] E [cli-rpc-ops.c:162:gf_cli3_1_probe_cbk] > 0-glusterd: Probe failed with op_ret -1 and op_errno 107 > [2012-02-29 23:28:10.161757] W [cli-rl.c:94:cli_rl_process_line] > 0-glusterfs: failed to process line > > > Appreciate a response. > > thanx, > deepak > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users > >
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 at 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 at llm65 ~]# [root at 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