#1148646 mariadb-server: new version of mariadb server breaks wordpress

Package:
mariadb-server
Source:
mariadb-server
Description:
MariaDB database server binaries
Submitter:
Eric Valette
Date:
2026-10-15 04:53:01 UTC
Severity:
normal
Tags:
#1148646#5
Date:
2026-09-21 13:44:57 UTC
From:
To:
Upgrading to this mariadb server breaks wordpress. I have the message
cannot connect to database while the site was previously working.

To fix I found two solutions:

1) replace localhost by 127.0.0.1 in the wordpress config
2) or create a link in /run :  ln -s mariadbd mysqld. Then restarting
apache makes the site works again.

I guess there are still things that use /run/mysql/mysqld.sock in wordpress...
Did not found were...

#1148646#10
Date:
2026-09-22 03:12:06 UTC
From:
To:
Hi!

After filing https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1148689
I just noticed this
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1148646 had also
been filed. They are about the same root cause.

This is a result of
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/178.

Based on teh crud search
https://codesearch.debian.net/search?q=run%2Fmysql%2Fmysqld&literal=1
the following packages have *some* kind of hard-coded reference to
run/mysql:

aiomysql
ansible
ansible-core
apparmor
asterisk
augeas
boost1.90
boost1.92
ceph
cl-qmynd
collectd
ddnet
debian-edu-install
dico
dovecot
ergochat
firejail
freedombox
ganglia
gnunet
golang-github-go-sql-driver-mysql
golang-github-percona-go-mysql
golang-github-xo-dburl
golang-github-ziutek-mymysql
grass
guix
icingadb
jc
jclic
jupyterhub
kamailio
kdb
kexi
ksystemlog
libdbd-mariadb-perl
libgda5
libnb-platform18-java
libnss-mysql
libreoffice
mariadb
mariadb-connector-java
matomo
monit
monitorix
mycli
mysql-9.7
mysql-connector-python
mysql++
nagios-plugins-contrib
netatalk
oar
openqa
openqa-server
openstack-cluster-installer
openstack-trove
orthanc-mysql
pacemaker
percona-toolkit
php-horde-prefs
php8.4
phpsysinfo
postfixadmin
postgresql-mysql-fdw
prometheus-mysqld-exporter
puppet-module-michaeltchapman-galera
puppet-module-puppetlabs-mysql
puppet-module-voxpupuli-collectd
pure-ftpd
px
pypy3
python-django
python-django-extensions
python-pymysql
python3.13
python3.14
python3.15
racket
rails
refpolicy
resource-agents
rsyslog
ruby-will-paginate
runit-services
rust-diesel
rustc
skeema
snmpsim
solarpowerlog
stunnel
tango
trillian
trufflehog
usql
wait4x
xapian-core
zabbix
zoneminder

WordPress or Mediawiki are not among the results however. Tango is in the list.

#1148646#13
Date:
2026-09-23 12:39:59 UTC
From:
To:
Hello,

