[MDEV-9227] Both CentOS service names mysql and mariadb exist ? Created: 2015-12-01  Updated: 2015-12-27  Resolved: 2015-12-09

Status: Closed
Project: MariaDB Server
Component/s: Platform RedHat
Affects Version/s: 10.1.9
Fix Version/s: 10.1.10

Type: Bug Priority: Major
Reporter: George L Assignee: Nirbhay Choubey (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Environment:

CentOS 7.1 64bit

Issue Links:
Blocks
is blocked by MDEV-9328 service mysql status returns an error Closed

 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



 Comments   
Comment by Elena Stepanova [ 2015-12-03 ]

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.

Comment by Sergey Vojtovich [ 2015-12-03 ]

Looks like it was broken by this change: https://github.com/MariaDB/server/commit/fd1b2e486a9a81ffb5416e7a0a0d85d15598c77c

Comment by Daniel Black [ 2015-12-04 ]

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.

Comment by Nirbhay Choubey (Inactive) [ 2015-12-09 ]

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

Generated at Thu Feb 08 07:33:05 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.