|
Hi there, I had to figure out that there seems to be an incompatibility of chkconfig and the cman-Initscript under Debian 6(.0.2). I recognized it after having installed chkconfig. With chkconfig installed I get this... # service cman restart Stopping cluster: Leaving fence domain... [ OK ] Stopping gfs_controld... [ OK ] Stopping dlm_controld... [ OK ] Stopping fenced... [ OK ] Stopping cman... [ OK ] Unloading kernel modules... [ OK ] Unmounting configfs... [ OK ] Starting cluster: Checking Network Manager... NetworkManager: unknown service Network Manager is configured to run. Please disable it in the cluster. [FAILED] I checked the Initscipt for the error message: # less /etc/init.d/cman [...] network_manager_enabled() { if type chkconfig >/dev/null 2>&1 && chkconfig NetworkManager; then errmsg="\nNetwork Manager is configured to run. Please disable it in the cluster." return 1 fi if status NetworkManager > /dev/null 2>&1 || \ status network-manager > /dev/null; then errmsg="\nNetwork Manager is running. Please disable it in the cluster." return 1 fi return 0 } [...] Without chkconfig it works fine: # service cman restart Stopping cluster: Leaving fence domain... [ OK ] Stopping gfs_controld... [ OK ] Stopping dlm_controld... [ OK ] Stopping fenced... [ OK ] Stopping cman... [ OK ] Unloading kernel modules... [ OK ] Unmounting configfs... [ OK ] Starting cluster: Checking Network Manager... [ OK ] Global setup... [ OK ] Loading kernel modules... [ OK ] Mounting configfs... [ OK ] Starting cman... [ OK ] Waiting for quorum... [ OK ] Starting fenced... [ OK ] Starting dlm_controld... [ OK ] Starting gfs_controld... [ OK ] Unfencing self... [ OK ] Joining fence domain... [ OK ] A possible workaround could be to temporarily rename the "chkconfig" command. I simply uninstalled it. CU, Mészi. |
-- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
