On Sun, 16 Mar 2025 14:38:45 +0000 "Gareth Evans" <donots...@fastmail.fm> wrote:
> On Sun 16/03/2025 at 11:01, Joe <j...@jretrading.com> wrote: > > > What's the background here? Did you have a working mariadb > > installation before, and is it still working? > > Hi Joe, > > It was working before and after the failed upgrade, as neither it nor > anything else had been upgraded. > > I copied mariadb.cnf from the extracted mariadb-common package files > to /etc/mysql/ and retried the upgrade, which succeeded, but mariadb > then produced "SQLSTATE <some code> no such file or directory" errors > in my web apps, so I restarted the mariadb service, and got: > > $ sudo systemctl status mariadb > × mariadb.service - MariaDB 10.11.11 database server > Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; > preset: enabled) Active: failed (Result: exit-code) since Sun > 2025-03-16 14:21:46 GMT; 15s ago Duration: 7h 28min 31.155s > Docs: man:mariadbd(8) > https://mariadb.com/kb/en/library/systemd/ > Process: 1777879 ExecStartPre=/usr/bin/install -m 755 -o mysql -g > root -d /var/run/mysqld (code=exited, status=0/SUCCESS) Process: > 1777880 ExecStartPre=/bin/sh -c systemctl unset-environment > _WSREP_START_POSITION (code=exited, status=0/SUCCESS) Process: > 1777882 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && > VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl > set-environment> Process: 1777899 ExecStart=/usr/sbin/mariadbd > $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, > status=1/FAILURE) Main PID: 1777899 (code=exited, status=1/FAILURE) > CPU: 102ms > > Mar 16 14:21:46 qwerty.local systemd[1]: Starting mariadb.service - > MariaDB 10.11.11 database server... Mar 16 14:21:46 qwerty.local > sh[1777896]: [108B blob data] Mar 16 14:21:46 qwerty.local > sh[1777896]: Fatal error in defaults handling. Program aborted Mar 16 > 14:21:46 qwerty.local mariadbd[1777899]: [100B blob data] Mar 16 > 14:21:46 qwerty.local mariadbd[1777899]: Fatal error in defaults > handling. Program aborted Mar 16 14:21:46 qwerty.local systemd[1]: > mariadb.service: Main process exited, code=exited, status=1/FAILURE > Mar 16 14:21:46 qwerty.local systemd[1]: mariadb.service: Failed with > result 'exit-code'. Mar 16 14:21:46 qwerty.local systemd[1]: Failed > to start mariadb.service - MariaDB 10.11.11 database server. > > > Same state reported after a reboot. > > Then: > > $ sudo mv /etc/mysql/mariadb.cnf /etc/mysql/mariadb.cnf.xxx > > $ sudo systemctl restart mariadb > > $ sudo systemctl status mariadb > > ● mariadb.service - MariaDB 10.11.11 database server > Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; > preset: enab> Active: active (running) since Sun 2025-03-16 14:30:37 > GMT; 4s ago ... > > So working again, but a messy/broken upgrade process for me. > > Is this worth reporting? > Yes, I would think so, most Debian servers will be running mariadb on bookworm, either for production use or for internal purposes or both. Sid is on mariadb 11.4.5, so while it would have used the current bookworm version at some time, the fact that there has just been an upgrade in stable means a security fix for a bug that was not known when it was in sid. -- Joe
