How to track process which is opening /dev/watchdog and closing incorrectly causing “watchdog did not stop!“ message followed by system crash?

Solution Verified - Updated -

Issue

  • How to track process which is opening /dev/watchdog and closing incorrectly causing “watchdog did not stop!“ message followed by system crash?
kernel: watchdog: watchdog0: watchdog did not stop!
kernel: watchdog: watchdog0: watchdog did not stop!
  • Why does executing grep -R "No valid host was found" / causes system to reset with following message
"The watchdog timer reset the system" (iDRAC) 

UEFI0082: The system was reset due to a timeout from the watchdog timer. 
Check the System Event Log (SEL) or crash dumps from Operating Sysstem to 
identify the source that triggered the watchdog timer reset. Update the
firmware or driver for the identified device.

watchdog_timer_idrac

Environment

  • RHEL
  • Dell Servers

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content