mysql will not start on the Spectrum Report Manager (SRM) system running on Linux

Products

• Spectrum
• CA eHealth
• Network Observability

Issue/Introduction

mysql will not start on the Spectrum Report Manager (SRM) system running on Linux

The following is seen in the $SPECROOT/mysql/bin/MYSQL.OUT file:

██ 07:46:37 $ cat MYSQL.OUT

2020-07-12T10:58:21.369987Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)

2020-07-12T10:58:21.515462Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

2020-07-12T10:58:21.515491Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.

2020-07-12T10:58:21.515522Z 0 [Warning] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.

2020-07-12T10:58:21.515559Z 0 [Note] /ca/spectrum/mysql/bin//mysqld (mysqld 5.7.27-enterprise-commercial-advanced) starting as process 9813 ...

2020-07-12T10:58:21.529017Z 0 [Note] InnoDB: PUNCH HOLE support available

2020-07-12T10:58:21.529058Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2020-07-12T10:58:21.529063Z 0 [Note] InnoDB: Uses event mutexes

2020-07-12T10:58:21.529068Z 0 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier

2020-07-12T10:58:21.529073Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11

2020-07-12T10:58:21.529077Z 0 [Note] InnoDB: Using Linux native AIO

2020-07-12T10:58:21.529304Z 0 [Note] InnoDB: Number of pools: 1

2020-07-12T10:58:21.529391Z 0 [Note] InnoDB: Using CPU crc32 instructions

2020-07-12T10:58:21.532044Z 0 [Note] InnoDB: Initializing buffer pool, total size = 3G, instances = 2, chunk size = 128M

2020-07-12T10:58:21.701675Z 0 [Note] InnoDB: Completed initialization of buffer pool

2020-07-12T10:58:21.719909Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().

2020-07-12T10:58:21.732180Z 0 [ERROR] InnoDB: ./ib_logfile0 can't be opened in read-write mode.

2020-07-12T10:58:21.732241Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error

2020-07-12T10:58:22.332854Z 0 [ERROR] Plugin 'InnoDB' init function returned error.

2020-07-12T10:58:22.332898Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

2020-07-12T10:58:22.332906Z 0 [ERROR] Failed to initialize builtin plugins.

2020-07-12T10:58:22.332916Z 0 [ERROR] Aborting

 

2020-07-12T10:58:22.332927Z 0 [Note] Binlog end

2020-07-12T10:58:22.332982Z 0 [Note] Shutting down plugin 'CSV'

2020-07-12T10:58:22.332992Z 0 [Note] Shutting down plugin 'MyISAM'

2020-07-12T10:58:22.333410Z 0 [Note] /ca/spectrum/mysql/bin//mysqld: Shutdown complete

Environment

Release : Any

Component : Spectrum Core / SpectroSERVER

Cause

From the above MYSQL.OUT file, we see the following error:

2020-07-12T10:58:21.732180Z 0 [ERROR] InnoDB: ./ib_logfile0 can't be opened in read-write mode.

The most likely root cause are the permissions on the $SPECROOT/mysql/data/ib_logfile0 file

Resolution

Check the permissions on the mysql files. They should be owned by the user/group that owns the Spectrum installation. Change as needed.