Issue Plesk stuck in 18.0.60

[jorge ceballos]

Server operating system version

AlmaLinux 8.10

Plesk version and microupdate number

Versión 18.0.60

Hi,
Recently migrated from centos 7 to almalinux 8.10 and noticed plesk has not been updated from v 18.0.60 though running v is 18.0.63
When running yum, only a kernel 4.18.0-553.16.1.el8_10 update is shown.
I am missing something but what is it?
Please advice.

TIA

 

[Kaspar@Plesk]

Yum only updates installed packages, not Plesk itself. Are automatic updates enabled for Plesk?

 

[jorge ceballos]

Thanks Kaspar.

System update is checked enabling updates as well as keeping only safe updates.

In my /etc/yum.repos.d there we have the following repos:

almalinux-ha.repo ELevate.repo.rpmsave
almalinux-nfv.repo
epel-modular.repo
almalinux-plus.repo
epel.repo
almalinux-powertools.repo
epel-testing-modular.repo
almalinux.repo
epel-testing.repo
almalinux-resilientstorage.repo mariadb.repo
almalinux-rt.repo mariadb.repo.old_1
almalinux-saphana.repo
plesk-ext-grafana.repo
almalinux-sap.repo
plesk-ext-panel-migrator.repo
BitNinja.repo
plesk-ext-site-import.repo
CentOS-Base.repo.rpmsave
plesk-ext-sophos-av.repo
CentOS-CR.repo.rpmsave plesk.repo
CentOS-fasttrack.repo.rpmsave
tortix-common.repo
CentOS-x86_64-kernel.repo.rpmsave

Which should be active and which not?

Thanks again.

 

[jorge ceballos]

I found the following:
If you’re using Plesk 18.0.60 or earlier, you can run a script to update the repositories:

curl -fsSL https://autoinstall.plesk.com/PSA_18.0.62/examiners/repository_check.sh | bash -s -- update >/dev/null

Does this apply to my current Alma install?

TIA

 

[Kaspar@Plesk]

Does this apply to my current Alma install?

I don't think so. However I might be best to manually update the server to Plesk 18.0.63.

 

[jorge ceballos]

Thanks Kaspar,

Forgot to tell you that if If we run "plesk installer install-all-updates", downloading starts but only refering to v 18.0.60 as follows:

Downloading file products.inf3: 0%
Downloading file products.inf3: 100% was finished.
Downloading file pool/PSA_18.0.60_pr-btb-16771/release.inf3: 0%
Downloading file pool/PSA_18.0.60_pr-btb-16771/release.inf3: 100% was finished.
Downloading file PHP83_17/release.inf3: 0%
Downloading file PHP83_17/release.inf3: 100% was finished.
Downloading file PHP82_17/release.inf3: 0%
Downloading file PHP82_17/release.inf3: 100% was finished.
Downloading file PHP81_17/release.inf3: 0%
Downloading file PHP81_17/release.inf3: 100% was finished.
Downloading file PHP80_17/release.inf3: 0%
Downloading file PHP80_17/release.inf3: 100% was finished.
Downloading file PHP74_17/release.inf3: 0%
Downloading file PHP74_17/release.inf3: 100% was finished.
Checking for installed packages...

... and keeps only to end:

Detecting installed product components.
Last metadata expiration check: 0:00:03 ago on Sun Aug 11 22:45:35 2024.
You already have the latest version of product(s) and all the selected components installed. Installation will not continue.

Seems like upgrade is somewhere specifically pointed to v 18.0.60 not allowing yum nor plesk download newer packages.

Have the impression this comes from the change we had to do in yum when Centos7 support was finished
How can yum update be reset ???

TIA,

 

[Sebahat.hadzhi]

Hello, @jorge ceballos. Could you please attempt the update with the following command instead:

plesk installer --select-release-latest --upgrade-installed-components

Please let us know if the update is still failing and what the output is. Please note that it is always advisable to have an additional backup copy of the server, just to be on the safe side.

 

[jorge ceballos]

