Plesk

InnoDB corruption occurs in MariaDB on Plesk server after reboot: Unspecified GSS failure

Symptoms

Cause

MariaDB bug MDEV-18298 or its consequences.

Resolution

Check if the InnoDB engine has already been corrupted using the symptoms from the article How to fix InnoDB corruption cases for the MySQL/MariaDB databases on Plesk for Linux? and apply one of the following solutions:

If InnoDB is corrupted

  1. Log in to Plesk server via SSH.

  2. Create Plesk database backup

  3. List all available Plesk daily database dumps sorted by the date:

    # ls -lt /var/lib/psa/dumps/mysql.daily.*
    -rw------- 1 root root 236253 Feb 3 01:51 mysql.daily.dump.0.gz
    -rw------- 1 root root 229653 Feb 2 01:48 mysql.daily.dump.1.gz
    -rw------- 1 root root 222485 Feb 1 01:56 mysql.daily.dump.2.gz

    Note: where mysql.daily.dump.0.gz is the most recent daily database dump.

  4. Navigate to the directory /var/lib/psa/dumps/:

    # cd /var/lib/psa/dumps/

  5. Restore the psa database from the most recent daily dump:

    # zcat mysql.daily.dump.0.gz | sed -n '/-- Current Database: psa/,/-- Current Database:*/p' | MYSQL_PWD=cat /etc/psa/.psa.shadow mysql -uadmin

  6. Disable GSSAPI plugin by commenting it out in /etc/my.cnf.d/auth_gssapi.cnf. Use any comfortable text editor, e.g. Vi:

    #plugin-load-add=auth_gssapi.so

  7. Restart MariaDB:

    # service mariadb restart

If InnoDB is not corrupted

  1. Log in to Plesk server via SSH.

  2. Disable GSSAPI plugin by commenting it out in /etc/my.cnf.d/auth_gssapi.cnf. Use any comfortable text editor, e.g. Vi:

    #plugin-load-add=auth_gssapi.so

  3. Restart MariaDB:

    # service mariadb restart

 

 

Exit mobile version