Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Version:
sanlock 2.3.1
wdmd service fails to start if it can find a watchdog device, hence sanlock service fails to start too since wdmd is its dependency.
It will be best to load the softdog module in case there is no loaded watchdog driver, as a dependency for wdmd service.
From /var/log/messages:
Jun 13 17:44:06 localhost sanlock[2682]: 2012-06-13 17:44:06+0300 112156 [2682]: wdmd connect failed for watchdog handling
Comment 1Federico Simoncelli
2012-06-18 08:46:30 UTC
A fix has been proposed and committed upstream:
https://fedorahosted.org/pipermail/sanlock-devel/2012-June/000197.html
commit b6dc3c761c75a0411a607544a1b76955dbe9a1a7
Author: Federico Simoncelli <fsimonce>
Date: Thu Jun 14 09:41:12 2012 +0000
wdmd: load the softdog module when needed
Signed-off-by: Federico Simoncelli <fsimonce>
*** Bug 832056 has been marked as a duplicate of this bug. ***
Comment 7Douglas Schilling Landgraf
2012-07-27 19:10:57 UTC
Hi David,
Which version of sanlock this bug has been fixed?
Tested with the following packages and still occurs:
sanlock-lib-2.3-3.fc17.x86_64
sanlock-python-2.3-3.fc17.x86_64
libvirt-lock-sanlock-0.9.11.4-3.fc17.x86_64
sanlock-2.3-3.fc17.x86_64
Thanks!
Comment 8Douglas Schilling Landgraf
2012-07-27 19:16:50 UTC
Sorry, I must say that I am using Fedora 17 (oVirt Node), do we have a bugzilla for fedora ?
Should I open a bz for Fedora?
Thanks
Douglas
Verified on RHEL6.3 with sanlock-2.5-1.el6.x86_64
I rmmod the softdog kernel module after stopping sanlock and wdmd services. The softdog kernel module was loaded automatically while stating the wdmd service.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2013-0530.html