• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Project: 100% Manual Upgrades

M

madcat

Guest
Hello. I am interested in figuring out how to update Plesk in a manner that is as manual as possible, and if you search this forum for "updater screwed up AGAIN! :-(" or something similar, you'll see why.

I've recently upgraded a server from 8.3, to 8.4, then to 8.6, and not one of the upgrades was without problems. An example of this is:

Stop running named daemon
Trying to stop service named... done
Trying to untar named run-root directory structure... mknod: `dev/random': File exists
mknod: `dev/urandom': File exists
done
Trying to set up default permissions... chown: cannot access `/var/named/run-root/var/run/named/named.pid': No such file or directory

ERROR while trying to set up default permissions

Aborting...

STOP psa-8.4.0-cos4.build84080425.19 upgrading AT Thu Jul 31 16:03:40 PDT 2008

The problem here is that the file /var/named/run-root/var/run/named/named.pid doesn't exist. This is because I have stopped the nameserver, because DNS for all domains is handled by a different server. What does the installer do? Properly written software would handle this problem gracefully, note the "error" and continue. Instead, this "auto updater" just dies, with the server 1/2 way between 8.3 and 8.4. I managed to fix it by forcefully installing the /tmp/PSA_8.4.0/dist-rpm-CentOS-4.3-x86_64/base/psa-8.4.0-cos4.build84080425.19.x86_64.rpm . It wouldn't do it without "--force" because it thought the RPM was already installed.

I grow tired of this.

For future upgrades, I'd like to download the RPM's from the website and install them manually. I don't want to use the "Update" icon in the control panel, nor do I want to use /usr/local/psa/bin/autoinstaller, as both always have been, and probably always will be broken.

Question: Does anybody know what order to install the RPM's, and if any other commands have to be run to perform an upgrade?

Thanks.
 
Hi,

Question: Does anybody know what order to install the RPM's, and if any other commands have to be run to perform an upgrade?

There should not be a specific order. Just download plesk distributive archive, unpack and install all packages using
rpm -Uvh list_of_all_rpms_from_archive

This will update plesk base packages and all its modules/components. However it may give you some dependency errors and you will need to download packages needed and add them to list of rpms you are updating with rpm -Uvh.
 
Back
Top