Take one newly installed f14 via beaker provisioning, add gfs2-utils, gfs2-cluster and the deps. Turn off NetworkManager, turn on network. Create /etc/cluster/cluster.conf, do /etc/init.d/cman start, and I get this: [root@gfs-a24c-01 ~]# /etc/init.d/cman start Starting cluster: Checking Network Manager... [ OK ] Global setup... [ OK ] Loading kernel modules... [ 107.997256] DLM (built Oct 18 2010 23:59:12) ind [ OK ] Mounting configfs... [ OK ] Starting cman... I/O warning : failed to load external entity "/etc/cluster/" Unable to get the configuration I/O warning : failed to load external entity "/etc/cluster/cluster.conf" corosync [MAIN ] Corosync Cluster Engine ('1.3.0'): started and ready to provi. corosync [MAIN ] Corosync built-in features: nss rdma corosync [MAIN ] Unable to read config from /etc/cluster/cluster.conf corosync [MAIN ] Corosync Cluster Engine exiting with status 8 at main.c:1626. corosync died: Could not read cluster configuration Check cluster logs for detas [FAILED] Turn selinux into permissive mode and it appears to work correctly.
What AVC messages are you seeing? # ausearch -m avc -ts today Also how is "/etc/cluster/cluster.conf" labeled? # ls -Z /etc/cluster/cluster.conf
[root@gfs-a24c-01 ~]# ls -Z /etc/cluster/cluster.conf -rw-r-----. root root unconfined_u:object_r:admin_home_t:s0 /etc/cluster/cluster.conf
Created attachment 472079 [details] ausearch -m avc -ts today >my.avc
Steve you created the file in /root and then moved it to /etc/cluster/cluster.conf This means it maintained the label of admin_home_t which corosync would not be allowed to read. Run restorecon -R -v /etc/cluster Will fix the problem.