Bug 529498 - /etc/init.d/cman fails in set_networking_params with 3.0.2 and 3.0.3
/etc/init.d/cman fails in set_networking_params with 3.0.2 and 3.0.3
Product: Fedora
Classification: Fedora
Component: cluster (Show other bugs)
x86_64 Linux
low Severity high
: ---
: ---
Assigned To: Fabio Massimo Di Nitto
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-10-17 13:40 EDT by Thomas Sjolshagen
Modified: 2009-10-21 10:11 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-10-19 00:48:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
/etc/sysconfig/cman file (181 bytes, text/plain)
2009-10-17 13:41 EDT, Thomas Sjolshagen
no flags Details
Log from "bash -x /etc/init.d/cman start" run (6.69 KB, text/plain)
2009-10-17 13:46 EDT, Thomas Sjolshagen
no flags Details
proposed fix (561 bytes, patch)
2009-10-17 13:57 EDT, Fabio Massimo Di Nitto
no flags Details | Diff

  None (edit)
Description Thomas Sjolshagen 2009-10-17 13:40:09 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):


How reproducible:

Every time

Steps to Reproduce:
1. Boot cluster node with /etc/init.d/cman enabled

1. service cman start

Actual results:

"Setting network parameters...        [FAILED]"

and cman script stops executing resulting in the cluster member not joining the cluster.

Expected results:

"Setting network parameters...        [OK]"

and cman script completing with the node having joined the cluster.

Additional info:

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?
Comment 1 Thomas Sjolshagen 2009-10-17 13:41:23 EDT
Created attachment 365130 [details]
/etc/sysconfig/cman file
Comment 2 Thomas Sjolshagen 2009-10-17 13:46:17 EDT
Created attachment 365131 [details]
Log from "bash -x /etc/init.d/cman start" run

Log file showing failed /etc/init.d/cman start.
Comment 3 Fabio Massimo Di Nitto 2009-10-17 13:57:05 EDT
Created attachment 365133 [details]
proposed fix

Please patch /etc/init.d/cman and test.

The patch should address the issue

Comment 4 Thomas Sjolshagen 2009-10-18 12:49:17 EDT
Tested the patch. The cman service now starts with set_networking_params enabled as part of the start action.
Comment 5 Fabio Massimo Di Nitto 2009-10-19 00:48:31 EDT
Fix is now upstream.

git commit 1ece3abed41a6debf4175201c4061108e9034e68

Comment 6 Gianluca Cecchi 2009-10-21 09:58:10 EDT
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
Starting cluster:
   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.
Comment 7 Fabio Massimo Di Nitto 2009-10-21 10:11:03 EDT
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.


Note You need to log in before you can comment on or make changes to this bug.