On 07/31/2013 11:42 AM, Joel Young wrote:
On Wed, Jul 31, 2013 at 10:29 AM, Joe Julian <[email protected]> wrote:
To kill a zombie process, you have to kill the parent process.

ps -p 23744 -o ppid=

If the result is 1, then you are stuck rebooting. Otherwise, kill that
process.
Thanks Joe.  Unfortunately the parent pid is indeed 1 and I'm not
likely to want to kill systemd.

Can gluster be told to stop trying to use that old port and named pipe/socket?

In any case, it looks like I'll have to schedule some down time for
the cluster and reboot that node.

The only way to change that would be to change the md5 sum of ... I think it's the brick path... If you move your brick to a different directory then replace-brick...commit force you should produce a new hash and therefore a different named pipe (theoretically).
_______________________________________________
Gluster-users mailing list
[email protected]
http://supercolony.gluster.org/mailman/listinfo/gluster-users

Reply via email to