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

[Emmanuel Dreyfus]

Emmanuel Dreyfus m...@netbsd.org wrote:

 That seems to suggest gluster volume status is broken, and it does not
 report the self heal daemon while it is working. Any hint on how to
 track that problem down?

A hint that the problem may be in glusterd: if I restart glusterd it reports
the self heal deamon again:

Status of volume: patchy
Gluster process PortOnline  Pid
--
Brick netbsd0.cloud.gluster.org:/d/backends/brick0  49152   Y   16509
Brick netbsd0.cloud.gluster.org:/d/backends/brick1  49153   Y   19129
NFS Server on localhost N/A N   N/A
Self-heal Daemon on localhost   N/A Y   19234

Just restarting the volume (gluster volume stop,  start), or restartign and
resetting (gluster volume stop, reset, start) does not recover self heal deamon
presence detection.

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
m...@netbsd.org
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

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

[Emmanuel Dreyfus]

Hi

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. And executing the commands one by one from the shell, I can see
that:
1) gluster volume status always reports it as non running
2) logs are flowing in glustershd.log, and there is a glusterfs
--volfile-id gluster/glustershd running.

That seems to suggest gluster volume status is broken, and it does not
report the self heal daemon while it is working. Any hint on how to
track that problem down?

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
m...@netbsd.org
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel