[Gluster-devel] failing basic/afr/self-heal.t

[Emmanuel Dreyfus]

Emmanuel Dreyfus <manu at netbsd.org> wrote:

> NetBSD fails basic/afr/self-heal.t and I am looking for help on how to
> fix it.
> 
> Basically the test breaks when it checks wether self heal daemon is
> running. 

More debugging: glusterd --debug tells me that:
[2014-07-13 04:48:18.789503] D [run.c:190:runner_log]  0-: Starting the nfs/glustershd services: /autobuild/install/sbin/glusterfs -s localhost --volfile-id gluster/nfs -p /var/lib/glusterd/nfs/run/nfs.pid -l /autobuild/install/var/log/glusterfs/nfs.log -S /var/run/5b491963922197e7f33117ea2b11d9d2.socket

Then later:
[2014-07-13 04:48:18.794378] D [run.c:190:runner_log]  0-: Starting the nfs/glustershd services: /autobuild/install/sbin/glusterfs -s localhost --volfile-id gluster/glustershd -p /var/lib/glusterd/glustershd/run/glustershd.pid -l /autobuild/install/var/log/glusterfs/glustershd.log -S /var/run/9e135700ac782ef46ef398e884f19b36.socket --xlator-option *replicate*.node-uuid=71ea38dd-ab2c-48b6-b099-94e0283fb4af

The socket is not the same. After initialization id gone, glusterd loops on this:
[2014-07-13 04:48:38.183322] D [glusterd-handler.c:4256:__glusterd_nodesvc_rpc_notify] 0-management: got RPC_CLNT_CONNECT
[2014-07-13 04:48:38.183417] D [socket.c:499:__socket_rwv] 0-management: EOF on socket
[2014-07-13 04:48:38.183540] W [socket.c:529:__socket_rwv] 0-management: readv on /var/run/5b491963922197e7f33117ea2b11d9d2.socket failed (No message available)
[2014-07-13 04:48:38.183560] D [socket.c:2246:socket_event_handler] 0-transport: disconnecting now
[2014-07-13 04:48:41.203280] D [socket.c:2852:socket_connect] 0-management: connection attempt on /var/run/5b491963922197e7f33117ea2b11d9d2.socket failed, (Connection refused)

It looks like if there is a mismatch between the socket names as 
expected by glusterd and used by glustershd. How are they chosen?

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu at netbsd.org