root@moodle:~# 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 Fri 2025-03-28 09:53:18 UTC; 2 days ago
Docs: man:mariadbd(8)
https://mariadb.com/kb/en/library/systemd/
Process: 556 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Process: 575 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 582 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 >
Process: 652 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILUR>
Main PID: 652 (code=exited, status=1/FAILURE)
Status: "MariaDB server is down"
CPU: 215ms
Mar 28 09:53:18 moodle mariadbd[652]: 2025-03-28 9:53:18 0 [ERROR] InnoDB: File ./ib_logfile0 was not found
Mar 28 09:53:18 moodle mariadbd[652]: 2025-03-28 9:53:18 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
Mar 28 09:53:18 moodle mariadbd[652]: 2025-03-28 9:53:18 0 [Note] InnoDB: Starting shutdown...
Mar 28 09:53:18 moodle mariadbd[652]: 2025-03-28 9:53:18 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Mar 28 09:53:18 moodle mariadbd[652]: 2025-03-28 9:53:18 0 [Note] Plugin 'FEEDBACK' is disabled.
Mar 28 09:53:18 moodle mariadbd[652]: 2025-03-28 9:53:18 0 [ERROR] Unknown/unsupported storage engine: InnoDB
Mar 28 09:53:18 moodle mariadbd[652]: 2025-03-28 9:53:18 0 [ERROR] Aborting
Mar 28 09:53:18 moodle systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Mar 28 09:53:18 moodle systemd[1]: mariadb.service: Failed with result 'exit-code'.
Mar 28 09:53:18 moodle systemd[1]: Failed to start mariadb.service - MariaDB 10.11.11 database server.
lines 1-23/23 (END)
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hello, @admin1c235b282fa044969fa081215
MariaDB uses internal log files for InnoDB (like ib_logfile0 and ib_logfile1). If one is missing or corrupted, MariaDB cannot start because it relies on those to recover data and ensure consistency.
If you have backup of your data you can try restore from the backup file. If backup file is not present let me know and I can give you instructions on how to recover.
Regards
Hey there 👋
Before anything else, make sure you have a backup of your Droplet:
https://docs.digitalocean.com/products/backups/how-to/create-and-restore/
That way, if anything goes wrong, you can try to recover from the backup.
Now, looking at the logs, MariaDB is complaining that ib_logfile0 is missing. That file is part of the InnoDB storage engine, and without it, MariaDB can’t start.
⚠️ If you’re certain the data isn’t needed (like on a new setup), you can remove the log files and let MariaDB regenerate them, first stop the MariaDB service and then:
sudo rm -f /var/lib/mysql/ib_logfile*
sudo systemctl start mariadb
If you’re still having issues or want to dig deeper, share the output of:
journalctl -xeu mariadb
- Bobby
Failed to start mariadb.service - MariaDB 10.11.11 database server.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.