Bug 763220 (GLUSTER-1488) - rdma client fails to connect to the servers
Summary: rdma client fails to connect to the servers
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-1488
Product: GlusterFS
Classification: Community
Component: transport
Version: mainline
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Raghavendra G
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-31 14:09 UTC by Anush Shetty
Modified: 2015-12-01 16:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Anush Shetty 2010-08-31 14:09:09 UTC
2010-08-31 07:04:02.489881] D [rdma.c:4210:rdma_handshake_pollerr] rpc-transport/rdma: client5: peer disconnected, cleaning up
[2010-08-31 07:04:02.491898] D [name.c:146:client_fill_address_family] client1: address-family not specified, guessing it to be inet/inet6
[2010-08-31 07:04:02.491981] E [rdma.c:4290:tcp_connect_finish] client2: tcp connect to  failed (No route to host)
[2010-08-31 07:04:02.491997] D [rdma.c:4210:rdma_handshake_pollerr] rpc-transport/rdma: client2: peer disconnected, cleaning up
[2010-08-31 07:04:02.494764] E [rdma.c:4290:tcp_connect_finish] client1: tcp connect to  failed (No route to host)
[2010-08-31 07:04:02.494779] D [rdma.c:4210:rdma_handshake_pollerr] rpc-transport/rdma: client1: peer disconnected, cleaning up
[2010-08-31 07:04:05.497783] D [name.c:146:client_fill_address_family] client3: address-family not specified, guessing it to be inet/inet6
[2010-08-31 07:04:05.500580] D [name.c:146:client_fill_address_family] client4: address-family not specified, guessing it to be inet/inet6
[2010-08-31 07:04:05.500584] E [rdma.c:4290:tcp_connect_finish] client3: tcp connect to  failed (Connection refused)
[2010-08-31 07:04:05.500620] D [rdma.c:4210:rdma_handshake_pollerr] rpc-transport/rdma: client3: peer disconnected, cleaning up
[2010-08-31 07:04:05.503377] D [name.c:146:client_fill_address_family] client5: address-family not specified, guessing it to be inet/inet6
[2010-08-31 07:04:05.504089] E [rpc-clnt.c:674:rpc_clnt_handle_cbk] rpc-clnt: RPC call decoding failed
[2010-08-31 07:04:05.504121] E [rdma.c:4341:rdma_event_handler] rpc-transport/rdma: client4: pollin received on tcp socket (peer: 10.1.10.35:7719) after handshake is complete
[2010-08-31 07:04:05.504141] D [rdma.c:4210:rdma_handshake_pollerr] rpc-transport/rdma: client4: peer disconnected, cleaning up
[2010-08-31 07:04:05.506170] D [name.c:146:client_fill_address_family] client2: address-family not specified, guessing it to be inet/inet6
[2010-08-31 07:04:05.506895] E [rpc-clnt.c:674:rpc_clnt_handle_cbk] rpc-clnt: RPC call decoding failed
[2010-08-31 07:04:05.506924] E [rdma.c:4341:rdma_event_handler] rpc-transport/rdma: client5: pollin received on tcp socket (peer: 10.1.10.31:7717) after handshake is complete
[2010-08-31 07:04:05.506944] D [rdma.c:4210:rdma_handshake_pollerr] rpc-transport/rdma: client5: peer disconnected, cleaning up
[2010-08-31 07:04:05.508971] D [name.c:146:client_fill_address_family] client1: address-family not specified, guessing it to be inet/inet6
[2010-08-31 07:04:05.509054] E [rdma.c:4290:tcp_connect_finish] client2: tcp connect to  failed (No route to host)
[2010-08-31 07:04:05.509071] D [rdma.c:4210:rdma_handshake_pollerr] rpc-transport/rdma: client2: peer disconnected, cleaning up
[2010-08-31 07:04:05.511848] E [rdma.c:4290:tcp_connect_finish] client1: tcp connect to  failed (No route to host)
[2010-08-31 07:04:05.511864] D [rdma.c:4210:rdma_handshake_pollerr] rpc-transport/rdma: client1: peer disconnected, cleaning up
[2010-08-31 07:04:08.514854] D [name.c:146:client_fill_address_family] client3: address-family not specified, guessing it to be inet/inet6

Comment 1 Vijay Bellur 2010-09-01 09:16:18 UTC
PATCH: http://patches.gluster.com/patch/4452 in master (rpc-transport/rdma: set whether pollin data is for request/reply.)


Note You need to log in before you can comment on or make changes to this bug.