ach das gibt's doch nicht, super anfang fürs neue Jahr, der Server startet wieder nicht mit mysql!!! wieder der selbe Fehler nur jetzt bringt es nicht mal was innoforce zu aktivieren, mysql startet nicht
root@server:/var/lib/mysql# systemctl status mysql.service
â mysql.service - LSB: Start and stop the mysql database server daemon
Loaded: loaded (/etc/init.d/mysql)
Active: failed (Result: exit-code) since Sun 2017-01-01 17:59:31 CET; 2min 56s ago
Process: 5906 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE)
Jan 01 17:59:01 server.dsjo.de mysqld[6201]: InnoDB: 2) If the table is not needed, or you can restore it from a backup,
Jan 01 17:59:01 server.dsjo.de mysqld[6201]: InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
Jan 01 17:59:01 server.dsjo.de mysqld[6201]: InnoDB: crash recovery and ignore that table.
Jan 01 17:59:01 server.dsjo.de mysqld[6201]: InnoDB: 3) If the file system or the disk is broken, and you cannot remove
Jan 01 17:59:01 server.dsjo.de mysqld[6201]: InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
Jan 01 17:59:01 server.dsjo.de mysqld[6201]: InnoDB: and force InnoDB to continue crash recovery here.
Jan 01 17:59:31 server.dsjo.de mysql[5906]: Starting MariaDB database server: mysqld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failed!
Jan 01 17:59:31 server.dsjo.de systemd[1]: mysql.service: control process exited, code=exited status=1
Jan 01 17:59:31 server.dsjo.de systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
Jan 01 17:59:31 server.dsjo.de systemd[1]: Unit mysql.service entered failed state.
in der my.cf ist
innodb_force_recovery=3
innodb_purge_threads=0
eingetragen aber ohne erfolg. Kann doch nicht sein das alle paar Wochen alles kaputt geht....