Failed Update Problems

[Esisolak]

Hello,

A server with Plesk Panel 10 failed during an update when /root/parallels ran out of space. Our client was performing the update so I do not know what update was being applied (updating to 10.4.4 I believe).

We restored the Plesk DB and applied all 10.3.1 fixes. A second attempt to upgrade was made (once the disk space had been worked out), and this failed as well. This time the problem was that a bootstrapper was apparently already installed (pp10.13.4-bootstrapper), but all of its files were missing. I have removed the package so that it can be installed during the update process, but upgrading to 10.4.4 is no longer listed as an option in the dropdown. Upgrading to 11.0.9 is our ultimate goal, so I tried that, but it fails with being unable to upgrade the license key right away.

I believe the issue stems from the fact that the Plesk install is 10.3.1 but several 10.4.4 packages are installed from partial updates. Also, strangely, the db_version is blank.

How can I complete the upgrade to Panel 11? I posted here since the issues seem to be related to 10.x failures. I did not see any KBs that were relevant to this issue. I have included some information about the packages below, please let me know if you need any other information.

Eric

# cat /usr/local/psa/version
10.3.1 RedHat el5 1013110726.09

# rpm -q psa
psa-10.3.1-rhel5.build1012110718.16

# mysql -uadmin -p`cat /etc/psa/.psa.shadow` -D psa -e 'select * from upgrade_history order by upgrade_date desc limit 1'
+---------------------+---------------------------------+------------+
| upgrade_date | version_info | db_version |
+---------------------+---------------------------------+------------+
| 2012-07-17 15:28:35 | 10.3.1 RedHat el5 1013110726.09 | |
+---------------------+---------------------------------+------------+

From autoinstaller3.log (during attempted 11.x upgrade):
Detecting installed product components.
(update package names cache) Component plesk/base: mode up2date, installed=1320241872, available=1311741321
Component plesk/base have no older version, so keyupdate not needed
Component plesk/psa-autoinstaller: mode up2date, installed=1313132905, available=1313132905
Component plesk/postgresql: mode up2date, installed=1296252827, available=1296252827
Component plesk/pmm: mode up2date, installed=1309348246, available=1309348246
Component plesk/health-monitor: mode install, installed=0, available=1309167176

Installed plesk* packages:
plesk-billing-10.3.0-20110630.04
plesk-l10n-10.12.0-rhel5.build1012110727.11
plesk-billing-plugins-10.12.0-rhel5.build1012110725.16
plesk-base-10.13.4-rhel5.build1013111102.19
plesk-skins-10.12.0-11062815
plesk-core-10.12.0-rhel5.build1012110629.18
plesk-mail-qc-driver-10.12.0-rhel5.build1012110722.14

Installed packages with version 10.13.4 (10.4.4?):
psa-selinux-10.13.4-rhel5.build1013111102.19
psa-pylibplesk-10.13.4-rhel5.build1013111102.19
plesk-base-10.13.4-rhel5.build1013111102.19
psa-mail-driver-common-10.13.4-rhel5.build1013111102.19
psa-locale-base-en-US-10.13.4-rhel5.build1013111102.15

OS ver:
# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.6 (Tikanga)

 

[IgorG]

What sort of error in /tmp/autoinstaller3.log exactly do you have?

 

[Esisolak]

I attached two files. The first is bootstrap-fail.txt and gives some of the output from autoinstaller3.log when the update failed due to the bootstrap issue. The error was:

Starting installation of packages
~empty~emptysh: /usr/local/psa/bootstrapper/pp10.13.4-bootstrapper/bootstrapper.sh: No such file or directory
~empty~emptyExecute command /usr/local/psa/admin/bin/send-error-report install
Error: An error occurred during performing of installation PREP actions (see log for details). Installation was rolled back.
Warning! Not all packages were installed.


The second is from the most recent attempt where it dos not offer the ability to update to 10.4 and updating to 11 give an error about not being able to upgrade the key. No errors were logged, it seems to fail some initial tests, possibly due to the plesk-base version issue.

Thanks
--
Eric

 

[Esisolak]

Any Ideas at all?

Would it be safe to revert plesk-base to an earlier version, if that is even the problem?

--
Eric