[debian-mysql] Bug#879728: closed by Otto Kekäläinen <otto at debian.org> (Re: Bug#879728: mysqld fails to start not finding messagefile when started by systemd)

[Thomas DEBESSE]

Note: the faulty package was not MariaDB but was likely to be
another Debian package because this server did not use
third-party software or software from non-Debian repositories.
I have seen the issue on more servers at the time, all of them
running Debian without third-party stuff. The other affected Debian
servers did not run MariaDB so this was less blocking.


Le lun. 21 sept. 2020 à 22:25, Thomas DEBESSE <debian at illwieckz.net> a
écrit :

> The failure of MariaDB came from a permission set by another process
> on a shared parent dir of that file.
> Then, this was the side effect of another software from another
> package I did not figure.
> Basically another software from another package removed some read
> permission to “other” (or something like that) to some directory that
> sits between / root directory and this file, maybe /usr/share or
> something like that.
> This permission change did not only affect MariaDB but also other
> softwares, some simple “sudo <specific command>” would have been able
> to reproduce the bug.
>
> The root cause, the package modifying some permission of some shared
> parent dir to make it less permissive than Debian default, was not
> found.
> As a workaround I've set a cron task restoring the default Debian
> folder permission every time.
> I don't work anymore for the ones running the affected server so I
> lost access to the faulty environment and cannot track down the faulty
> package anymore.
>
>
> Le lun. 21 sept. 2020 à 21:57, Debian Bug Tracking System
> <owner at bugs.debian.org> a écrit :
> >
> > This is an automatic notification regarding your Bug report
> > which was filed against the mariadb-server-10.1 package:
> >
> > #879728: mysqld fails to start not finding messagefile when started by
> systemd
> >
> > It has been closed by Otto Kekäläinen <otto at debian.org>.
> >
> > Their explanation is attached below along with your original report.
> > If this explanation is unsatisfactory and you have not received a
> > better one in a separate message then please contact Otto Kekäläinen <
> otto at debian.org> by
> > replying to this email.
> >
> >
> > --
> > 879728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879728
> > Debian Bug Tracking System
> > Contact owner at bugs.debian.org with problems
> >
> >
> >
> > ---------- Forwarded message ----------
> > From: "Otto Kekäläinen" <otto at debian.org>
> > To: 879728-done at bugs.debian.org
> > Cc:
> > Bcc:
> > Date: Mon, 21 Sep 2020 22:49:19 +0300
> > Subject: Re: [debian-mysql] Bug#879728: mysqld fails to start not
> finding messagefile when started by systemd
> > Control: tags -1 wontfix
> >
> > There was no further information provides, so closing this as 'wontfix'.
> >
> >
> > ---------- Forwarded message ----------
> > From: Thomas DEBESSE <debian at illwieckz.net>
> > To: submit at bugs.debian.org
> > Cc:
> > Bcc:
> > Date: Wed, 25 Oct 2017 08:33:48 +0200
> > Subject: mysqld fails to start not finding messagefile when started by
> systemd
> > 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
>
>
>
> --
> Thomas DEBESSE
>


-- 
Thomas DEBESSE
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-mysql-maint/attachments/20200921/98c82b7b/attachment-0001.html>