On 20 April 2016 at 16:15, Bishoy Mikhael <b.s.mikhael@xxxxxxxxx> wrote:
> try restarting glusterd.
> # service glistered restart
>
> if it didn’t work, try killing glusterfsd PID(s)
> # kill $(ps -ef | grep glusterfsd | awk '{print $2}’)
> t
> hen, restart glusterd
> # service glusterd restart
Already tried all those, its a zombie linux process with parent pid 1,
so can't be killed short of a reboot.
It seems to have released the socket handle now (49156) but the brick
still isn't connecting to the others. Going to have to reboot.
--
Lindsay
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
