MySQL Forums
Forum List  »  Install & Repo

MySQL 8.0.13 database can't start on SAN disk (Linux)
Posted by: Yiu Wing Leung
Date: December 24, 2018 11:46PM

hi Guys,

I get a problem that the MyQL 8.0.13 can't start on SAN disk if I move the database to SAN disk.
mysql-community-server-8.0.13-1.sles12.x86_64
SLES 12 SP3, pacemaker cluster

The SAN disk path is /idm/var/lib/mysql, it get following error.

*******************************
node-1:/etc/apparmor/profiles/extras # systemctl status mysql.service
‚óŹ mysql.service - MySQL Server
Loaded: loaded (/usr/lib/systemd/system/mysql.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2018-12-24 23:00:03 HKT; 1min 25s ago
Docs: man:mysqld(8)
http://dev.mysql.com/doc/refman/en/using-systemd.html
Process: 29564 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS (code=exited, status=1/FAILURE)
Process: 29547 ExecStartPre=/usr/bin/mysqld_pre_systemd (code=exited, status=0/SUCCESS)
Main PID: 29564 (code=exited, status=1/FAILURE)
Status: "SERVER_BOOTING"
Error: 13 (Permission denied)

Dec 24 23:00:03 node-1 mysqld[29564]: 2018-12-24T15:00:03.953277Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.13) starting as process 29564
Dec 24 23:00:03 node-1 mysqld[29564]: 2018-12-24T15:00:03.956665Z 0 [Warning] [MY-010091] [Server] Can't create test file /idm/var/lib/mysql/node-1.lower-test
Dec 24 23:00:03 node-1 mysqld[29564]: 2018-12-24T15:00:03.956680Z 0 [Warning] [MY-010159] [Server] Setting lower_case_table_names=2 because file system for /idm/var/lib/mysql/ is case insensitive
Dec 24 23:00:03 node-1 mysqld[29564]: 2018-12-24T15:00:03.957159Z 0 [ERROR] [MY-010172] [Server] failed to set datadir to /idm/var/lib/mysql/
Dec 24 23:00:03 node-1 mysqld[29564]: 2018-12-24T15:00:03.958486Z 0 [ERROR] [MY-010119] [Server] Aborting
Dec 24 23:00:03 node-1 mysqld[29564]: 2018-12-24T15:00:03.958649Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.13) MySQL Community Server - GPL.
Dec 24 23:00:03 node-1 systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE
Dec 24 23:00:03 node-1 systemd[1]: Failed to start MySQL Server.
Dec 24 23:00:03 node-1 systemd[1]: mysql.service: Unit entered failed state.
Dec 24 23:00:03 node-1 systemd[1]: mysql.service: Failed with result 'exit-code'.
********************

If migrate out the cluster resource (SAN disk mount point) to node-2, and copy database with the same path (means it is local) on node-1, the mysql can start.
There have no install AppArmor already.

Any setting that need the of MySQL database run SAN disk?

Regards
Thanks...KEN

Options: ReplyQuote


Subject
Written By
Posted
MySQL 8.0.13 database can't start on SAN disk (Linux)
December 24, 2018 11:46PM


Sorry, only registered users may post in this forum.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.