On 07/18/2013 04:41 AM, Bobby Jacob wrote:>
> GlusterFSD service is running on all the bricks. But self heal is not
> happening. I restart glusterd service, still nothing.
>
glusterfsd is the brick process. It does not do self-healing. Self
healing is provided by a glusterfs process with "--volfile-id
gluster/glustershd" and is started by glusterd. You can check to see if
it's running with "gluster volume status".>
> When I do "service glusterfsd restart". The services stops but
doesn't
> start. Once I restart the server, the self heal resumes. PLEASE
> ADVICE> !!!!
>
All that command is going to do is stop your bricks. The restart command
does a stop and start of glusterfsd. Since stop kills all the glusterfsd
processes, your bricks will then be killed. It does not start the
bricks, but rather tries to start a glusterfsd process with a default
volfile setting. This would work if you had some legacy configuration
that you still wanted to use, but does not work for restarting the
self-heal process.
The command you're looking for would be "service glusterd restart"
if
the self-heal process needed restarted.>
> GLusterfs 3.3.1
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130720/b6a84f8e/attachment.html>