Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.1.9
-
None
-
CentOS 7.1 64bit
Description
It seems MariaDB changed the service name for CentOS 7 yum packages of MariaDB 10.1.9 ? prior it was service name = mysql but now mariadb ?
However, both servcie names exist but for mysql service name you get incorrectly reported error that mysql isn't running. CentOS 7 usually can use both service or systemctl versions together.
Problem Summary
these 3 work
service mariadb status
|
systemctl status mysql
|
systemctl status mariadb
|
but this doesn't
service mysql status
|
Problem Details
service mysql status
|
ERROR! MySQL is running but PID file could not be found
|
service mariadb status
|
Redirecting to /bin/systemctl status mariadb.service
|
mariadb.service - MariaDB database server
|
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled)
|
Drop-In: /etc/systemd/system/mariadb.service.d
|
└─migrated-from-my.cnf-settings.conf
|
Active: active (running) since Tue 2015-12-01 17:23:15 UTC; 24min ago
|
Main PID: 907 (mysqld)
|
Status: "Taking your SQL requests now..."
|
CGroup: /system.slice/mariadb.service
|
└─907 /usr/sbin/mysqld
|
but seems only systemctl mysql service name works like it's mariadb service name counterpart
systemctl status mysql
|
mariadb.service - MariaDB database server
|
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled)
|
Drop-In: /etc/systemd/system/mariadb.service.d
|
└─migrated-from-my.cnf-settings.conf
|
Active: active (running) since Tue 2015-12-01 17:23:15 UTC; 34min ago
|
Main PID: 907 (mysqld)
|
Status: "Taking your SQL requests now..."
|
CGroup: /system.slice/mariadb.service
|
└─907 /usr/sbin/mysqld
|
Attachments
Issue Links
- is blocked by
-
-
- Closed
-
Activity
Looks like it was broken by this change: https://github.com/MariaDB/server/commit/fd1b2e486a9a81ffb5416e7a0a0d85d15598c77c
Saw _SYSTEMCTL_SKIP_REDIRECT=1 somehow made it into 10.1. Thought that was going to be a 10.0 workaround only (as 10.1 got the galera-new-cluster script).
I did start the documentation: https://mariadb.com/kb/en/mariadb/systemd/
For service mysql status to work there would need to be _SYSTEMCTL_SKIP_REDIRECT removed from the 10.1 scripts.
While all 4 given commands worked for me as expected, _SYSTEMCTL_SKIP_REDIRECT and SYSTEMD_NO_WRAP were not intended for 10.1 as it has systemd support. This bug could have been the side-effect of that.
https://github.com/MariaDB/server/commit/33f0cf71196d3d2869ccfcbf1c41a0a6709fe8df
svoj, danblack,
We already discussed this before, but there is no way I can intelligibly explain why it works the way it works, so you're up.
Better still, please somebody document it in the KB, so that we don't have to answer this very reasonable question over and over again (well, we'll still have to, but we'll be doing it by just providing the link).
Note: by the question I mean why service mysql ... does not work while systemctl mysql ... works.