Public bug reported:
If an installation has a customized 50-server.cnf, the upgrade will move it:
> Preserving user changes to /etc/mariadb/mariadb.conf.d/50-server.cnf
(renamed from /etc/mysql/mariadb.conf.d/50-server.cnf)...
However, it will still have
pid-file=/run/mysqld/mysqld.pid
After a reboot, /run/mysqld will no longer exist, replaced by
/run/mariadbd
This will cause mariadbd to crash with:
[ERROR] mariadbd: Can't create/write to file '/run/mysqld/mysqld.pid'
(Errcode: 2 \"No such file or directory\")
[ERROR] Can't start server: can't create PID file: No such file or
directory"
systemd: "mariadb.service: Failed with result 'core-dump'.
In a perpetual loop.
The postinst script *does* symlink, meaning that *before* a reboot, all
works as expected, however that symlink does NOT survive a reboot,
causing breakage after that point.
There is a workaround in replacing pid-file manually with
/run/mariadbd/mysqld.pid
** Affects: mariadb (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2171444
Title:
mariadbd crash loop after resolute->stonking upgrade with customized
50-server.cnf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb/+bug/2171444/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
