RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1183204 - Not able to start cman cluster
Summary: Not able to start cman cluster
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: cluster
Version: 6.4
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Christine Caulfield
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-17 05:35 UTC by arjun
Modified: 2015-06-29 08:27 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 08:27:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description arjun 2015-01-17 05:35:09 UTC 
Description of problem:Not able to start cman cluster

# /etc/init.d/cman start
Starting cluster:
   Checking if cluster has been disabled at boot...        [  OK  ]
   Checking Network Manager...                             [  OK  ]
   Global setup...                                         [  OK  ]
   Loading kernel modules... FATAL: Could not open 'kernel/fs/configfs/configfs.ko': No such file or directory
                                                           [FAILED]
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  ]

File is present- 
# ls /lib/modules/`uname -r`/kernel/fs/configfs/configfs.ko
/lib/modules/2.6.32-358.el6.x86_64/kernel/fs/configfs/configfs.ko

# getenforce
Permissive

Corosync was getting hang while starting/stopping. I read in one of the redhat site that use cman to manage corosync. So, I started using cman.
Please help.

Version-Release number of selected component (if applicable): cman-3.0.12.1-68.el6.x86_64.rpm

# more /etc/system-release
Red Hat Enterprise Linux Server release 6.4 (Santiago)

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Jan Friesse 2015-01-19 08:18:26 UTC 
kernel/fs/configfs/configfs.ko has nothing to do with corosync/cman. I'm pretty sure it's problem in your configuration (not completed depmod, corrupted module, ...). Dmesg shows anything interesting? Kernel update helps?
Comment 3 Christine Caulfield 2015-01-19 09:08:13 UTC 
DLM (part of the cman package) uses configfs to communicate between userspace and the kernel module. Without that it won't be able to start.

So it sounds to me like a corrupted kernel installation. Try reinstalling the package or upgrading it. It's not specifically a cman problem as Honza says, it's to do with the kernel package installation.

it's worth trying to re-run "depmod -a", also see if "modprobe -v configfs" shines any more light on why it's failing. If you get desperate an strace of the command might also help.

But I would begin with reinstalling or upgrading the kernel package.
Comment 4 Christine Caulfield 2015-06-29 08:27:10 UTC 
As this bug has been inactive for nearly six months I'm going to close it. If there's any more information then feel free to re-open it so we can have a look.
Note You need to log in before you can comment on or make changes to this bug.