Failed to start MariaDB 10 database server

enrico

Mysql is not working. I cannot access any dB, nor PhpMyAdmin. I'm using Debian 11 and aaPanel 7.0.25. Can you help me with the following logs?

service mysql status
root@vps:/var/lib/mysql# service mysql status ● mariadb.service - MariaDB 10.5.29 database server Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2025-09-29 12:12:50 CEST; 5min ago Docs: man:mariadbd(8) https://mariadb.com/kb/en/library/systemd/ Process: 3027615 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, > Process: 3027616 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited,> Process: 3027617 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=/usr/bin/ga> Process: 3027802 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (c> Main PID: 3027802 (code=exited, status=1/FAILURE) Status: "MariaDB server is down"

Sep 29 12:12:50 vps.mindteq.com mariadbd[3027802]: 2025-09-29 12:12:50 0 [ERROR] InnoDB: Plugin initializati> Sep 29 12:12:50 vps.mindteq.com mariadbd[3027802]: 2025-09-29 12:12:50 0 [Note] InnoDB: Starting shutdown... Sep 29 12:12:50 vps.mindteq.com mariadbd[3027802]: 2025-09-29 12:12:50 0 [ERROR] Plugin 'InnoDB' registratio> Sep 29 12:12:50 vps.mindteq.com mariadbd[3027802]: 2025-09-29 12:12:50 0 [Note] Plugin 'FEEDBACK' is disable> Sep 29 12:12:50 vps.mindteq.com mariadbd[3027802]: 2025-09-29 12:12:50 0 [ERROR] Could not open mysql.plugin> Sep 29 12:12:50 vps.mindteq.com mariadbd[3027802]: 2025-09-29 12:12:50 0 [ERROR] Failed to initialize plugin> Sep 29 12:12:50 vps.mindteq.com mariadbd[3027802]: 2025-09-29 12:12:50 0 [ERROR] Aborting Sep 29 12:12:50 vps.mindteq.com systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAIL> Sep 29 12:12:50 vps.mindteq.com systemd[1]: mariadb.service: Failed with result 'exit-code'. Sep 29 12:12:50 vps.mindteq.com systemd[1]: Failed to start MariaDB 10.5.29 database server.

InnodB error
250813 16:45:12 mysqld_safe Starting mariadbd daemon with databases from /www/server/data 2025-08-13 16:45:13 0 [Note] /www/server/mysql/bin/mariadbd (server 10.7.3-MariaDB-log) starting as process 1 249 ... 2025-08-13 16:45:13 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2025-08-13 16:45:13 0 [Note] InnoDB: Number of transaction pools: 1 2025-08-13 16:45:13 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2025-08-13 16:45:13 0 [Note] InnoDB: Initializing buffer pool, total size = 402653184, chunk size = 134217728 2025-08-13 16:45:13 0 [Note] InnoDB: Completed initialization of buffer pool 2025-08-13 16:45:13 0 [Note] InnoDB: 128 rollback segments are active. 2025-08-13 16:45:13 0 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2025-08-13 16:45:13 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2025-08-13 16:45:13 0 [ERROR] InnoDB: Cannot open datafile for read-only: './lessn/lessn_schema_info.ibd' OS error: 71 2025-08-13 16:45:13 0 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2025-08-13 16:45:13 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2025-08-13 16:45:13 0 [ERROR] InnoDB: Could not find a valid tablespace file for lessn/lessn_schema_info. Ple ase refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2025-08-13 16:45:13 0 [Warning] InnoDB: Ignoring tablespace for lessn/lessn_schema_info because it could not be opened. 2025-08-13 16:45:13 0 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2025-08-13 16:45:13 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2025-08-13 16:45:13 0 [ERROR] InnoDB: Cannot open datafile for read-only: './lessn/lessn_urls.ibd' OS error: 71 2025-08-13 16:45:13 0 [ERROR] InnoDB: Operating system error number 2 in a file operation. 2025-08-13 16:45:13 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2025-08-13 16:45:13 0 [ERROR] InnoDB: Could not find a valid tablespace file for lessn/lessn_urls. Please ref er to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2025-08-13 16:45:13 0 [Warning] InnoDB: Ignoring tablespace for lessn/lessn_urls because it could not be open ed. 2025-08-13 16:45:13 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2025-08-13 16:45:13 0 [Note] InnoDB: Setting file '/www/server/data/ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2025-08-13 16:45:13 0 [Note] InnoDB: File '/www/server/data/ibtmp1' size is now 12 MB. 2025-08-13 16:45:13 0 [Note] InnoDB: 10.7.3 started; log sequence number 31835520; transaction id 53270 2025-08-13 16:45:13 0 [Note] Plugin 'FEEDBACK' is disabled. 2025-08-13 17:08:04 0 [Note] InnoDB: Removed temporary tablespace data file: "/www/server/data/ibtmp1" 2025-08-13 17:08:04 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2025-08-13 17:08:04 0 [Note] InnoDB: Setting file '/www/server/data/ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2025-08-13 17:08:04 0 [Note] InnoDB: File '/www/server/data/ibtmp1' size is now 12 MB. 2025-08-13 17:08:04 0 [Note] InnoDB: 10.7.3 started; log sequence number 31835532; transaction id 53270 2025-08-13 17:08:04 0 [Note] Plugin 'FEEDBACK' is disabled. 2025-08-13 17:08:04 0 [Note] InnoDB: Loading buffer pool(s) from /www/server/data/ib_buffer_pool 2025-08-13 17:08:04 0 [Note] Recovering after a crash using mysql-bin 2025-08-13 17:08:04 0 [Note] Starting table crash recovery...

