Red Hat Bugzilla – Bug 529498
/etc/init.d/cman fails in set_networking_params with 3.0.2 and 3.0.3
Last modified: 2009-10-21 10:11:03 EDT
Description of problem:
When running the /etc/init.d/cman startup script, it fails while executing the set_networking_params() function on both of the members of my Fedora 11 based cluster cluster.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot cluster node with /etc/init.d/cman enabled
1. service cman start
"Setting network parameters... [FAILED]"
and cman script stops executing resulting in the cluster member not joining the cluster.
"Setting network parameters... [OK]"
and cman script completing with the node having joined the cluster.
Attaching a log file showing that because the default (existing) /proc/sys/net/core/rmem_max value is _greater_ than the expected value, setting the value to whatever the cluster needs/wants is failing.
Would think the test should be to validate that the rmem_max (and rmem_default) are set to a value greater or equal to what the cluster stack needs, the startup would proceed, if not the values get elevated. This since other applications (3rd party) may require a higher default network read buffer value than what the cluster software stack needs on its own?
Created attachment 365130 [details]
Created attachment 365131 [details]
Log from "bash -x /etc/init.d/cman start" run
Log file showing failed /etc/init.d/cman start.
Created attachment 365133 [details]
Please patch /etc/init.d/cman and test.
The patch should address the issue
Tested the patch. The cman service now starts with set_networking_params enabled as part of the start action.
Fix is now upstream.
git commit 1ece3abed41a6debf4175201c4061108e9034e68
ok also for me,
I had the same problem after updating from version 3.0.2-1.fc11.x86_64 to 3.0.3-1.fc11.x86_64
Without the proposed patch I get:
[root@r]# service cman start
Global setup... [ OK ]
Loading kernel modules... [ OK ]
Mounting configfs... [ OK ]
Setting network parameters... FATAL: Module lock_dlm not found.
Now with the proposed patch all is ok.
update packages for F11 are available in koji and bodhi.
They should be available "soonish" (it's a manual process) in f10 and f11 updates channels.