Skip to main content
NetApp Knowledge Base

MySQL fails to start when Active IQ Unified Manager is reverted from a newer version to an older version

Views:
1,160
Visibility:
Public
Votes:
0
Category:
active-iq-unified-manager
Specialty:
om
Last Updated:

Applies to

  • Active IQ Unified Manager 9.x ( AIQUM )
  • OnCommand Unified Manager 9.x ( OCUM )
  • Red Hat Enterprise Linux
  • CentOS

 

Issue

When reverting from Unified Manager (UM) to earlier versions of Unified Manager, MySQL fails to start. This MySQL start failure will also cause the new install of the previous versions of UM to fail.

  • The error from running systemctl status mysqld is:

mysqld.service - MySQL Server
Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Tue 2020-05-05 16:38:36 -07; 7min ago
Docs: man:mysqld(8)
http://dev.mysql.com/doc/refman/en/using-systemd.html

May 05 16:38:36 <server_name> systemd[1]: Failed to start MySQL Server.
May 05 16:38:36 <server_name> systemd[1]: Unit mysqld.service entered failed state.
May 05 16:38:36 <server_name> systemd[1]: mysqld.service failed.
May 05 16:38:36 <server_name> systemd[1]: mysqld.service holdoff time over, scheduling restart.
May 05 16:38:36 <server_name> systemd[1]: start request repeated too quickly for mysqld.service
May 05 16:38:36 <server_name> systemd[1]: Failed to start MySQL Server.
May 05 16:38:36 <server_name> systemd[1]: Unit mysqld.service entered failed state.
May 05 16:38:36 <server_name> systemd[1]: mysqld.service failed.

  • When checking /var/log/mysqld.log the following is seen:

2020-05-05T00:21:13.687193Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4000!
2020-05-04  17:21:13 0x7f758b34e780  InnoDB: Assertion failure in thread 140142823401344 in file ut0ut.cc line 918

 

"Cannot boot server version 80021 on data directory built by version 80023. Downgrade is not supported"

 

The error seen on the CLI during the UM install is:

Job for mysqld.service failed because the control process exited with error code. See "systemctl status mysqld.service" and "journalctl -xe" for details.

ERROR: MySQL pid missing after 600s, unable to continue.

Warning: %post(netapp-platform-base-9.5.0-2019.04.J68.x86_64) scriptlet failed, exit status 1
Non-fatal POSTIN scriptlet failure in rpm package netapp-platform-base-9.5.0-2019.04.J68.x86_64

FAILURE: netapp-platform-base package is installed, but in in a corrupt state. Install netapp-platform-base package and try again.

 

 

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.