[Bugs] [Bug 1422781] Transport endpoint not connected error seen on client when glusterd is restarted
bugzilla at redhat.com
bugzilla at redhat.com
Thu Feb 16 10:25:03 UTC 2017
https://bugzilla.redhat.com/show_bug.cgi?id=1422781
Atin Mukherjee <amukherj at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jdarcy at redhat.com
Component|glusterd |rpc
Blocks| |1416031 (glusterfs-3.10.0)
--- Comment #1 from Atin Mukherjee <amukherj at redhat.com> ---
This is reproducible locally as well. client log indicates that client process
is shutdown. Something is wrong in the reconnect logic.
[2017-02-16 10:21:29.026311] E [timer.c:44:gf_timer_call_after]
(-->/usr/local/lib/libgfrpc.so.0(rpc_transport_notify+0x23) [0x7fe5ffce4223]
-->/usr/local/lib/libgfrpc.so.0(rpc_clnt_notify+0x2b0) [0x7fe5ffce7ca0]
-->/usr/local/lib/ libglusterfs.so.0(gf_timer_call_after+0x2a9)
[0x7fe5fff293c9] ) 0-timer: !reg
[2017-02-16 10:21:29.026317] W [rpc-clnt.c:893:rpc_clnt_handle_disconnect]
0-test-vol-client-0: Cannot create rpc_clnt_reconnect timer
[2017-02-16 10:21:29.026322] I [MSGID: 114018]
[client.c:2276:client_rpc_notify] 0-test-vol-client-0: disconnected from
test-vol-client-0. Client process will keep trying to connect to glusterd until
brick's port is available [2017-02-16 10:21:29.030938] W
[glusterfsd.c:1329:cleanup_and_exit] (-->/lib64/libpthread.so.0(+0x75ba)
[0x7fe5fed775ba] -->/usr/local/sbin/glusterfs(glusterfs_sigwaiter+0xc5)
[0x408615] -->/usr/local/sbin/ glusterfs(cleanup_and_exit+0x4b)
[0x4084ab] ) 0-: received signum (15), shutting down
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1416031
[Bug 1416031] GlusterFS 3.10 tracker
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list