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.

Description of problem:
/etc/wdmd directory is not a part of sanlock package.

Version-Release number of selected component (if applicable):
sanlock-lib-1.6-1.el6
sanlock-1.6-1.el6

How reproducible:
always

Steps to Reproduce:
# ls -d /etc/wdmd
ls: cannot access /etc/wdmd: No such file or directory
# wdmd -D
1311770991 wdmd started tests_built scripts client

# echo $?
255
#
  
Actual results:
wdmd dies quietly without an error message

Expected results:
wdmd runs as expected

# mkdir /etc/wdmd
# ls -d /etc/wdmd
/etc/wdmd
# wdmd -D
1311771237 wdmd started tests_built scripts client

1311771237 /dev/watchdog armed with fire_timeout 60
1311771237 keepalive 0
1311771247 test_time 1311771247
1311771247 keepalive 0
1311771247 sleep_seconds 10

<still running>

Hi, thanks for testing that.  I was meaning to disable the test script code in the build until we were ready to use it for something.  Do you have a use for test scripts in wdmd?  If not I'll compile it out in the next build.

No, I have no use for test scripts.

# rpm -qa sanlock\*
sanlock-lib-1.6-1.el6.i686
sanlock-1.6-1.el6.i686
# wdmd -D
1312377989 wdmd started tests_built scripts client

1312377989 no /dev/watchdog, load a watchdog driver
# echo $?
255
# 

Where can I get such a watchdog driver ?

Can I use "modprobe softdog" for testing purposes ?

yes, you can use softdog if you don't have a hardware watchdog

*** This bug has been marked as a duplicate of bug 658971 ***