[MDEV-9227] Both CentOS service names mysql and mariadb exist ? - Jira

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 10.1.9
Fix Version/s: 10.1.10
Component/s: Platform RedHat
Labels:
None
Environment:
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

MDEV-9328 service mysql status returns an error

Closed

Activity

Ascending order - Click to sort in descending order

George L created issue - 2015-12-01 19:59

George L made changes - 2015-12-01 20:02

Field	Original Value	New Value
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 {code:shell} service mysql status ERROR! MySQL is running but PID file could not be found {code} {code:shell} 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 {code} but seems only systemctl mysql service name works like it's mariadb service name counterpart {code:shell} 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 {code}	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 {code:shell}service mariadb status systemctl status mysql systemctl status mariadb{code} but this doesn't {code:shell}service mysql status{code} Problem Details {code:shell} service mysql status ERROR! MySQL is running but PID file could not be found {code} {code:shell} 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 {code} but seems only systemctl mysql service name works like it's mariadb service name counterpart {code:shell} 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 {code}

George L made changes - 2015-12-01 20:03

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
{code:shell}service mariadb status
systemctl status mysql
systemctl status mariadb{code}
but this doesn't
{code:shell}service mysql status{code}

*Problem Details*

{code:shell}
service mysql status
ERROR! MySQL is running but PID file could not be found
{code}

{code:shell}
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
{code}

but seems only systemctl mysql service name works like it's mariadb service name counterpart

{code:shell}
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
{code}

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

{code:shell}service mariadb status
systemctl status mysql
systemctl status mariadb{code}

but this doesn't

{code:shell}service mysql status{code}

*Problem Details*

{code:shell}
service mysql status
ERROR! MySQL is running but PID file could not be found
{code}

{code:shell}
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
{code}

but seems only systemctl mysql service name works like it's mariadb service name counterpart

{code:shell}
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
{code}

George L made changes - 2015-12-01 20:03

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

{code:shell}service mariadb status
systemctl status mysql
systemctl status mariadb{code}

but this doesn't

{code:shell}service mysql status{code}

*Problem Details*

{code:shell}
service mysql status
ERROR! MySQL is running but PID file could not be found
{code}

{code:shell}
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
{code}

but seems only systemctl mysql service name works like it's mariadb service name counterpart

{code:shell}
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
{code}

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

{code:none}service mariadb status
systemctl status mysql
systemctl status mariadb{code}

but this doesn't

{code:shell}service mysql status{code}

*Problem Details*

{code:shell}
service mysql status
ERROR! MySQL is running but PID file could not be found
{code}

{code:shell}
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
{code}

but seems only systemctl mysql service name works like it's mariadb service name counterpart

{code:shell}
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
{code}

George L made changes - 2015-12-01 20:03

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

{code:none}service mariadb status
systemctl status mysql
systemctl status mariadb{code}

but this doesn't

{code:shell}service mysql status{code}

*Problem Details*

{code:shell}
service mysql status
ERROR! MySQL is running but PID file could not be found
{code}

{code:shell}
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
{code}

but seems only systemctl mysql service name works like it's mariadb service name counterpart

{code:shell}
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
{code}

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

{code:none}service mariadb status
systemctl status mysql
systemctl status mariadb{code}

but this doesn't

{code:none}service mysql status{code}

*Problem Details*

{code:none}
service mysql status
ERROR! MySQL is running but PID file could not be found
{code}

{code:none}
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
{code}

but seems only systemctl mysql service name works like it's mariadb service name counterpart

{code:none}
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
{code}

Elena Stepanova added a comment - 2015-12-03 13:22 - edited

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.

Elena Stepanova added a comment - 2015-12-03 13:22 - edited 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.

Elena Stepanova made changes - 2015-12-03 13:22

Fix Version/s		10.1 [ 16100 ]
Assignee		Sergey Vojtovich [ svoj ]

Sergey Vojtovich added a comment - 2015-12-03 13:54

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

Sergey Vojtovich added a comment - 2015-12-03 13:54 Looks like it was broken by this change: https://github.com/MariaDB/server/commit/fd1b2e486a9a81ffb5416e7a0a0d85d15598c77c

Sergey Vojtovich made changes - 2015-12-03 13:54

Assignee

Sergey Vojtovich [ svoj ]

Nirbhay Choubey [ nirbhay_c ]

Nirbhay Choubey (Inactive) made changes - 2015-12-03 15:18

Fix Version/s		10.1.10 [ 20402 ]
Fix Version/s	10.1 [ 16100 ]

Daniel Black added a comment - 2015-12-04 11:13

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.

Daniel Black added a comment - 2015-12-04 11:13 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.

Nirbhay Choubey (Inactive) made changes - 2015-12-09 19:22

Status

Open [ 1 ]

In Progress [ 3 ]

Nirbhay Choubey (Inactive) added a comment - 2015-12-09 19:30

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

Nirbhay Choubey (Inactive) added a comment - 2015-12-09 19:30 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

Nirbhay Choubey (Inactive) made changes - 2015-12-09 19:30

Resolution		Fixed [ 1 ]
Status	In Progress [ 3 ]	Closed [ 6 ]

Ahmad El-Bardan made changes - 2015-12-27 00:43

Link

This issue is blocked by ~~MDEV-9328~~ [ ~~MDEV-9328~~ ]

Sergei Golubchik made changes - 2021-12-06 21:42

Workflow

MariaDB v3 [ 72829 ]

MariaDB v4 [ 149884 ]

People

Assignee:: Nirbhay Choubey (Inactive)

Reporter:: George L

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: 2015-12-01 19:59

Updated:: 2015-12-27 00:43

Resolved:: 2015-12-09 19:30

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.

MariaDB Server

Details

Description

Attachments

Issue Links

Activity

People

Dates

Git Integration