MySQL / MariaDB startet nach update nicht mehr

[Mebus]

Hallo,

leider Startet mein MySQL / MariaDB auf einem Server nach einem Update nicht mehr:

cat /var/log/mysql/error.log | tail -n 1000: https://termbin.com/2qd4

Und noch ein paar Infos:

Code: Alles auswählen

# dpkg -l | grep mariadb
ii  libmariadb3:amd64                        1:10.3.23-0+deb10u1                                            amd64        MariaDB database client library
rc  mariadb-client-10.1                      10.1.44-0+deb9u1                                               amd64        MariaDB database client binaries
ii  mariadb-client-10.3                      1:10.3.23-0+deb10u1                                            amd64        MariaDB database client binaries
ii  mariadb-client-core-10.3                 1:10.3.23-0+deb10u1                                            amd64        MariaDB database core client binaries
ii  mariadb-common                           1:10.3.23-0+deb10u1                                            all          MariaDB common metapackage
ii  mariadb-server                           1:10.3.23-0+deb10u1                                            all          MariaDB database server (metapackage depending on the latest version)
rc  mariadb-server-10.1                      10.1.44-0+deb9u1                                               amd64        MariaDB database server binaries
ii  mariadb-server-10.3                      1:10.3.23-0+deb10u1                                            amd64        MariaDB database server binaries
ii  mariadb-server-core-10.3                 1:10.3.23-0+deb10u1                                            amd64        MariaDB database core server files

Code: Alles auswählen

# systemctl status mariadb                                                                                                                                             :(
● mariadb.service - MariaDB 10.3.23 database server
   Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: signal) since Sun 2020-08-09 15:46:37 CEST; 3s ago
     Docs: man:mysqld(8)
           https://mariadb.com/kb/en/library/systemd/
  Process: 32077 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
  Process: 32078 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
  Process: 32079 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || ex
  Process: 32178 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=killed, signal=ABRT)
  Process: 32209 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
  Process: 32210 ExecStartPost=/etc/mysql/debian-start (code=exited, status=0/SUCCESS)
 Main PID: 32178 (code=killed, signal=ABRT)
   Status: "Taking your SQL requests now..."

Hat jemand eine Idee, wie ich das reparieren kann?

Mebus

[Mebus]

Tach,

so, nachdem ich jetzt in

/etc/mysql/my.conf

Code: Alles auswählen

[mysqld]
innodb_force_recovery=4

eingefügt hatte, startet MariaDB wieder.

Siehe: https://dev.mysql.com/doc/refman/8.0/en ... overy.html

Mebus

[Mebus]

Jetzt ist es wieder kaputt gegangen :-O

https://termbin.com/u4om

Warum passiert das?

Wenn ich jetzt mit innodb_force_recovery=6 starte, bekomme ich das:

Code: Alles auswählen

2020-08-09 18:25:01 171 [ERROR] InnoDB: Failed to find tablespace for table `librenms`.`devices_attribs` in the cache. Attempting to load the tablespace with space id 143
2020-08-09 18:25:01 175 [ERROR] InnoDB: Failed to find tablespace for table `librenms`.`device_perf` in the cache. Attempting to load the tablespace with space id 328
2020-08-09 18:25:01 175 [ERROR] InnoDB: Failed to find tablespace for table `librenms`.`alert_schedule` in the cache. Attempting to load the tablespace with space id 124
2020-08-09 18:25:01 175 [ERROR] InnoDB: Failed to find tablespace for table `librenms`.`alert_schedule_items` in the cache. Attempting to load the tablespace with space id 125
2020-08-09 18:25:01 175 [ERROR] InnoDB: Failed to find tablespace for table `librenms`.`alert_device_map` in the cache. Attempting to load the tablespace with space id 253
....

und die Nextcloud kann die Datenbank nicht richtig benutzen.

Mebus