Re: cluster not fencing after filesystem failure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

You can check in the log for "fenced" messages, if it tries to fence the node at all. Also for "cman".
Is your cluster hanged after a node failure? That would indicate the fencing didn't succeed for some reason.

   >I've tested fencing from the command line and it works:
   >fence_vmware_soap --ip 192.168.50.9 --username ddsfence --password
   >secret -z --action reboot -U  "423d288c-03ff-74bf-9a4f-bf661f8ed87b"


You can also test fencing with "fence_node <node-to-be-fenced>" - that way it is tested with the exact arguments from the cluster.conf and you can see if it works or not.

BR,
Vasil

-- 
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux