Issue Problem when restoring a virtual machine with Plesk Obsidian.

[Johnny94]

Server operating system version

Ubuntu 20

Plesk version and microupdate number

Plesk Obsidian

Hello. We installed Plesk Obsidian in a virtual machine on Ubuntu 20. I configured all the parameters as I needed. Works great.

Now faced with a problem when backing up a virtual machine with Plesk and then restoring this image Plesk does not work. In my opinion, some Plesk files are corrupted.

My server is configured so that every week it backs up all my virtual machines to a separate storage system. All other virtual machines and services located in it are restored without errors. But it is Plesk that stops working after restoring from a backup.

Please help me to sort out this problem. I am attaching a screenshot of the error.

 

[Maarten]

The error means that the database server isn't running:

What's the output of this command?

# systemctl status mariadb.service

 

[Johnny94]

The error means that the database server isn't running:

What's the output of this command?

# systemctl status mariadb.service

mariadb.service - MariaDB 10.6.7 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2022-07-16 04:21:26 UTC; 3s ago
Docs: man:mariadbd(8)
systemd
Process: 414131 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Process: 414132 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 414134 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 exit 1 (code=exited, st>
Process: 414172 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
Main PID: 414172 (code=exited, status=1/FAILURE)
Status: "MariaDB server is down"
CPU: 143ms

Jul 16 04:21:26 ns1.regme.uz mariadbd[414172]: 2022-07-16 4:21:26 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
Jul 16 04:21:26 ns1.regme.uz mariadbd[414172]: 2022-07-16 4:21:26 0 [Note] InnoDB: Starting shutdown...
Jul 16 04:21:26 ns1.regme.uz mariadbd[414172]: 2022-07-16 4:21:26 0 [ERROR] Plugin 'InnoDB' init function returned error.
Jul 16 04:21:26 ns1.regme.uz mariadbd[414172]: 2022-07-16 4:21:26 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Jul 16 04:21:26 ns1.regme.uz mariadbd[414172]: 2022-07-16 4:21:26 0 [Note] Plugin 'FEEDBACK' is disabled.
Jul 16 04:21:26 ns1.regme.uz mariadbd[414172]: 2022-07-16 4:21:26 0 [ERROR] Unknown/unsupported storage engine: InnoDB
Jul 16 04:21:26 ns1.regme.uz mariadbd[414172]: 2022-07-16 4:21:26 0 [ERROR] Aborting
Jul 16 04:21:26 ns1.regme.uz systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jul 16 04:21:26 ns1.regme.uz systemd[1]: mariadb.service: Failed with result 'exit-code'.
Jul 16 04:21:26 ns1.regme.uz systemd[1]: Failed to start MariaDB 10.6.7 database server.

 

[WebHostingAce]

While the backup or restoring.. Your database on this server has been corrupted.

https://support.plesk.com/hc/en-us/articles/213939865-How-to-fix-InnoDB-corruption-cases-for-the-MySQL-databases-on-Plesk-for-Linux-

Read the instructions carefully. Also the Plesk support might be able to help you.