Skip to main content
NetApp Knowledge Base

Cannot perform giveback after panic occurs

Views:
55
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

ONTAP

Issue

  • SP log messages shows mdb.recovery.unsuccessful :
Jul 24 13:28:01 [XXXXX:callhome.mdb.recovery.unsuccessful:EMERGENCY]: Call home for MDB RECOVERY UNSUCCESSFUL FOR THE vifmgr WARNING.
Jul 24 13:28:01 [XXXXX:spm.vifmgr.process.exit:EMERGENCY]: Logical Interface Manager(VifMgr) with ID 19996 aborted as a result of signal signal 6. The subsystem will attempt to restart.
Jul 24 13:28:02 [XXXXX:callhome.mdb.recovery.unsuccessful:EMERGENCY]: Call home for MDB RECOVERY UNSUCCESSFUL FOR THE vldb WARNING.
Jul 24 13:28:02 [XXXXX:spm.vldb.process.exit:EMERGENCY]: Volume Location Database(VLDB) subsystem with ID 20055 exited as a result of signal signal 6. The subsystem will attempt to restart.
Jul 24 13:28:03 [XXXXX:spm.vifmgr.process.exit:EMERGENCY]: Logical Interface Manager(VifMgr) with ID 20060 aborted as a result of signal signal 6. The subsystem will attempt to restart.
Jul 24 13:28:03 [XXXXX:spm.vldb.process.exit:EMERGENCY]: Volume Location Database(VLDB) subsystem with ID 20065 exited as a result of signal signal 6. The subsystem will attempt to restart.
Jul 24 13:28:05 [XXXXX:spm.vldb.process.exit:EMERGENCY]: Volume Location Database(VLDB) subsystem with ID 20079 exited as a result of signal signal 6. The subsystem will attempt to restart.
Jul 24 13:28:05 [XXXXX:spm.vifmgr.process.exit:EMERGENCY]: Logical Interface Manager(VifMgr) with ID 20074 aborted as a result of signal signal 6. The subsystem will attempt to restart.
Jul 24 13:28:20 [XXXXX:spm.mgwd.process.exit:EMERGENCY]: Management Gateway (mgwd) subsystem with ID 1746 exited as a result of signal normal exit (0). The subsystem will attempt to restart.
Jul 24 13:29:48 [XXXXX:rdb.recovery.failed:EMERGENCY]: Error: Unable to find a master. Unable to recover the local database of Data Replication Module: VLDB.
Jul 24 13:29:49 [XXXXX:rdb.recovery.failed:EMERGENCY]: Error: Unable to find a master. Unable to recover the local database of Data Replication Module: VifMgr.
Jul 24 13:29:55 [XXXXX:spm.mgwd.process.exit:EMERGENCY]: Management Gateway (mgwd) subsystem with ID 20122 exited as a result of signal normal exit (255). The subsystem will attempt to restart.
PANIC  : Process vldb unresponsive for 184 seconds version: 9.7P5: Tue Jun 23 00:04:35 EDT 2020
  • Forced giveback failed with the following error :
::> storage failover giveback -ofnode XXXXX -override-vetoes true
Info: Node XXXXX that hosts aggregate XXXXX is offline

Warning: Initiating a giveback with vetoes overridden will result in giveback
         proceeding even if the node detects outstanding issues that would make
         a giveback dangerous or disruptive. Do you want to continue?
          {y|n}: y
Error: command failed: Failed to initiate giveback. Reason: A giveback is
       already in progress.
  • Cannot check the status of the components on the node where the panic occurred:
::> set advanced -confirmations off;cluster ring show;set admin

Node      UnitName Epoch    DB Epoch DB Trnxs Master    Online
--------- -------- -------- -------- -------- --------- ---------
XXXX    mgmt     -        -        -        -         -

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.