Comment # 1 on bug 956119 from Kristyna Streitova

Created attachment 661788 [details]
mariadb log

Hi, thank you for your report. 

I did some tests and it seems, that the problematic update was from
mariadb-5.5.33-2.2 to mariadb-5.5.44-4.1 where the package was reworked to use
native systemd services instead of init scripts.


How to reproduce (full log is attached):
----------------
# zypper in mariadb-5.5.33-2.2
# rcmysql start
# chkconfig mysql on
# chkconfig mysql
mysql  on
# zypper up mariadb-5.5.44-4.1
# systemctl status mysql
mysql.service - MySQL server
   Loaded: loaded (/usr/lib/systemd/system/mysql.service; disabled)
   Active: active (running) since Wed 2015-06-17 11:55:44 CEST; 1min 16s ago
   CGroup: /system.slice/mysql.service
           ������  477 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql
--plugin-dir=/usr/lib64/mysql/plugin --user=mysql
--log-error=/var/lib/mysql/linux-uo0a.err --pid-file=/var/run/mysql/mysqld.pid
--s...
           ������32725 /bin/sh /usr/bin/mysqld_safe --mysqld=mysqld --user=mysql
--pid-file=/var/run/mysql/mysqld.pid --socket=/var/run/mysql/mysql.sock
--datadir=/var/lib/mysql


I tried to install the further updates and there is no problem anymore (if the
service was enabled before update, it stays enabled after the update too).

However I'm afraid that there is nothing to do about this issue anymore. We
could just let users know about this problem so they can check and re-enable
their myslq service if it's needed.