aaPanel_Kern

Execute command to check mysql
curl -k https://www.aapanel.com/script/mysql_check.sh | bash

enrico

Thank you for the fast answer. This is the output of the command:

% Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 4858 100 4858 0 0 11040 0 --:--:-- --:--:-- --:--:-- 11040 WARNING: apt does not have a stable CLI interface. Use with caution in scripts. mariadb-server-10.5/oldoldstable-security,now 1:10.5.29-0+deb11u1 amd64 [installed] mariadb-server-core-10.5/oldoldstable-security,now 1:10.5.29-0+deb11u1 amd64 [installed,automatic] There exists mysql installed using apt-get. mysql 2841614 0.0 3.6 2062712 113544 ? Sl Sep25 1:04 /usr/sbin/mariadbd --basedir=/usr --datadi r=/var/lib/mysql --plugin-dir=/usr/lib/mysql/plugin --user=mysql --skip-grant-tables --skip-log-error --log-e rror=/var/lib/mysql/vps.mindteq.com.err --open-files-limit=65535 --pid-file=/run/mysqld/mysqld.pid --socket=/ run/mysqld/mysqld.sock --port=3306 panel cannot be managed apt-get installed mysql/mariadb If you do not use it, please delete it. Before this, please do a server snapshot backup. Delete command: apt-get remove mariadb-server* rm -f /etc/systemd/system/mysqld.service /etc/systemd/system/mysql.service

aaPanel_Kern

Hello, please follow the prompts. Please make a server snapshot backup before operation

enrico

aaP_countrysite547

It appears that MariaDB is experiencing issues starting because it can’t find or access certain data files, such as the lessn_schema_info.ibd and lessn_urls.ibd. The error message Operating system error number 2 generally means the system is looking for a file in a location where it doesn’t exist.

A few things to check:

Check your paths: Ensure the file paths in your MariaDB configuration are correct. Sometimes, a minor error in the file location can cause this type of issue.
Permissions: Ensure that MariaDB has the right permissions to access those files and directories.
Corruption or missing tables: If those files are corrupted or missing, you may need to recover or restore them from a backup, or attempt to repair them with mysqlcheck.
Try InnoDB recovery mode: If you’re still stuck, you can try booting MariaDB in InnoDB recovery mode to bypass certain errors and recover data.
Check logs: The MariaDB error log may contain more detailed information, which can help pinpoint the exact cause of the issue.

Before you do anything, be sure to make a backup of your data, especially if you're working directly with tables or files.

Good luck!

aaP_sophiajons8

The error logs indicate that InnoDB is unable to access certain data files. This typically occurs when tablespace files are missing, paths are incorrect, or permissions are not set correctly. The first step would be to confirm that the /www/server/data/ directory and all database folders exist and are readable by the MySQL user. If any .ibd files are missing, MariaDB will refuse to start. In that case, you may need to restore the missing tables or remove references to them so the service can boot normally. Checking the MariaDB knowledge base on InnoDB data dictionary issues can guide you through fixing corrupted or missing tablespaces.

enrico

Among others, I have these files in /www/server/data:

aria_log.00000001
aria_log_control
ib_logfile0
ibdata1
ibtmp1

In the datadirectory I don't have:

ib_logfile1
lessn_schema_info.ibd
lessn_urls.ibd

There are no .ibd files at all. I don't have a backup (!)