Skip to main content
NetApp Knowledge Base

Node panics due to mhost application becoming unresponsive

  1. Last updated
  2. Save as PDF
Views:
269
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • FAS/AFF systems
  • ONTAP 9.8 and higher

Issue

  • A node experiences a panic related to vifmgr, vldb, mgwd, bcomd, cpu, etc being unresponsive.
Example:
 
Panic String: Process vifmgr unresponsive for 210 seconds in process nodewatchdog on release 9.8P3 (C)
Panic string: Process vldb unresponsive for 209 seconds in process nodewatchdog on release 9.8P1 (C)
Panic string: Process bcomd unresponsive for 210 seconds in process nodewatchdog on release 9.9.1P6 (C)
PANIC: thread (swi4: clock (0)) on cpu 0 hung for 4001 milliseconds in process swi4: clock (0) on release 9.9.1P3 (C)
  • The panic dumps a core file on the affected node.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.