thanks for your help.
I tried the update unsuccessfully as follows:

plesk installer --select-release-latest --upgrade-installed-components
Downloading file products.inf3: 0%
Downloading file products.inf3: 100% was finished.
Downloading file pool/PSA_18.0.60_pr-btb-16771/release.inf3: 0%
Downloading file pool/PSA_18.0.60_pr-btb-16771/release.inf3: 100% was finished.
Downloading file PHP83_17/release.inf3: 0%
Downloading file PHP83_17/release.inf3: 100% was finished.
Downloading file PHP82_17/release.inf3: 0%
Downloading file PHP82_17/release.inf3: 100% was finished.
Downloading file PHP81_17/release.inf3: 0%
Downloading file PHP81_17/release.inf3: 100% was finished.
Downloading file PHP80_17/release.inf3: 0%
Downloading file PHP80_17/release.inf3: 100% was finished.
Downloading file PHP74_17/release.inf3: 0%
Downloading file PHP74_17/release.inf3: 100% was finished.
Checking for installed packages...
Downloading file pool/PSA_18.0.60_pr-btb-16771/plesk-18.0.60-rhel8-x86_64.inf3: 0%
Downloading file pool/PSA_18.0.60_pr-btb-16771/plesk-18.0.60-rhel8-x86_64.inf3: 100% was finished.
Downloading file PHP74_17/php74-rhel8-x86_64.inf3: 0%
Downloading file PHP74_17/php74-rhel8-x86_64.inf3: 100% was finished.
Downloading file PHP80_17/php80-rhel8-x86_64.inf3: 0%
Downloading file PHP80_17/php80-rhel8-x86_64.inf3: 100% was finished.
Downloading file PHP81_17/php81-rhel8-x86_64.inf3: 0%
Downloading file PHP81_17/php81-rhel8-x86_64.inf3: 100% was finished.
Downloading file PHP82_17/php82-rhel8-x86_64.inf3: 0%
Downloading file PHP82_17/php82-rhel8-x86_64.inf3: 100% was finished.
Downloading file PHP83_17/php83-rhel8-x86_64.inf3: 0%
Downloading file PHP83_17/php83-rhel8-x86_64.inf3: 100% was finished.
gpg-pubkey-e3c94f49-54930db0 gpg(MariaDB Enterprise Signing Key <[email protected]>)
gpg-pubkey-f4a80eb5-53a7ff4b gpg(CentOS-7 Key (CentOS 7 Official Signing Key) <[email protected]>)
gpg-pubkey-352c64e5-52ae6884 gpg(Fedora EPEL (7) <[email protected]>)
gpg-pubkey-2c52609d-55a59f6e gpg(Docker Release Tool (releasedocker) <[email protected]>)
gpg-pubkey-10458545-64e78669 gpg(Grafana Labs <[email protected]>)
gpg-pubkey-c74cd1d8-56fc10ab gpg(MariaDB Signing Key <[email protected]>)
gpg-pubkey-81b961a5-64106f70 gpg(ELevate <[email protected]>)
gpg-pubkey-4520afa9-50ab914c gpg(Atomicorp (Atomicorp Official Signing Key) <[email protected]>)
gpg-pubkey-621e9f35-58adea78 gpg(Docker Release (CE rpm) <[email protected]>)
gpg-pubkey-1bb943db-511147a9 gpg(MariaDB Package Signing Key <[email protected]>)
gpg-pubkey-28c12247-59e4bf5a gpg(MariaDB Maxscale <[email protected]>)
gpg-pubkey-914bdf7e-55c05220 gpg(Plesk Team <[email protected]>)
Start downloading 1 files of unknown size and 0 delta RPMs
Download PLESK_18_0_60 extras 3089B [total 0/unknown B 1/1 files]
Start downloading 1 files of unknown size and 0 delta RPMs
Download PHP 7.4 3081B [total 0/unknown B 1/1 files]
Start downloading 1 files of unknown size and 0 delta RPMs
Download PHP 8.0 3080B [total 0/unknown B 1/1 files]
Start downloading 1 files of unknown size and 0 delta RPMs
Download PHP 8.1 3081B [total 0/unknown B 1/1 files]
Start downloading 1 files of unknown size and 0 delta RPMs
Download PHP 8.2 3081B [total 0/unknown B 1/1 files]
Start downloading 1 files of unknown size and 0 delta RPMs
Download PHP 8.3 3081B [total 0/unknown B 1/1 files]
Detecting installed product components.
Last metadata expiration check: 0:00:03 ago on Mon Aug 12 11:18:26 2024.
You already have the latest version of product(s) and all the selected components installed. Installation will not continue.

