Skip to main content
NetApp Knowledge Base

ONTAP Upgrade stuck due to Panic: Shutdown taking longer than 930 seconds in process nodewatchdog

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

Applies to

  • ONTAP 9
  • Service Processor (SP)

Issue

  • Node panic and cannot boot up during ONTAP upgrading.
  • EMS reports Panic String.

[Node-A: nodewatchdog: nodewatchdog.node.longreboot:alert]: Data ONTAP has experienced a serious internal error. The node experiencing this problem is unable to reboot within it's allotted time of 930 seconds causing it to be unavailable. The node has been panicked to enable it to recover.
[Node-A: nodewatchdog: sk.panic:alert]: Panic String: Shutdown taking longer than 930 seconds in process nodewatchdog on release 9.5P12 (C)
[Node-A: nodewatchdog: coredump.shutdown.trace:notice]: coredump shutdown times: kmod dumper start 208, panic_info set 52, sf_dumpcore sent 0, sparecore id sent 0, fmot_outage info sent 0, disk_dump_start done 5113, coredump begin 29 (all in msec).

 

 

 

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.