Mariadb broken, please help

Hestia Control Panel
1

Hi,

A few days ago, my website usually get errors then I thought it was because of the Redis server because I upgraded Redis to the latest version two days ago. Then I download the 6.x version and do downgrade Redis just like I upgrade it.

That seems like a stupid downgrade.

Today, all my websites are down and MySQL stopped working because the disk is FULL.

System log files and email log files increased to more than 100GB. But I didn’t know the disk is full immediately, I tried to do something (I don’t remember what I did) with Redis before that.

I tried to remove and reinstall MariaDB server but every time I did the server will try to install Redis

sudo apt-get install mariadb-server
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
mariadb-server is already the newest version (1:10.11.2+maria~deb11).
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y

Setting up redis-server (5:6.0.16-1+deb11u2) ...
Job for redis-server.service failed because the control process exited with error code.
See "systemctl status redis-server.service" and "journalctl -xe" for details.
find: ‘/etc/redis’: No such file or directory
dpkg: error processing package redis-server (--configure):
 installed redis-server package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 redis-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

I completely removed Redis but still can’t install the MariaDB server.

Could you please give me some hints?

It’s urgent because the websites are still down.

Thank you for your time.

2 
systemctl status mariadb.service
● mariadb.service - MariaDB 10.11.2 database server
     Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/mariadb.service.d
             └─migrated-from-my.cnf-settings.conf
     Active: failed (Result: exit-code) since Sat 2023-05-06 15:38:15 UTC; 10s ago
       Docs: man:mariadbd(8)
             https://mariadb.com/kb/en/library/systemd/
    Process: 655354 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
    Process: 655355 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
    Process: 655357 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ]   && syste>
    Process: 655386 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
   Main PID: 655386 (code=exited, status=1/FAILURE)
     Status: "MariaDB server is down"
        CPU: 100ms

May 06 15:38:15 server.example.com mariadbd[655386]: 2023-05-06 15:38:15 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
May 06 15:38:15 server.example.com mariadbd[655386]: 2023-05-06 15:38:15 0 [Note] InnoDB: Starting shutdown...
May 06 15:38:15 server.example.com mariadbd[655386]: 2023-05-06 15:38:15 0 [ERROR] Plugin 'InnoDB' init function returned error.
May 06 15:38:15 server.example.com mariadbd[655386]: 2023-05-06 15:38:15 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
May 06 15:38:15 server.example.com mariadbd[655386]: 2023-05-06 15:38:15 0 [Note] Plugin 'FEEDBACK' is disabled.
May 06 15:38:15 server.example.com mariadbd[655386]: 2023-05-06 15:38:15 0 [ERROR] Unknown/unsupported storage engine: InnoDB
May 06 15:38:15 server.example.com mariadbd[655386]: 2023-05-06 15:38:15 0 [ERROR] Aborting
May 06 15:38:15 server.example.com systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
May 06 15:38:15 server.example.com systemd[1]: mariadb.service: Failed with result 'exit-code'.
May 06 15:38:15 server.example.com systemd[1]: Failed to start MariaDB 10.11.2 database server.
3

I fixed it myself

1 Like
4

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