Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.1.17
-
CentOS 7
-
10.1.30
Description
MariaDB 10.1.17 and other recent releases still include an init script as well as a systemd unit. The init script ships with chkconfig on and this causes a race condition as to which version of the daemon starts first. This has caused us significant problems with RPM updates and system reboots.
[jg4461@db2 ~]$ yum provides */init.d/mysql
|
MariaDB-server-10.1.16-1.el7.centos.x86_64 : MariaDB: a very fast and robust SQL database server
|
Repo : mariadb-enterprise-main
|
Matched from:
|
Filename : /etc/init.d/mysql
|
 |
MariaDB-server-10.1.17-1.el7.centos.x86_64 : MariaDB: a very fast and robust SQL database server
|
Repo : mariadb
|
Matched from:
|
Filename : /etc/init.d/mysql
|
Attachments
Issue Links
- blocks
-
MDEV-17961 SystemD "Alias=mysql" considered harmful
- Closed
- causes
-
MDEV-19706 RPM no longer installs init script on systemd systems, but preun script still tries to erase it
- Closed
- duplicates
-
MDEV-11046 systemd loses control of running daemon after RPM upgrade
- Closed
-
MDEV-15526 SysV init service deployed file '/etc/init.d/mysql' prevents systemctl disable command to work correctly (mariadb|mysql naming support) (debian/ubuntu)
- Closed
- is blocked by
-
MDEV-11045 RPM should execute systemctl daemon-reload after update
- Closed
- relates to
-
MDEV-12598 systemd-devel missing from p8 RPM build slaves
- Closed
-
MDEV-28759 Deployment of /etc/init.d/mysql causes issues
- Closed