One of the main reasons that can cause upgrades to fail is “named” (the DNS Bind program), having its permissions changed so it cannot run. Check this and correct as below:
[root@vps16505916 ~]# ls -la /etc/init.d/named
-rwxr-xr-x 1 root root 7478 Jan 7 12:17 /etc/init.d/named
[root@vps16505916 ~]# chmod 755 /etc/init.d/named
Once done, try and run the update process again. This can be done by selecting ‘Updates and Upgrades’ from the ‘panel’ menu that is on the ‘Server’ tab or the Tools & Settings page if you are logged in as full administrator.
Once you select the Upgrade link this will open another tab. On this page select the option to ‘Upgrade the Components’.
If the problem still persists:
A utility of the Parallels Plesk control panel, “bootstrapper.sh” is a SSH command which can repair a failed Plesk upgrade. To begin, change directory into “/usr/local/psa/bootstrapper/” and then run a directory list command:
The directory listing will present you with a list of folders, the number varying between how many upgrades of Plesk have been applied in the past:
drwxr-xr-x 3 root root 4096 Apr 22 2011 pp10.10.1-bootstrapper
drwxr-xr-x 3 root root 4096 Jul 30 20:24 pp10.12.0-bootstrapper
drwxr-xr-x 3 root root 4096 Dec 08 06:39 pp10.13.4-bootstrapper
In this example, the failed upgrade was for Plesk 10.4, so the newest folder “pp10.13.4-bootstrapper” would be used. Change in that directory, and again perform a directory listing:
-rwxr-xr-x 1 root root 269303 Dec 08 05:00 bootstrapper.sh
drwxr-xr-x 3 root root 4096 Dec 08 06:39 db
rw-r–r– 1 root root 2515 Dec 08 04:35 psa.conf.default
The “bootstrapper.sh” file will repair the Plesk databases, and reapply the patches as part of repairing the failed Plesk upgrade. To kick off the repair, simply run the following command:
Wait a few moments while the repair takes place, and once it is done you should be able to log into Plesk with your newest upgrade successfully applied!