wdmd should load softdog if hardware watchdog is not available

Bug #1229525 reported by Zhou Zheng Sheng on 2013-09-24
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sanlock (Ubuntu)

Bug Description

Ubuntu release: Ubuntu 13.04 server edition and older releases
sanlock version: 2.2-2

When there is no hardware watchdog available, I expect softdog kernel module is loaded automatically to make wdmd and sanlock work properly. The actual result is it does not load softdog and wdmd fails to start.

Steps to reproduce the bug:
0. Install Ubuntu 13.04 server edition on a host that does not have a watchdog device
1. aptitude update; aptitude install sanlock
2. vi /etc/default/wdmd
  change "enabled" to "1"
3. service wdmd start
  service wdmd status

Expected result
wdmd started

Actual result
wdmd is not started
/var/log/syslog shows the following
Sep 24 11:55:22 uvdsm1 wdmd[2446]: wdmd started tests_built client
Sep 24 11:55:22 uvdsm1 wdmd[2446]: no /dev/watchdog, load a watchdog driver

I think wdmd SysV init script should detect if /dev/watchdog exists, if there is no /dev/watchdog, it may call "modprobe softdog". This modprobe invocation is needed only on Debian and Ubuntu, because on Red Hat family distributions, if there is no hardware watch dog, they load softdog automatically regardless wdmd and sanlock is installed or not.

Zhou Zheng Sheng (zhshzhou) wrote :
Changed in sanlock (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments