Red Hat Bugzilla – Bug 832935
sanlock: softdog module should be loaded in case no watchdog driver was loaded
Last modified: 2016-04-26 09:57:20 EDT
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.
Jun 13 17:44:06 localhost sanlock: 2012-06-13 17:44:06+0300 112156 : wdmd connect failed for watchdog handling
A fix has been proposed and committed upstream:
Author: Federico Simoncelli <email@example.com>
Date: Thu Jun 14 09:41:12 2012 +0000
wdmd: load the softdog module when needed
Signed-off-by: Federico Simoncelli <firstname.lastname@example.org>
*** This bug has been marked as a duplicate of bug 838654 ***
*** Bug 832056 has been marked as a duplicate of this bug. ***
Which version of sanlock this bug has been fixed?
Tested with the following packages and still occurs:
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?
f17 is sanlock-2.4-2.fc17
rhel6 is sanlock-2.3-3.el6_3
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.
sanlock-2.6-2.el6.x86_64 same behavior as 2.5-1.
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.