Post OL6 to OL7 Migration on the BDA /var/log/messages on OL7 Hosts without MySQL Master/Replica Roles are Flooded with Message Indicating MySQL Can Not Start
(Doc ID 2740141.1)
Last updated on APRIL 17, 2023
Applies to:
Big Data Appliance Integrated Software - Version 4.13.0 and laterLinux x86-64
Symptoms
NOTE: In the examples that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner.
Post OL6 to OL7 migration on the BDA /var/log/messages on the OL7 hosts which are neither the MySQL Master nor the MySQL Replica are flooded with messages like below indicating that MySQL can not start. These messages can be seen in /var/log/messages on the affected host or from a sosreport generated on the affected host.
systemd: Starting MySQL Server...
mysqld_pre_systemd: <TIMESTAMP> 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
mysqld_pre_systemd: <TIMESTAMP> 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
mysqld_pre_systemd: <TIMESTAMP> 0 [ERROR] --initialize specified but the data directory has files in it. Aborting.
mysqld_pre_systemd: <TIMESTAMP> 0 [ERROR] Aborting
mysqld: <TIMESTAMP> 0 [Warning] Changed limits: max_open_files: 5000 (requested 5010)
mysqld: <TIMESTAMP> 0 [Warning] Changed limits: table_open_cache: 1995 (requested 2000)
mysqld: <TIMESTAMP> 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
mysqld: <TIMESTAMP> 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
mysqld: <TIMESTAMP> 0 [Note] /usr/sbin/mysqld (mysqld 5.7.23-enterprise-commercial-advanced-log) starting as process <PID> ...
mysqld: <TIMESTAMP> 0 [ERROR] You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentation
mysqld: <TIMESTAMP> 0 [ERROR] Aborting
systemd: mysqld.service: control process exited, code=exited status=1
mysqld: <TIMESTAMP> 0 [Note] Binlog end
mysqld: Initialization of mysqld failed: 0
mysqld: <TIMESTAMP> 0 [Note] /usr/sbin/mysqld: Shutdown complete
systemd: Failed to start MySQL Server.
systemd: Unit mysqld.service entered failed state.
systemd: mysqld.service failed.
systemd: mysqld.service holdoff time over, scheduling restart.
mysqld_pre_systemd: <TIMESTAMP> 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
mysqld_pre_systemd: <TIMESTAMP> 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
mysqld_pre_systemd: <TIMESTAMP> 0 [ERROR] --initialize specified but the data directory has files in it. Aborting.
mysqld_pre_systemd: <TIMESTAMP> 0 [ERROR] Aborting
mysqld: <TIMESTAMP> 0 [Warning] Changed limits: max_open_files: 5000 (requested 5010)
mysqld: <TIMESTAMP> 0 [Warning] Changed limits: table_open_cache: 1995 (requested 2000)
mysqld: <TIMESTAMP> 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
mysqld: <TIMESTAMP> 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
mysqld: <TIMESTAMP> 0 [Note] /usr/sbin/mysqld (mysqld 5.7.23-enterprise-commercial-advanced-log) starting as process <PID> ...
mysqld: <TIMESTAMP> 0 [ERROR] You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentation
mysqld: <TIMESTAMP> 0 [ERROR] Aborting
systemd: mysqld.service: control process exited, code=exited status=1
mysqld: <TIMESTAMP> 0 [Note] Binlog end
mysqld: Initialization of mysqld failed: 0
mysqld: <TIMESTAMP> 0 [Note] /usr/sbin/mysqld: Shutdown complete
systemd: Failed to start MySQL Server.
systemd: Unit mysqld.service entered failed state.
systemd: mysqld.service failed.
systemd: mysqld.service holdoff time over, scheduling restart.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |