Resolved Just had a bumpy ride upgrading from Plesk 17.8.11 to Obsidian 18.0.28

[akira9000]

Hi everyone,

Was just running the updater on the last of my Plesk v17 boxes. CentOS 7.8.2003 8GB RAM 4 cores

The updater failed right at the end with a warning that Plesk may not function. So then noticed that there were additional updates available in the Plesk Updater page which stayed available. Plesk itself turned into some HTML and a huge Facebook F - basically a strange looking webpage with no proper CSS.

Websites have stayed live as far as I can tell. After I ran the additional updates, Plesk came back up with a warning that an update didn't apply correctly but it is showing Obsidian 18.0.28 so maybe it's just confused because of the glitch a few minutes before.

As far as I can tell the system is OK. I have a recent backup for worst case.

Can I run anything in terminal to check system is good? Here is the error message from the main upgrade from 17x to 18x. I guess what I'm saying is I know this is not ideal but should I be concerned?

Error: Cannot open file /var/cache/yum/x86_64/7/base/packages/perl-Error-0.17020-2.el7.noarch.rpm: [Errno 2] No such file or directory: '/var/cache/yum/x86_64/7/base/packages/perl-Error-0.17020-2.el7.noarch.rpm'
TypeError: an integer is required
FATAL ERROR: python callback <bound method RPMTransaction.callback of <yum.rpmtrans.RPMTransaction instance at 0x7f6848494e60>> failed, aborting!
processTransaction event: 10 (Downloading Packages)
processTransaction event: 11 (unknown)
processTransaction event: 20 (Check Package Signatures)
processTransaction event: 30 (Running Test Transaction)
processTransaction event: 40 (Running Transaction)
Bootstrapper has finished action (exec time: 0 sec.): parent_name='PLESK_18_0_28', sequence='pkgs', stage='rollback', sequence_order='1', operation='install', exec_cmd='rm -f /tmp/pp-bootstrapper-mode.flag; rm -f /var/lock/parallels-panel-maintenance-mode.flag; touch /var/lock/parallels-panel-upgrade-failure.flag; :'', m_arch='', output: ~empty
[2020-07-08 18:16:19.079688] Bootstrapper has finished action (exec time: 1 sec.): parent_name='panel', sequence='pkgs', stage='rollback', sequence_order='9999', operation='install', exec_cmd='test ! -f /usr/local/psa/admin/plib/scripts/update-failure-notification.php || /usr/local/psa/admin/bin/php /usr/local/psa/admin/plib/scripts/update-failure-notification.php'', m_arch='', output: ~empty
[2020-07-08 18:16:19.098486] Launching component and product checkers...
[2020-07-08 18:16:19.098534] FileFetcher: get file (~empty)/report-update
[2020-07-08 18:16:19.098661] Downloading file report-update: 0%
[2020-07-08 18:16:19.149871] Downloading file report-update: 100% was finished.
[2020-07-08 18:16:19.150077] FileFetcher: get file (~empty)/pool/PSA_18.0.28_3548/examiners/py_launcher.sh
[2020-07-08 18:16:19.150130] Downloading file pool/PSA_18.0.28_3548/examiners/py_launcher.sh: 0%
[2020-07-08 18:16:19.171292] Downloading file pool/PSA_18.0.28_3548/examiners/py_launcher.sh: 100% was finished.
[2020-07-08 18:16:19.651652] Examination executed ["/root/parallels/pool/PSA_18.0.28_3548/examiners/py_launcher.sh" "/root/parallels/report-update" --op upgrade --rc 1 --start-flag /var/lock/plesk-report-update.flag --to=18.0.28.2 --from=17.8.11] with code 0
 Output:
~empty
 Error:
~empty
[2020-07-08 18:16:19.652691] Execute command /usr/local/psa/admin/bin/send-error-report install --version 18.0.28
[2020-07-08 18:16:19.654616] Warning: Failed to attach to cgroup /sys/fs/cgroup/systemd/user/root/tasks, installer might be unexpectedly killed later by the system
[2020-07-08 18:16:19.674212] Error: The Yum utility failed to install the required packages.
Attention! Your software might be inoperable.
Visit https://support.plesk.com/ to search for a solution.

 

[IgorG]

I'd suggest you reboot the server and then run the upgrade process again with:

# plesk installer

and then come again if there are new errors when upgrading.

 

[Dave W]

Hi Igor,
Same error here:

Updating: plesk-dns-bind-driver-18.0-2.centos.7+p18.0.28.1+t200630.1010.x86_64 [62/134]
Error: Cannot open file /var/cache/yum/x86_64/7/base/packages/perl-Error-0.17020-2.el7.noarch.rpm: [Errno 2] No such file or directory: '/var/cache/yum/x86_64/7/base/packages/perl-Error-0.17020-2.el7.noarch.rpm'
TypeError: an integer is required
FATAL ERROR: python callback <bound method RPMTransaction.callback of <yum.rpmtrans.RPMTransaction instance at 0x7f951a67e5f0>> failed, aborting!

Update:
rebooted and did a

plesk installer update

got:

You already have the latest version of product(s) and all the selected components installed. Installation will not continue.

Dave_W

 

[IgorG]

And what is the output of

# plesk version

?

 

[Dave W]

Hi Igor,

Product version: Plesk Obsidian 18.0.28.2
OS version: CentOS 7.8.2003 x86_64
Build date: 2020/07/03 14:00
Revision: 3e2c0bdf6dc81e82d4bc5d0b128b12fbfbf5b89f

 

[akira9000]

Same here Igor.
Did a yum update too. Terminal said:

There are unfinished transactions remaining. You might consider running yum-complete-transaction first to finish them.
The program yum-complete-transaction is found in the yum-utils package.

I assume this is from the glitch I described at the start of the thread.

So I did exactly that and re-ran yum update. There were a couple of bits inc a firmware release. Machine rebooted no problem afterwards.

 

[akira9000]

email alert from that machine this morning:

Hello, Administrator
Some problems occurred with the System Updates tool on your server xyz.com. Please resolve them manually.

Reason: 2020-07-21 03:11:56 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2020-07-21 03:11:56 ERROR: Previous Plesk installer call finished unsuccessfully. PUM will not perform any update operations until Plesk installation is fixed.
2020-07-21 03:11:56 ERROR: Exited with returncode 50.

 

[akira9000]

So at least a pattern. Have checked the manual updates in Plesk and have been presented with the same ones that wouldn't auto update at the start of this thread. These look like the ones I upgraded manually after the "crash" for Obsidian 18.0.28 but this time it must be the Update #3 batch that's just been released.

 

[akira9000]

This time I am also presented with this alert on the dashboard

 

[IgorG]

This time I am also presented with this alert on the dashboard

And? Have you removed this file?
What about:

# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components

after that?

 

[akira9000]

So to round out this thread, I did actually manage to fix and forgot to post the solution.

I ran into this help article -
To remove duplicate install files

After that, I could re-run the upgrade and all good.