MySQL - Connection Error: No such file or directory [SOLVED]

[Keyfolk]

I'm sure the cause of the problem is within KeyHelp
(e.g. Yes


Server operating system + version
Debian 12


Server virtualization technology used
KVM


KeyHelp version + build number
im not sure


Problem description / error messages

Please help me. Suddenly, my websites are no longer accessible.

The error displayed is:

**Service Unavailable**

> The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

When I try to log in to the KeyHelp admin dashboard, I get the following error:

**MySQL - Connection Error: No such file or directory**

How can I fix this?

Here is the output of the MariaDB service log:

```bash
~# journalctl -xeu mariadb.service --no-pager | tail -n 30

Aug 08 05:57:00 hela.xpanel.my.id mariadbd[955]: 2026-08-08 05:57:00 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool

Aug 08 05:57:00 hela.myserver.com mariadbd[955]: 2026-08-08 05:57:00 0 [Note] Plugin 'FEEDBACK' is disabled.

Aug 08 05:57:00 hela.myserver.com mariadbd[955]: 2026-08-08 05:57:00 0 [ERROR] /usr/sbin/mariadbd: unknown variable 'provider_bzip2=force_plus_permanent'

Aug 08 05:57:00 hela.myserver.com mariadbd[955]: 2026-08-08 05:57:00 0 [ERROR] /usr/sbin/mariadbd: unknown variable 'provider_lz4=force_plus_permanent'

Aug 08 05:57:00 hela.myserver.com mariadbd[955]: 2026-08-08 05:57:00 0 [ERROR] /usr/sbin/mariadbd: unknown variable 'provider_lzma=force_plus_permanent'

Aug 08 05:57:00 hela.myserver.com mariadbd[955]: 2026-08-08 05:57:00 0 [ERROR] /usr/sbin/mariadbd: unknown variable 'provider_lzo=force_plus_permanent'

Aug 08 05:57:00 hela.myserver.com mariadbd[955]: 2026-08-08 05:57:00 0 [ERROR] /usr/sbin/mariadbd: unknown variable 'provider_snappy=force_plus_permanent'

Aug 08 05:57:00 hela.myserver.com mariadbd[955]: 2026-08-08 05:57:00 0 [ERROR] Aborting

Aug 08 05:57:01 hela.myserver.com systemd[1]: mariadb.service: Main process exited, code=exited, status=7/NOTRUNNING

Subject: Unit process exited

An ExecStart= process belonging to unit mariadb.service has exited.

The process exited with status code 7.

Aug 08 05:57:01 hela.myserver.com systemd[1]: mariadb.service: Failed with result 'exit-code'.

Subject: Unit failed

The unit mariadb.service has entered the 'failed' state with result 'exit-code'.

Aug 08 05:57:01 hela.myserver.com systemd[1]: Failed to start mariadb.service - MariaDB 10.11.14 database server.

Subject: A start job for unit mariadb.service has failed.

The job identifier is 103 and the job result is failed.
```


Expected result


Actual result


Steps to reproduce


Additional information
(e.g. recent changes to the server, excerpts from log files (/var/log/*, /var/log/keyhelp/php-error.log, etc.))


.

[24unix]

apt update
apt upgrade

I had the same issue today on a customers server.

[Florian]

Hello,

just run:

Code: Select all

apt install mariadb-plugin-provider-lz4

It seems there is a bug in the last updates of Debian.

[tab-kh]

Is this a Debian 12 only problem? Did the Debian update remove the package? I have several Debian 13 servers, not showing this problems (yet?). Should I be worried about suddenly running in the same bug?

[24unix]

Is this a Debian 12 only problem? Did the Debian update remove the package? I have several Debian 13 servers, not showing this problems (yet?). Should I be worried about suddenly running in the same bug?

The customer where I had the issue is still on Debian 12.

[Florian]

Is this a Debian 12 only problem? Did the Debian update remove the package? I have several Debian 13 servers, not showing this problems (yet?). Should I be worried about suddenly running in the same bug?

The customer where I had the issue is still on Debian 12.

Same here.

[tab-kh]

Ok, thanks. So I guess there is no need for me to be alerted, seems to be Debian 12 only then. Some very small servers are still running on Debian 12, but none of them has MySQL/MariaDB installed.

[Fezzi]

After reading this post, I checked on my test server (where I run some not critical web sites) and just restarted it. The same problem occurred.

Running the install Florian proposed had no effect and said it's already installed.
Doing then the apt update and apt upgrade as 24unix proposed, nothing was updated or upgraded, but afterwards everything was running again.

Checking the logs didn't bring up any reasonable explanation.

[xister]

We had this issue on several systems as well, and the following fix helped.

Code: Select all

cd /etc/mysql/mariadb.conf.d

for f in provider_*.cnf; do
    mv "$f" "$f.disabled"
done

[Tiresias]

We had the same problem a few days ago on Debian 12.
In our case, however, it was caused by "unattended upgrades" on some servers, because it still seems to be using `apt-get upgrade` instead of `apt upgrade`, which does not install new Dependencies. mariadb-common and the providers were upgraded to 1.11.18, but mariadb-server* and mariadb-client* were not updated and remained at 1.11.14 because libaio1 was not installed.

We didn’t notice this until after a server reboot, because then the different versions prevented MariaDB from starting.

A bold `apt upgrade` or even `apt full-upgrade` immediately resolved the issue. libaio1 was then installed, and the mariadb-server* and mariadb-client* packages were fully upgraded.

Code: Select all

Start-Date: 2026-07-13 03:00:31 Commandline: apt-get -o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confold -y upgrade 
Upgrade: mariadb-plugin-provider-bzip2:amd64 (1:10.11.14-0+deb12u2, 1:10.11.18-0+deb12u1), mariadb-plugin-provider-lzma:amd64 (1:10.11.14-0+deb12u2, 1:10.11.18-0+deb12u1),  [...] mariadb-common:amd64 (1:10.11.14-0+deb12u2, 1:10.11.18-0+deb12u1), libmariadb3:amd64 (1:10.11.14-0+deb12u2, 1:10.11.18-0+deb12u1), apache2:amd64 (2.4.67-1~deb12u3, 2.4.68-1~deb12u1), mariadb-plugin-provider-lz4:amd64 (1:10.11.14-0+deb12u2, 1:10.11.18-0+deb12u1), mariadb-plugin-provider-lzo:amd64 (1:10.11.14-0+deb12u2, 1:10.11.18-0+deb12u1) End-Date: 2026-07-13 03:02:53

Start-Date: 2026-07-15 14:46:06 Commandline: apt full-upgrade Install: libaio1:amd64 (0.3.113-4, automatic) Upgrade: mariadb-server:amd64 (1:10.11.14-0+deb12u2, 1:10.11.18-0+deb12u1), mariadb-client-core:amd64 (1:10.11.14-0+deb12u2, 1:10.11.18-0+deb12u1), mariadb-server-core:amd64 (1:10.11.14-0+deb12u2, 1:10.11.18-0+deb12u1), mariadb-client:amd64 (1:10.11.14-0+deb12u2, 1:10.11.18-0+deb12u1) End-Date: 2026-07-15 14:47:10