New MariaDB error updating today

1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up mariadb-server (1:10.11.9+maria~deb12) …
Job for mariadb.service failed because the control process exited with error code.
See “systemctl status mariadb.service” and “journalctl -xeu mariadb.service” for details.
invoke-rc.d: initscript mariadb, action “restart” failed.
× mariadb.service - MariaDB 10.11.9 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; preset: enabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
Active: failed (Result: exit-code) since Fri 2024-08-09 11:11:51 MST; 8ms ago
Docs: man:mariadbd(8)
https://mariadb.com/kb/en/library/systemd/
Process: 3551 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Process: 3552 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 3554 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=/usr/bin/galera_recovery; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
Process: 3613 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=7)
Main PID: 3613 (code=exited, status=7)
Status: “MariaDB server is down”
CPU: 175ms

Aug 09 11:11:50 webserver.pacificdatacom.net mariadbd[3613]: 2024-08-09 11:11:50 0 [Note] Plugin ‘FEEDBACK’ is disabled.
Aug 09 11:11:50 webserver.pacificdatacom.net mariadbd[3613]: 2024-08-09 11:11:50 0 [ERROR] /usr/sbin/mariadbd: unknown variable ‘provider_bzip2=force_plus_permanent’
Aug 09 11:11:50 webserver.pacificdatacom.net mariadbd[3613]: 2024-08-09 11:11:50 0 [ERROR] /usr/sbin/mariadbd: unknown variable ‘provider_lz4=force_plus_permanent’
Aug 09 11:11:50 webserver.pacificdatacom.net mariadbd[3613]: 2024-08-09 11:11:50 0 [ERROR] /usr/sbin/mariadbd: unknown variable ‘provider_lzma=force_plus_permanent’
Aug 09 11:11:50 webserver.pacificdatacom.net mariadbd[3613]: 2024-08-09 11:11:50 0 [ERROR] /usr/sbin/mariadbd: unknown variable ‘provider_lzo=force_plus_permanent’
Aug 09 11:11:50 webserver.pacificdatacom.net mariadbd[3613]: 2024-08-09 11:11:50 0 [ERROR] /usr/sbin/mariadbd: unknown variable ‘provider_snappy=force_plus_permanent’
Aug 09 11:11:50 webserver.pacificdatacom.net mariadbd[3613]: 2024-08-09 11:11:50 0 [ERROR] Aborting
Aug 09 11:11:51 webserver.pacificdatacom.net systemd[1]: mariadb.service: Main process exited, code=exited, status=7/NOTRUNNING
Aug 09 11:11:51 webserver.pacificdatacom.net systemd[1]: mariadb.service: Failed with result ‘exit-code’.
Aug 09 11:11:51 webserver.pacificdatacom.net systemd[1]: Failed to start mariadb.service - MariaDB 10.11.9 database server.
dpkg: error processing package mariadb-server (–configure):
installed mariadb-server package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
mariadb-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

And fyi this does break some of the websites. Honestly, I hardly ever get any errors updating my Hestia web server this is very weird thing.

Try to install plugin packages:

apt install mariadb-plugin-provider-bzip2 mariadb-plugin-provider-lz4 mariadb-plugin-provider-lzma mariadb-plugin-provider-lzo mariadb-plugin-provider-snappy

And after that:

apt-get -f install
1 Like

Thanks but still get the error.

Same errors, less errors, other errors?

Same errors. So a little history I changed that repository on MariaDB From the old one that was still on Bullseye everything else was upgraded to use Bookworm repositories. So something to do with the database now using the newer repository the one you sent is the same one I upgraded it to.

So what repository should the MariaDB be using?

So, are you using this one?

> cat /etc/apt/sources.list.d/mariadb.list
deb [arch=amd64 signed-by=/usr/share/keyrings/mariadb-keyring.gpg] https://dlm.mariadb.com/repo/mariadb-server/10.11/repo/debian bookworm main

I suppose you messed the conf files:

ls -la /etc/mysql/
grep -Ev '^$|^#' /etc/mysql/mariadb.cnf
dpkg -l | grep -E '^ii\s*mariadb'

This repo you sent works… Not sure what I had. Like I said I just restored from a backup to before I broke it then put your repository in there for Bookworm and everything worked perfectly.

cat /etc/apt/sources.list.d/mariadb.list
deb [arch=amd64 signed-by=/usr/share/keyrings/mariadb-keyring.gpg] https://dlm.mariadb.com/repo/mariadb-server/10.11/repo/debian bookworm main

2 Likes

root@webserver:~# apt update && apt upgrade -y
Hit:1 Index of /debian bookworm InRelease
Hit:2 Index of /debian-security bookworm-security InRelease
Hit:3 Index of /debian bookworm-updates InRelease
Hit:4 Index of /apache2/ bookworm InRelease
Hit:5 Index of /php/ bookworm InRelease
Hit:6 https://dlm.mariadb.com/repo/mariadb-server/10.11/repo/debian bookworm InRelease
Hit:7 Index of /packages/mainline/debian/ bookworm InRelease
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
All packages are up to date.
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Calculating upgrade… Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Thank you Sahsanu

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.