Cannot get Mysql to start on Leap

English Applications
#1

I have a new build of Leap 42.1. everything in is as the standard install built it. When I try to start (via Yast2) Mysql I get the following:

mysql.service - MySQL server Loaded: loaded (/usr/lib/systemd/system/mysql.service; enabled)
Active: activating (start-post) (Result: exit-code) since Sun 2016-06-26 17:04:40 EDT; 34s ago
Process: 20523 ExecStart=/usr/lib/mysql/mysql-systemd-helper start default (code=exited, status=1/FAILURE)
Process: 20514 ExecStartPre=/usr/lib/mysql/mysql-systemd-helper upgrade default (code=exited, status=0/SUCCESS)
Process: 20507 ExecStartPre=/usr/lib/mysql/mysql-systemd-helper install default (code=exited, status=0/SUCCESS)
Main PID: 20523 (code=exited, status=1/FAILURE); : 20524 (mysql-systemd-h)
CGroup: /system.slice/mysql.service -control |-20524 /bin/bash /usr/lib/mysql/mysql-systemd-helper wait default -21934 sleep 1
Jun 26 17:04:40 mmgdb001 mysql-systemd-helper[20523]: 160626 17:04:40 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
Jun 26 17:04:40 mmgdb001 mysql-systemd-helper[20523]: 160626 17:04:40 [ERROR] mysqld: File ‘/var/lib/mysql/aria_log_control’ not found (Errcode: 13 “Permission denied”)
Jun 26 17:04:40 mmgdb001 mysql-systemd-helper[20523]: 160626 17:04:40 [ERROR] mysqld: Got error ‘Can’t open file’ when trying to use aria control file ‘/var/lib/mysql/aria_log_control’
Jun 26 17:04:40 mmgdb001 mysql-systemd-helper[20523]: 160626 17:04:40 [ERROR] Plugin ‘Aria’ init function returned error.
Jun 26 17:04:40 mmgdb001 mysql-systemd-helper[20523]: 160626 17:04:40 [ERROR] Plugin ‘Aria’ registration as a STORAGE ENGINE failed.
Jun 26 17:04:40 mmgdb001 mysql-systemd-helper[20523]: 160626 17:04:40 [ERROR] Can’t open the mysql.plugin table. Please run mysql_upgrade to create it.
Jun 26 17:04:40 mmgdb001 mysql-systemd-helper[20523]: 160626 17:04:40 [ERROR] Unknown/unsupported storage engine: InnoDB
Jun 26 17:04:40 mmgdb001 mysql-systemd-helper[20523]: 160626 17:04:40 [ERROR] Aborting Jun 26 17:04:40 mmgdb001 mysql-systemd-helper[20523]: 160626 17:04:40 [Note] /usr/sbin/mysqld: Shutdown complete
Jun 26 17:04:40 mmgdb001 systemd[1]: mysql.service: main process exited, code=exited, status=1/FAILURE

I spent several hours researching the InnoDB error and tried numerous suggestion with zero success, finally just rebuilt the machine, but still get this error. This is a virtual machine running under virtual box.

#2

The message says that it cannot find the InnoDB plugin and so it is defaulting to the Aria storate engine. Have you added

[mysqld]]
ignore_builtin_innodb
plugin_load=innodb=ha_innodb.so
# The following should not be needed if you are
using a mariadb package:
plugin_dir=/usr/local/mysql/lib/mysql/plugin

to my.cnf as described in the MariaDB documentation?

#3

ok, that fixed a few things, now I get:

Jun 26 19:59:06 mmgdb001 mysql-systemd-helper[21392]: 160626 19:59:06 [Note] InnoDB: Initializing buffer pool, size = 128.0M

Jun 26 19:59:06 mmgdb001 mysql-systemd-helper[21392]: 160626 19:59:06 [Note] InnoDB: Completed initialization of buffer pool

Jun 26 19:59:06 mmgdb001 mysql-systemd-helper[21392]: 160626 19:59:06 [ERROR] InnoDB: ./ibdata1 can’t be opened in read-write mode

Jun 26 19:59:06 mmgdb001 mysql-systemd-helper[21392]: 160626 19:59:06 [ERROR] InnoDB: The system tablespace must be writable!

Jun 26 19:59:06 mmgdb001 mysql-systemd-helper[21392]: 160626 19:59:06 [ERROR] Plugin ‘InnoDB’ init function returned error.

Jun 26 19:59:06 mmgdb001 mysql-systemd-helper[21392]: 160626 19:59:06 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.

Jun 26 19:59:06 mmgdb001 mysql-systemd-helper[21392]: 160626 19:59:06 [ERROR] Unknown/unsupported storage engine: InnoDB

Jun 26 19:59:06 mmgdb001 mysql-systemd-helper[21392]: 160626 19:59:06 [ERROR] Aborting

Jun 26 19:59:06 mmgdb001 mysql-systemd-helper[21392]: 160626 19:59:06 [Note] /usr/sbin/mysqld: Shutdown complete

Jun 26 19:59:06 mmgdb001 systemd[1]: mysql.service: main process exited, code=exited, status=1/FAILURE

Checked that the file had proper permissions. it seems to:

mmgdb001:/var/lib/mysql # ls -la
total 110612
drwxr-xr-x 1 root root 178 Jun 26 19:59 .
drwxr-xr-x 1 root root 740 Jun 26 15:38 …
-rw-rw---- 1 root root 16384 Jun 26 19:57 aria_log.00000001
-rw-rw---- 1 root root 52 Jun 26 19:57 aria_log_control
-rw-rw---- 1 root root 50331648 Jun 26 19:57 ib_logfile0
-rw-rw---- 1 root root 50331648 Jun 26 15:47 ib_logfile1
-rw-rw---- 1 root root 12582912 Jun 26 19:57 ibdata1
drwx------ 1 root root 2600 Jun 26 15:47 mysql
drwx------ 1 root root 3296 Jun 26 19:57 performance_schema
drwx------ 1 root root 0 Jun 26 15:47 test

checked mount and confirmed that it is mounted rw, it is,

Spent some time researching, no answers, any thoughts?

#4

What were your initial steps installing MySQL/Mariadb?
Did you import your data before starting up even for the first time or is this <really> a default install?

If you didn’t, I recommend the following steps in order…

  • install MySQL/Mariadb using YAST or zypper, either specifying the package or using a pattern.
    The result should be a <default> installation.

  • Start MySQL/Mariadb manually.
    The first time you do this, you will be prompted to configure MySQL security. The alternative is to run “mysql_secure_installation” directly. You can also automate the interactive answers running the script I provide and describe here
    https://en.opensuse.org/User:Tsu2/MySQL_and_Mariadb

  • If there are special plugin requirements, address them now.
    Re your specific errors, do you need or want that innodb plugin or not? (I may be incorrect, but I thought that innodb is implemented by default nowadays)

  • Lastly, import the data <only> after you have verified that a default installation of MySQL/Mariadb will run without error with no data.

TSU

#5

I’m not sure what was wrong here. The whole build seemed full of odd problems. So I’ve downloaded the .iso again and rebuilt the machine once more. This time everything works as it should. Issue closed.

#6

For any new install (or re-install returning openSUSE to its original release), you should always update the system immediately to pull in everything that has been released since, including fixes, patches, feature enhancements.

zypper up

TSU