OpenAIS/Corosync daemon fails to start
This document (7010879) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Linux Enterprise High Availability Extension 11 (HAE)
SUSE Linux Enterprise Server 11 (SLES)
SUSE Linux Enterprise Server 11 (SLES)
Situation
Shutting down an HAE node results in the error:
"Stopping OpenAIS/corosync daemon (corosync): ...... Stopping SBD - Message is not delivered vai more then a half of devices"
At other times, the daemon never shuts down completely and requires the node to be powered off. The error is:
"Stopping OpenAIS/corosync daemon (corosync): ..........." with the dots continuing indefinitely.
When the HAE cluster node is restarted, there are two errors:
"Failed services in runlevel 3: openais" and
"Starting OpenAIS/Corosync daemon (corosync): Starting SBD - SBD failed to start; aborting."
The SBD partition header does not dump correctly, but displays the sbd command help screen like this:
# /usr/sbin/sbd -d /dev/disk/by-id/scsi-149455400000000000000-part1 dump
Shared storage fencing tool.
Syntax:
sbd <options> <command> <cmdarguments>
Options:
-d <devname> Block device to use (mandatory; can be specified up to 3 times)
<snip>
"Stopping OpenAIS/corosync daemon (corosync): ...... Stopping SBD - Message is not delivered vai more then a half of devices"
At other times, the daemon never shuts down completely and requires the node to be powered off. The error is:
"Stopping OpenAIS/corosync daemon (corosync): ..........." with the dots continuing indefinitely.
When the HAE cluster node is restarted, there are two errors:
"Failed services in runlevel 3: openais" and
"Starting OpenAIS/Corosync daemon (corosync): Starting SBD - SBD failed to start; aborting."
The SBD partition header does not dump correctly, but displays the sbd command help screen like this:
# /usr/sbin/sbd -d /dev/disk/by-id/scsi-149455400000000000000-part1 dump
Shared storage fencing tool.
Syntax:
sbd <options> <command> <cmdarguments>
Options:
-d <devname> Block device to use (mandatory; can be specified up to 3 times)
<snip>
Resolution
Do the following to recreate the SBD partition.
1. Source /etc/sysconfig/sbd into your environment
. /etc/sysconfig/sbd
2. Recreate the SBD partition
sbd -d $SBD_DEVICE create
3. Reboot all nodes in the cluster that use the SBD partition
reboot
1. Source /etc/sysconfig/sbd into your environment
. /etc/sysconfig/sbd
2. Recreate the SBD partition
sbd -d $SBD_DEVICE create
3. Reboot all nodes in the cluster that use the SBD partition
reboot
Cause
The SDB partition became damaged. In this case the customer accidentally formatted the SBD partition with a filesystem.
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7010879
- Creation Date: 05-Oct-2012
- Modified Date:04-Oct-2022
-
- SUSE Linux Enterprise High Availability Extension
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com