Please advice,

TIA
Regards

 

[Kaspar@Plesk]

What's the output of grep SOURCE /root/.autoinstallerrc and cat /etc/yum.repos.d/plesk.repo?

 

[jorge ceballos]

Hi Kaspar,

grep SOURCE /root/.autoinstallerrc
# SOURCE value is locked by plesk-installer script
SOURCE = http://autoinstall.plesk.com/plesk-php8.3

cat /etc/yum.repos.d/plesk.repo
## Persistent repositories for Plesk Products.

[PLESK_18_0_60-extras]
name=PLESK_18_0_60 extras
baseurl=http://autoinstall.plesk.com/plesk-...60_pr-btb-16771/extras-rpm-RedHat-el8-x86_64/
enabled=1
gpgcheck=1

[PLESK_17_PHP74]
name=PHP 7.4
baseurl=http://autoinstall.plesk.com/plesk-php8.3/PHP74_17/dist-rpm-RedHat-el8-x86_64/
enabled=1
gpgcheck=1

[PLESK_17_PHP80]
name=PHP 8.0
baseurl=http://autoinstall.plesk.com/plesk-php8.3/PHP80_17/dist-rpm-RedHat-el8-x86_64/
enabled=1
gpgcheck=1

[PLESK_17_PHP81]
name=PHP 8.1
baseurl=http://autoinstall.plesk.com/plesk-php8.3/PHP81_17/dist-rpm-RedHat-el8-x86_64/
enabled=1
gpgcheck=1

[PLESK_17_PHP82]
name=PHP 8.2
baseurl=http://autoinstall.plesk.com/plesk-php8.3/PHP82_17/dist-rpm-RedHat-el8-x86_64/
enabled=1
gpgcheck=1

[PLESK_17_PHP83]
name=PHP 8.3
baseurl=http://autoinstall.plesk.com/plesk-php8.3/PHP83_17/dist-rpm-RedHat-el8-x86_64/
enabled=1
gpgcheck=1

Thanks for your help,

Regards

 

[Kaspar@Plesk]

This line SOURCE = http://autoinstall.plesk.com/plesk-php8.3 in your /root/.autoinstallerrc file indicates that an earlier Plesk version was updated with experimental PHP 8.3 support. This is likely prohibiting you from upgrading.

Before you make any changes make sure to make a backup. You can try to use the following steps to solve the issue.

1. Comment out the SOURCE = http://autoinstall.plesk.com/plesk-php8.3 in /root/.autoinstallerrc by adding # sign in front of it
2. Run plesk installer --skip-cleanup to make autoinstaller not remove any Plesk repositories
3. In /etc/yum.repos.d/plesk.repochange this line
   

   baseurl=http://autoinstall.plesk.com/plesk-php8.3/pool/PSA_18.0.60_pr-btb-16771/extras-rpm-RedHat-el8-x86_64/

   with
   

   baseurl=http://autoinstall.plesk.com/pool/PSA_18.0.60_14384/extras-rpm-RedHat-el8-x86_64/

4. Run plesk installer install-all-updates again
   

 

[jorge ceballos]

This line SOURCE = [URL]http://autoinstall.plesk.com/plesk-php8.3[/URL] in your /root/.autoinstallerrc file indicates that an earlier Plesk version was updated with experimental PHP 8.3 support. This is likely prohibiting you from upgrading.

Before you make any changes make sure to make a backup. You can try to use the following steps to solve the issue.

