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.
DescriptionRichard W.M. Jones
2012-07-06 10:19:23 UTC
+++ This bug was initially created as a clone of Bug #837949 +++
Description of problem:
watchdog 5.9 (2010) in FC17 is very old, and has a number of crticial bugs such as the inability to reliably ping a target. it should be updated to 5.12 (2012).
Version-Release number of selected component (if applicable):
watchdog-5.9-3.fc17.x86_64
How reproducible:
always
Steps to Reproduce:
1.put a ping <ipaddress> option in watchdog.conf
2.start up watchdog
3.
Actual results:
Jul 5 04:29:55 ns1 watchdog[1044]: starting daemon (5.9):
Jul 5 04:29:55 ns1 watchdog[1044]: int=1s realtime=yes sync=no soft=no mla=0 mem=0
Jul 5 04:29:55 ns1 watchdog[1044]: ping: 192.168.0.1
Jul 5 04:29:55 ns1 watchdog[1044]: file: no file to check
Jul 5 04:29:55 ns1 watchdog[1044]: pidfile: no server process to check
Jul 5 04:29:55 ns1 watchdog[1044]: interface: no interface to check
Jul 5 04:29:55 ns1 watchdog[1044]: test=none(0) repair=none(0) alive=none heartbeat=none temp=none to=root no_act=yes
Jul 5 04:29:56 ns1 watchdog[1044]: no response from ping (target: 192.168.0.1)
Jul 5 04:29:56 ns1 watchdog[1020]: still alive after 8 interval(s)
Jul 5 04:29:56 ns1 watchdog[1020]: no response from ping (target: 192.168.0.1)
[...]
Jul 5 04:30:21 ns1 watchdog[315]: shutting down the system because of error 101
Expected results:
Jul 5 04:32:16 ns1 watchdog[2697]: starting daemon (5.12):
Jul 5 04:32:16 ns1 watchdog[2697]: int=1s realtime=yes sync=no soft=no mla=0 mem=0
Jul 5 04:32:16 ns1 watchdog[2697]: ping: 192.168.0.1
Jul 5 04:32:16 ns1 watchdog[2697]: file: no file to check
Jul 5 04:32:16 ns1 watchdog[2697]: pidfile: no server process to check
Jul 5 04:32:16 ns1 watchdog[2697]: interface: no interface to check
Jul 5 04:32:16 ns1 watchdog[2697]: test=none(0) repair=none(0) alive=none heartbeat=none temp=none to=root no_act=yes
Jul 5 04:32:16 ns1 watchdog[2697]: ping select timeout = 1 seconds and 0 useconds
Jul 5 04:32:16 ns1 watchdog[2697]: got answer from target 192.168.0.1
Jul 5 04:32:16 ns1 watchdog[2697]: still alive after 1 interval(s)
Additional info:
--- Additional comment from rjones on 2012-07-05 18:04:06 EDT ---
Agreed. Since it's rather late now I'll try to push
an updated package tomorrow.
Comment 2Richard W.M. Jones
2013-07-29 12:14:30 UTC
RHEL 7 contains watchdog 5.13 which is the latest upstream version
and in synch with Fedora 20.
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.