Bug #1148646 in mariadb reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/4052c15f66b0bd7ac2df5d2c300b320d246822ef
------------------------------------------------------------------------
Add link from /run/mysqld to /run/mariadbd in mariadb-server-compat
(Closes: #1148646)
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1148646

#1148646#20
Date:
2026-09-23 12:54:00 UTC
From:
To:
We believe that the bug you reported is fixed in the latest version of
mariadb, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1148646@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Otto Kekäläinen <otto@debian.org> (supplier of updated mariadb package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Wed, 23 Sep 2026 10:10:10 +0000
Source: mariadb
Architecture: source
Version: 1:11.8.9+ds-4
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers <pkg-mysql-maint@lists.alioth.debian.org>
Changed-By: Otto Kekäläinen <otto@debian.org>
Closes: 1148646
Changes:
 mariadb (1:11.8.9+ds-4) unstable; urgency=medium
 .
   [ Lena Voytek ]
   * Add link from /run/mysqld to /run/mariadbd in mariadb-server-compat
     (Closes: #1148646)
Checksums-Sha1:
 53bf996916627e4afe5eda992958507437da68d3 5410 mariadb_11.8.9+ds-4.dsc
 7aa625ae9b5d62521f8204626f719a89b5268da1 306356 mariadb_11.8.9+ds-4.debian.tar.xz
 389c93b2eba2dee1b289ad8d9ccf6533f2a01822 13679 mariadb_11.8.9+ds-4_source.buildinfo
Checksums-Sha256:
 855dc35dfc13ed8a1014ae09c00f14f05f42d824a91dc0b8ec853b8b52a2d675 5410 mariadb_11.8.9+ds-4.dsc
 4b873dbd2d4c6666e97ee7a97d6fe78b7cc9c547ac7ab640f4bbe884072457cd 306356 mariadb_11.8.9+ds-4.debian.tar.xz
 47b8182648cf661dca8bb152da36a075b7c185d7ea848b033519a5edab9b3f5a 13679 mariadb_11.8.9+ds-4_source.buildinfo
Files:
 efcb7ebceaa978f2410f1600a31b6d3e 5410 database optional mariadb_11.8.9+ds-4.dsc
 fb0644ac6200aae4d3c869fd00227e32 306356 database optional mariadb_11.8.9+ds-4.debian.tar.xz
 7b89ab9e78592c398d59268d0b70ed32 13679 database optional mariadb_11.8.9+ds-4_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAmqzx6sACgkQvthEn87o
2oh70w//cxO21LJz6IC2pBXVP2ngS8hHofOPgHYp0uJJolTe0loMYnOnVKSRkc6e
XJwMYF1UVPFSux0hLb/ipIkobfIUH2jUKyGSphNFwKBw8dwwkP59NBEc7819adxx
Ed25zSSuoIdyTGiX8Xw/iQkOqCrLq6mWp2ZKPycf77uUBUxLP2jv/lmhuYsPjLo8
m7UKSalrxUtfKGLbs2u+GmgknAV7rcGoYCfk0p9kD2EkF4o6werO0USv0PgOlUpy
lb2p6WB9LM6D2Sj7WigiEjkZnQ3roJSbmVibhRZOx9ZVaEgE0tzMuPNrXQB8Gh8E
9BjB9oejy5Eg7hzXol0NJDlCkSdjJb4VSkqkoZcb1OExB2T6+QSYWmiGAkz1xJpG
2qL205OvNGczY3m0NeSEbS7hi52Yc1Jfc+3uPv0NAwKGq03CPSNvUo8kZEm1fuOR
W6da0Ti9R3nq5f5JlEpQ5PivELZkReB5JRvktFSkuWsnYMeSy5q4YbAjRgOdLdty
3MBgMdSIyiOxtrvMWkZxwpsGaMICmFkA3XC7HZBx/yRpjPPlnHgvdlqftITkYnvp
KS26FOuRj/rfy8IUUXQ5oTlDccoJEhzEsQnu309VJTYZEjw+29lhPRYJy/jf6//f
j9fn/Og5bu8Pny1SsIq9GrtWqETALezpbHD9jsHKps3pY4OJVMY=
=tWww
-----END PGP SIGNATURE-----

#1148646#29
Date:
2026-09-23 16:01:57 UTC
From:
To:
On Wed, 23 Sep 2026 12:54:00 +0000 Debian FTP Masters  <ftpmaster@ftp-master.debian.org> wrote:

I have reoppenend the bug as it does not chnage anyrthing:

ls -l /run/m*
-rw-r--r-- 1 root  root 98 23 sept. 17:50 /run/motd.dynamic

/run/mariadbd:
total 4
-rw-rw---- 1 mysql mysql 5 23 sept. 17:55 mysqld.pid
srwxrwxrwx 1 mysql mysql 0 23 sept. 17:55 mysqld.sock

/run/media:
total 0

/run/mount:
total 0


mariadb-client-compat: Version: 1:11.8.9+ds-4

#1148646#34
Date:
2026-09-24 04:28:29 UTC
From:
To:
Just derived here as a reboot after a recent mariadb broke things for me.
The symlink was indeed the fix for me too. Could it be because of my
old autogenerated /etc/mysql/debian.cnf file that still points to
/var/run/mysqld?

I do not that while the proposed fix does work for me, I needed to
manually install mariadb-server-compat . Somehow, I did not have that
package installed already.

#1148646#39
Date:
2026-10-15 04:04:38 UTC
From:
To:
I did a few upgrades from 1:10.11.18+deb12u1 to 1:10.11.19+deb12u1.

Most of these worked fine, but in one case, mariadb failed to stop.
I think this was because mariadb was running under socket activation
but there must have been other factors at play. I have not been
able to determine what the critical factor was; the couple of others
I checked were running under socket activation.

I did check for /var/run paths to the socket in the config,
this was only found in my.cnf.fallback.
debian.cnf contains (sans comments)

[client]
host     = localhost
user     = root
protocol = socket
[mysql_upgrade]
host     = localhost
user     = root
protocol = socket

The upgrade started normally enough

# apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  mariadb-backup mariadb-client mariadb-client-core mariadb-server mariadb-server-core
5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 21.5 MB of archives.
After this operation, 636 kB of additional disk space will be used.
Do you want to continue? [Y/n]
...
Fetched 21.5 MB in 3s (8,258 kB/s)
Reading changelogs... Done
Preconfiguring packages ...
(Reading database ... 86799 files and directories currently installed.)
Preparing to unpack .../mariadb-backup_1%3a10.11.19-0+deb12u1_amd64.deb ...
Unpacking mariadb-backup (1:10.11.19-0+deb12u1) over (1:10.11.18-0+deb12u1) ...
Preparing to unpack .../mariadb-server_1%3a10.11.19-0+deb12u1_amd64.deb ...
Warning: Stopping mariadb.service, but it can still be activated by:
  mariadb.socket
/var/lib/mysql: found previous version 10.11

at this point dpkg was stuck:

# ps -fade|grep maria
root      536865  536570  0 11:13 pts/4    00:00:00 /usr/bin/dpkg --status-fd 45 --no-triggers --unpack --auto-deconfigure
  /var/cache/apt/archives/mariadb-backup_1%3a10.11.19-0+deb12u1_amd64.deb
  /var/cache/apt/archives/mariadb-server_1%3a10.11.19-0+deb12u1_amd64.deb
  /var/cache/apt/archives/mariadb-server-core_1%3a10.11.19-0+deb12u1_amd64.deb
  /var/cache/apt/archives/mariadb-client-core_1%3a10.11.19-0+deb12u1_amd64.deb
  /var/cache/apt/archives/mariadb-client_1%3a10.11.19-0+deb12u1_amd64.
mysql     537002       1  0 11:13 ?        00:00:01 /usr/sbin/mariadbd
root      537018  537007  0 11:13 pts/4    00:00:00 /bin/sh /usr/sbin/invoke-rc.d mariadb stop
root      537021  537018  0 11:13 pts/4    00:00:00 systemctl stop mariadb.service


'systemctl status mariadb' was showing

Active: deactivating (final-sigterm) (Result: timeout)
TriggeredBy: * mariadb.socket

Eventually I killed the shell doing the restart (537018) and then dpkg (536570).

/var/lib/dpkg/tmp.ci/preinst: line 36: 537018 Killed                  invoke-rc.d mariadb stop
E: Sub-process /usr/bin/dpkg exited unexpectedly
W: Operation was interrupted before it could finish

The mariadb process sailed on, I could not access mysql.
# /usr/bin/mysql
<crickets>


After reading this bug, I ran these commands

# systemctl stop mariadb.socket.         #no impact?
# systemctl disable --now mariadb.socket
# systemctl mask mariadb.socket


'systemctl status mariadb' then showed:

Active: activating (auto-restart) (Result: resources)


but was not properly restarting because a mariadb process
was left running (this is why Result: was 'resources').

I waited for several minutes, then 'kill -9 <that process>'


At this point I was able to start the service normally.
# systemctl stop mariadb
Active: inactive (dead) since ...

# systemctl start mariadb

# systemct status mariadb

Active: active (running)
<no TriggeredBy line>

Kind regards

#1148646#44
Date:
2026-10-15 04:44:00 UTC
From:
To:
apologies, wrong bug. Meant for 1141976.