1. Comment out the SOURCE = http://autoinstall.plesk.com/plesk-php8.3 in /root/.autoinstallerrc by adding # sign in front of it
2. Run plesk installer --skip-cleanup to make autoinstaller not remove any Plesk repositories
3. In /etc/yum.repos.d/plesk.repochange this line
   

   baseurl=http://autoinstall.plesk.com/plesk-php8.3/pool/PSA_18.0.60_pr-btb-16771/extras-rpm-RedHat-el8-x86_64/

   with
   

   baseurl=http://autoinstall.plesk.com/pool/PSA_18.0.60_14384/extras-rpm-RedHat-el8-x86_64/

4. Run plesk installer install-all-updates again
   

Thanks Kaspar,

Did as instructed and when running point 2 it came to a stop asking if I wanted to upgrade or install/uninstall Plesk packages. Choose upgrade and started downloading packages until it stopped again and asked if I wanted to install 24 or so needed packages as Plesk had only one which would be removed. I quitted on the spot and went to point 3 and 4.
Updates were installed successfully - or so says CLI - with the following message:


Warning: execute post install/upgrade actions

***** problem report *****
Warning: execute post install/upgrade actions
/usr/bin/sw-engine: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /lib64/libaps.so.1)
/usr/bin/sw-engine: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /lib64/liblock_manager.so.2)
/usr/bin/sw-engine: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /usr/lib64/sw/librdbmspp.so.2)
/usr/bin/sw-engine: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /usr/lib64/libboost-plesk-1.84/libboost_program_options-plesk.so.1.84.0)
Launching component and product checkers...
Downloading file report-update: 0%
Downloading file report-update: 100% was finished.
Downloading file pool/PSA_18.0.60_14384/examiners/py_launcher.sh: 0%
Downloading file pool/PSA_18.0.60_14384/examiners/py_launcher.sh: 100% was finished.

The changes were applied successfully.

In the control panel, version shown now is 18.0.60 Update 1 .... so, it moved a step ahead.

Will try the following updates and keep you posted.

Thanks again,
Regards

 

[jorge ceballos]

Well, Plesk panel control update now shows 18.0.63 as the current version.

Clicked to update and it came to a stop showing:

Plesk license key availability check
/usr/bin/sw-engine: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /lib64/libaps.so.1)
/usr/bin/sw-engine: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /lib64/liblock_manager.so.2)
/usr/bin/sw-engine: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /usr/lib64/sw/librdbmspp.so.2)
/usr/bin/sw-engine: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /usr/lib64/libboost-plesk-1.84/libboost_program_options-plesk.so.1.84.0)
Plesk pre-upgrade check
/usr/bin/sw-engine: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /lib64/libaps.so.1)
/usr/bin/sw-engine: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /lib64/liblock_manager.so.2)
/usr/bin/sw-engine: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /usr/lib64/sw/librdbmspp.so.2)
/usr/bin/sw-engine: /usr/lib64/c++-plesk-12.2.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /usr/lib64/libboost-plesk-1.84/libboost_program_options-plesk.so.1.84.0)

And a warning sign saying that proceeding with the update without solving this incidents may harm server's data.

Is it sound to update the libstdc++ using yum?

Please advice and many thanks again for your help

Regards,

 

[Kaspar@Plesk]

I suggest opening a ticket with our support team for an investigation of the issue. To sign-in to support and open a ticket go to https://support.plesk.com.

If you got your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative to get support directly from Plesk: https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk

 

[jorge ceballos]

I suggest opening a ticket with our support team for an investigation of the issue. To sign-in to support and open a ticket go to Plesk.

If you got your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative to get support directly from Plesk: How to get support directly from Plesk?

Thanks Kaspar,

Just sent my request ticket and searching a bit more, found that this may be caused by an interrupted update; came to my mind that when did "plesk installer --skip-cleanup" it started the installer and I interrupted it when asked if I wanted to remove the installed Plesk package.

We'll wait for the ticket resolution and let you know.

Thanks again,
Regards