Skip to main content
NetApp Knowledge Base

StorageGRID reports Unable to communicaite with node with Unresponsive mgmtapi service

  1. Last updated
  2. Save as PDF
Views:
511
Visibility:
Public
Votes:
0
Category:
storagegrid
Specialty:
sgrid
Last Updated:

Applies to

  • NetApp StorageGRID  11.9
  • Admin and/or Gateway node(s)

Issue

  • StorageGRID Admin or Gateway node is reporting Unable to communicate with node with Unresponsive mgmtapi service in Grid Manager.
  • storagegrid-status on affected node reports MySQL in ERROR state with the following service statuses and all other services running:
    • Database Engine     package MySQL        Error      
      mi                  11.9.0.8             Starting...
      mgmt api            11.9.0.8             Starting...
      attrDownPurge       11.9.0.8             Stopped    
      attrDownSamp1       11.9.0.8             Stopped    
  • The mysql and mgmt-api services fail to start via /var/local/log/servermanager.log :

 11:00:11 +0000 | mysql | starting mysql
 11:00:13 +0000 | mysql | mysql ended
 11:00:13 +0000 | mysql | force-restarting mgmt-api
 11:00:13 +0000 | mgmt-api | mgmt-api ended
 11:00:25 +0000 | mgmt-api | waiting for mysql, waiting 2s to try again
 11:00:35 +0000 | mgmt-api | waiting for mysql, waiting 4s to try again
 11:00:44 +0000 | mgmt-api | mgmt-api ended
 11:00:44 +0000 | mysql | force-restarting mi
 11:00:44 +0000 | mi | mi ended
 11:00:55 +0000 | mgmt-api | waiting for mysql, waiting 2s to try again

  • The/msql/mysql.err log records: 

[ERROR] InnoDB: Corrupted page identifier at 448993352621; set innodb_force_recovery=1 to ignore the record.
[Note] InnoDB: End of log at LSN=448993352621
[ERROR] InnoDB: Plugin initialization aborted with error Generic error
[Note] InnoDB: Starting shutdown...
[ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

  • Other errors in /msql/mysql.err log may be present:

2025-06-12 17:12:34 0 [ERROR] InnoDB: Tablespace 16198 was not found at ./mi/tempwritetree.ibd.
2025-06-12 17:12:34 0 [Note] InnoDB: Set innodb_force_recovery=1 to ignore this and to permanently lose all changes to the tablespace.
2025-06-12 17:12:34 0 [ERROR] InnoDB: Plugin initialization aborted with error Tablespace not found

2025-06-02 22:32:10 24 [ERROR] InnoDB: Trying to read 16384 bytes at 70368744161280 outside the bounds of the file: /var/local/mysql_ibdata/mysql_data/ib1
2025-06-02 22:32:10 24 [ERROR] InnoDB: File '/var/local/mysql_ibdata/mysql_data/ib1' is corrupted
2025-06-02 22:32:10 0x7fe0681756c0 InnoDB: Assertion failure in file ./storage/innobase/trx/trx0purge.cc line 262
InnoDB: Failing assertion: undo_page
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mariadbd startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.
250602 22:32:10 [ERROR] mysqld got signal 6 ;

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.