Skip to main content
NetApp Knowledge Base

Unified Manager upgrade fails due to MySQL service unable to start

  1. Last updated
  2. Save as PDF
Views:
1,176
Visibility:
Public
Votes:
0
Category:
oncommand-unified-manager
Specialty:
nas
Last Updated:

Applies to

  • Unified Manager 7.2+
  • RHEL/CentOS 6 or 7

Issue

Attempt to upgrade from Unified Manager fails, and the MySQL error log reports the following error:
 

/var/log/mysql/error.log 

2019-05-03T10:16:37.578843Z 0 [ERROR] InnoDB: Operating system error number 116 in a file operation.
2019-05-03T10:16:37.578870Z 0 [ERROR] InnoDB: Error number 116 means 'Stale file handle'
2019-05-03T10:16:37.578876Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/...ror-codes.html
2019-05-03T10:16:37.578881Z 0 [ERROR] InnoDB: File .//ocum-backup: 'stat' returned OS error 216.
2019-05-03T10:16:37.578885Z 0 [ERROR] InnoDB: os_file_readdir_next_file() returned -1 in directory ./, crash recovery may have failed for some .ibd files!
2019-05-03T10:16:37.578920Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error


The file reported might be different depending on the environment.

The following errors are reported on the install.log:
 

May 03 10:57:00 server01.netapp.com systemd[1]: Failed to start MySQL Server.
May 03 10:57:00 server01.netapp.com systemd[1]: Unit mysqld.service entered failed state.
May 03 10:57:00 server01.netapp.com systemd[1]: mysqld.service failed.
May 03 10:57:00 server01.netapp.com systemd[1]: mysqld.service holdoff time over, scheduling restart.
May 03 10:57:00 server01.netapp.com systemd[1]: start request repeated too quickly for mysqld.service
May 03 10:57:00 server01.netapp.com systemd[1]: Failed to start MySQL Server.
May 03 10:57:00 server01.netapp.com systemd[1]: Unit mysqld.service entered failed state.
May 03 10:57:00 server01.netapp.com systemd[1]: mysqld.service failed.
Changing mysql configuration to small
May 03 11:07:17:  INFO: Starting MySQL database...
Job for mysqld.service failed because the control process exited with error code. See "systemctl status mysqld.service" and "journalctl -xe" for details.
May 03 11:07:28:  Granting privileges to jboss user for Unified Manager related databases...
mysql_upgrade: Got error: 2002: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) while connecting to the MySQL server
Upgrade process encountered error and will not continue.
May 03 11:07:28:  Failed while granting privileges to jboss user for Unified Manager related databases
May 03 11:07:28:  preun_upgrade_ocum called

 

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.