Rescue Plesk after a Failed Update

Please Note:

The text on this page was translated by translation software. A revised version from our editors will be available soon.

For Linux Server with CentOS 6 and Plesk 11

This allows you to restore Plesk after a failed update.

With the following approach, you can reuse Plesk in many cases by restoring a database backup (dump).

Plesk itself performs automatic, regular backups of Plesk databases:

  • Daily dumps created every night when the Plesk statistics tool is run. These dump files are in mysql.daily.dump.1.gz format.
  • Pre-upgrade dumps created during pleskupdate execution. These files are e.g. in the format mysql.preupgrade.dump.gz.1.

Step 1

Log on to your server as root using a shell.

Step 2

First check in which directory the dumps are located. This information can be found in /etc/psa/psa.conf. Usually the dumps should be located in /var/lib/psa/dumps. Change to this directory and display the available dumps:

# cd /var/lib/psa/dumps
[root@s12345678 dumps]# ls -la
total 744drwxr-xr-x 2 psaadm psaadm 4096 Jan 18 03:29 .
drwxr-xr-x 3 root root 4096 Jan 15 16:05 ..
-rw------- 1 root root 187029 Jan 18 03:29 mysql.daily.dump.0.gz
-rw------- 1 root root 186958 Jan 17 03:14 mysql.daily.dump.1.gz
-rw------- 1 root root 191560 Jan 16 03:19 mysql.daily.dump.2.gz
-rw------- 1 root root 181169 Jan 15 17:13 mysql.daily.dump.3.gz
step 3

Unpack the desired dump file using the command gunzip:

# gunzip /var/lib/psa/dumps/mysql.daily.dump.1.gz 
Step 4

Now delete the old, defective database from the directory /etc/psa with DROP DATABASE:

# mysql -uadmin -p`cat /etc/psa/.psa.shadow` -e"DROP DATABASE psa;" 
Step 5

In the last step, restore the psa database from the previously unpacked dump file.

# mysql -f -uadmin -p`cat /etc/psa/.psa.shadow` < /var/lib/psa/dumps/mysql.daily.dump.1 

Please note: The daily database backup (mysql.daily.dump) consists of three different applications:

psa - The actual Plesk
service mysql - The MySQL database
server horde - Horde, a mail server

If you receive an error message such as 'ERROR 1050 at line 3165: Table 'horde_categories' already exists (ERROR 1050 in line 3165: table 'horde_categories' already exists)' after the shell command from step 5, it is necessary to delete this component via DROP DATABASE before the recovery.

Step 6

Then check the availability of Plesk. If this manual has not had the desired effect, we recommend that you visit the Plesk Knowledge Base. Experienced Plesk users may be able to help you in the Plesk forum of software vendor Parallels.

If Plesk could not be started despite all hints, we advise you to reinitialize the server. Since all old data is deleted, we recommend that you make a complete server backup in advance.