We have several Dell PowerEdge T620 servers in remote locations throughout our Enterprise. Each of them is randomly throwing the following event and thus far I've found no information about the message or how to resolve it. I'm hoping someone here can help me figure this out.
Event Message: The watchdog time expired.
Severity: Critical
Detailed Description: The operating system or potentially an application failed to communicate to the baseboard management controller (BMC) within the timeout period.
Recommended Action: Check the operating system, application, hardware, and system event log for exception events.
Message ID: ASR0000
System Model: PowerEdge T620
Power State: ON
Operating System: Microsoft Windows Server 2012, Standard x64 Edition
While I've been working in the desktop support world for a very long time, I'm fairly new to Dell servers. I'm trying to help another highly over-worked, over-stressed, administrator with this issue. Is someone can spare the time to help me learn where to look to gain more insight on what might be going on, I'd really appreciate it. I'm willing and able to learn so I can help take some work off a co-worker's plate. Thanks.
I apologize for the delay in responding. After reviewing the errors and doing some research, the error is coming from Dell's OpenManage software v7.2 . Our recommendation is to update your OpenManage to version 7.3 and monitor. This version should address the timeout error in this particular service is giving the watchdog error.
The watchdog timer is used to monitor the status of a component. It operates by monitoring responses. When it stops getting a heartbeat from a component that it is monitoring then the timer expires, and you receive an error in the log. When the timer expires it will initiate whatever action is set. If the operating system stops responding then the timer will expire and restart the server if it is set to perform that action.
The above error doesn't tell us why the timer expired, so you will need to review your hardware and operating system logs to find out what happened when the timer expired.
These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dsm_sa_datamgr64_6033d1f5754645d6f47ce76327e3cf9364ed73_cab_094e147b
These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dsm_sa_datamgr64_6033d1f5754645d6f47ce76327e3cf9364ed73_cab_094e147b
Does that help at all? If not, where specifically should I be looking for logs? I've checked the iDRAC7 and it had less data then the original message. The above mentioned three events were located in the Windows Event Viewer.
I was at one of our facilities yesterday so I went ahead and ran the latest SUU upon the server and got it caught up on all firmware and driver updates. That did include the OpenManage Server Administrator upgrade to 7.3.0. We'll monitor the server over the next few days and I'll report back with my findings.
So far I've not seen this message return on the 1 server upgraded. I will be upgrading a second of seven servers tomorrow. I'll update you afterward. Thank you for your patience while we work to get fully updated. It should go faster after tomorrow's work.
Actually, I have the same error, but mine is brand new server loaded with OM7.3.
Any though?
-------------------------------
System Host Name: JCMS8BDC01
Event Message: The watchdog timer expired.
Date/Time: Mon Oct 14 2013 16:37:08
Severity: Critical
Detailed Description: The operating system or potentially an application failed to communicate to the baseboard management controller (BMC) within the timeout period.
Recommended Action: Check the operating system, application, hardware, and system event log for exception events.
Message ID: ASR0000
------------------------ Windows log reads ------------------------
I've had the same error on 4 Windows 2008 R2 PE blades with OM 7.3 after installing this month's Microsoft patches which included numerous .NET. After the reboot the DSM SA Data Manager service does not start. Manually starting the service works. A second reboot the service starts on its own.
DELL-Geoff P
990 Posts
97696
0
Posted August 28th, 2013 14:00
I apologize for the delay in responding. After reviewing the errors and doing some research, the error is coming from Dell's OpenManage software v7.2 . Our recommendation is to update your OpenManage to version 7.3 and monitor. This version should address the timeout error in this particular service is giving the watchdog error.
Regards,