Package: mariadb-server-10.1 Version: 10.1.26-0+deb9u1 Severity: grave Hi, I just upgraded my server from jessie to stretch and I face a bug I already reported 13 month ago as bug #837166 but unfortunately this bug was closed when the related package (mysql-server-5.6) was removed from archive. But the bug is still present in mariadb-server-10.1 shiped within stretch repository (no backport).
What is expected: “systemctl start mariadb” starts mariadb server. What is happening: mariadb server shutdowns at startup printing “[ERROR] Can't find messagefile '/usr/share/mysql/errmsg.sys'” error message. Another interesting fact: starting “/usr/sbin/mysqld” from command line in an interactive shell leads to a working mysql server, but the exact same command started by systemd leads to a instantaneous shutdown with error reporting as stated. Output of “systemctl status mariadb.service” command: oct. 25 06:49:35 machine mysqld[4868]: 2017-10-25 4:49:35 140131405656640 [Note] /usr/sbin/mysqld (mysqld 10.1.26-MariaDB-0+deb9u1) starting as process 4868 ... oct. 25 06:49:35 machine mysqld[4868]: 2017-10-25 4:49:35 140131405656640 [ERROR] Can't find messagefile '/usr/share/mysql/errmsg.sys' For rerefence, the initial bug report (now closed and archived) with some detailed explanations: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837166 I set the severity of this bug to “grave” since this bug makes the package unusable. The package mariadb-server-10.1=10.1.26-0+deb9u1 is unusable since the service is not startable. The mysql-server-5.5=5.5.58-0+deb8u1 package from jessie is known to not be affected by the bug. A prior occurrence to this bug was reported on mysql-server-5.6=5.6.30-1~bpo8+1 at the date of 2016-09-09. The mariadb-server-10.1=10.1.26-0+deb9u1 package is known to still be affected by the bug at the date of 2017-10-25. Previous bug report #837166 says the bug was fixed in version 5.6.35-1+rm, but it's now verified the bug is still there in lately versions. -- Thomas Debesse
