[Bugs] [Bug 1372356] glusterd experiencing repeated connect/ disconnect messages when shd is down

bugzilla at redhat.com bugzilla at redhat.com
Tue Sep 6 05:40:15 UTC 2016


--- Comment #2 from Raghavendra G <rgowdapp at redhat.com> ---
(In reply to Raghavendra G from comment #1)
> Analysis from Atin:
> <analysis>
> I am seeing glusterd is receiving RPC_CLNT_CONNECT in
> glusterd_svc_common_rpc_notify () even though shd service is not up (note -
> this is applicable for all daemon services including brick process). In
> further debugging what I found is socket_connect_finish () calls
> __socket_connect_finish () which returns 0 which means its able to connect
> to the socket and hence RPC_CLNT_CONNECT event is sent to the transport. Is
> this right? My understanding is __socket_connect_finish () shouldn't be
> returning 0 here.

Yes. __socket_connect_finish (or getsockopt (socket, SOL_SOCKET, SO_ERROR) 
specifically) should've returned ECONNREFUSED as shd is down. I am not sure why
this is not the case. Wondering whether there is an issue in TCP/IP (socket)
layer or the way we are using getsockopt.

> </analysis>

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