Resolved Plesk System Updater Not Working

[Aaron2020]

I seem to have been experiencing issues with the system updater on the server since the 1st of December 2020.

The server will not pull in any Plesk updates or package updates whatsoever. Initially the error was only displayed with the following message in the GUI "Error: Unable to receive update information for the package(s)". After assigning my email address in the GUI I was able to receive a more detailed message regarding the error. I've pasted this message below:

"Hello,
Some problems occurred with the System Updates tool on your server pumasolutions.co.uk. Please resolve them manually.

Reason: 2021-02-09 03:22:32 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2021-02-09 03:22:32 ERROR: Cannot retrieve repository metadata (repomd.xml) for repository: base. Please verify its path and try again
2021-02-09 03:22:32 ERROR: Exited with returncode 1."

As we currently can't update our systems either I thought it would be best to include current versions below:

Plesk Obsidian: Version 18.0.31 Update #2, last updated on Dec 1, 2020 03:46 AM
Cent OS: 6.10 (Final)

My experience with servers is unfortunately incredibly limited, but I have also tried logging via SSH and running the command "yum update -y". Unfortunately this didn't have the desired effect of magically helping!

 

[IgorG]

The problem is caused by fact that CentOS 6 reached its end-of-life on November 30th, 2020.
More details you can find here: After November 30th, 2020, updating system packages on Plesk server with CentOS 6 fails: Cannot find a valid baseurl for repo: base

 

[Aaron2020]

Thank you for your quick response, I've contacted the company we rent the server from and will be looking at upgrading the OS.

Possibly a bit of a stupid question to ask but do you reckon upgrading to CentOS 7 would be the best move from here or is there another OS that would be better suited with respects to longevity?

 

[IgorG]

Plesk does not support CentOS distupgrade.
In my opinion, migration is the best way. You can migrate not necessarily to CentOS, but also to Ubuntu or Debian if you think this is the best choice.

 

[Aaron2020]

I've had a chat with the company that we rent the server from, they've given us two options at the moment.

The first option they've offered being a server rebuild with CentOS 7 as the base OS and then restoring our server from a Plesk backup.

I've had a chat with the company regarding migration and the second option they've offered being to rent out a new server with CentOS 7, Ubuntu or Debian as the base OS and then using the Plesk Migration Extension Tool to pull over all of the data and configurations from our current server.

Definitely agree that migration would be the best option, certainly want to try and mitigate any down time that our customers would have to deal with as we swap over to a different server. Thank you very much for your help in this matter, it is greatly appreciated!

 

[MarianV]

Hi everyone.

I have been suffering exactly the same situation, however, my server OS is Debian, not CentOS.

• OS: ‪Debian 8.11‬
• Product: Plesk Obsidian 18.0.28 Update #3 , last updated at Sept 1, 2020 12:28 PM

Message :
Hello, Administrator
Some problems occurred with the System Updates tool on your server xxx.xx. Please resolve them manually.

Reason: 2021-08-03 06:25:19 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2021-08-03 06:25:39 ERROR: W:Failed to fetch http://autoinstall.plesk.com/pool/PSA_18.0.28_3654/dists/jessie/extras/binary-amd64/Packages 404 Not Found [IP: 185.93.2.16 80]
, W:Failed to fetch http://autoinstall.plesk.com/pool/PSA_18.0.28_3654/dists/jessie/extras/binary-i386/Packages 404 Not Found [IP: 185.93.2.16 80]
, E:Some index files failed to download. They have been ignored, or old ones used instead.
2021-08-03 06:25:39 ERROR: Exited with returncode 1.

Please help

 

[IgorG]

Hi everyone.

I have been suffering exactly the same situation, however, my server OS is Debian, not CentOS.

• OS: ‪Debian 8.11‬
• Product: Plesk Obsidian 18.0.28 Update #3 , last updated at Sept 1, 2020 12:28 PM

Message :
Hello, Administrator
Some problems occurred with the System Updates tool on your server xxx.xx. Please resolve them manually.

Reason: 2021-08-03 06:25:19 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2021-08-03 06:25:39 ERROR: W:Failed to fetch http://autoinstall.plesk.com/pool/PSA_18.0.28_3654/dists/jessie/extras/binary-amd64/Packages 404 Not Found [IP: 185.93.2.16 80]
, W:Failed to fetch http://autoinstall.plesk.com/pool/PSA_18.0.28_3654/dists/jessie/extras/binary-i386/Packages 404 Not Found [IP: 185.93.2.16 80]
, E:Some index files failed to download. They have been ignored, or old ones used instead.
2021-08-03 06:25:39 ERROR: Exited with returncode 1.

Please help

Try to fix it with

# plesk installer --select-release-id PLESK_18_0_28 --upgrade-installed-components

 

[MarianV]

First, apologies for replying late, I only did not see the instruction before. Clumsy I know, but that is what happened.
I have just tried the solution but it did not work. You will have noticed I am not too familiar with Plesk, even so, I do not understand why the information in my dashboard should be wrong. I case you think of another solution, I shall be most grateful if you can help.

When I try to fix with
# plesk installer --select-release-id PLESK_18_0_28 --upgrade-installed-components


the message I get is

ERROR: There is no product with ID '<default=plesk>' at the installation source.
Run Plesk Installer with the --show-releases option or the 'list' command to get the list of products and their latest releases available for installation. Use the --show-all-releases option or the 'list-all' command to get the list of all products and their releases from the installation source.


and when I run
plesk installer --show-all-releases

I see no sign of 18_0_28 displayed on the dashboard, but I get

prod_id release_id (description) (tiers) ---
plesk PLESK_18_0_37 (Plesk Obsidian 18.0.37) (development,testing,release,stable,current)
plesk PLESK_18_0_36 (Plesk Obsidian 18.0.36) (development,testing,release,stable,current)
plesk PLESK_18_0_35 (Plesk Obsidian 18.0.35) (development,testing,release,stable,current)
plesk PLESK_18_0_34 (Plesk Obsidian 18.0.34) (development,testing,release,stable,current)
plesk PLESK_18_0_33 (Plesk Obsidian 18.0.33) (development,testing,release,stable,current)
plesk PLESK_18_0_32 (Plesk Obsidian 18.0.32) (development,testing,release,stable,current)
plesk PLESK_18_0_31 (Plesk Obsidian 18.0.31) (development,testing,release,stable,current)
plesk PLESK_17_8_11 (Plesk Onyx 17.8.11) (development,testing,release,stable,current)
plesk PLESK_17_5_3 (Plesk Onyx 17.5.3) (testing,stable,current,release)
plesk PLESK_17_0_17 (Plesk Onyx 17.0.17) (testing,stable,current,release)
plesk PLESK_12_5_30 (Plesk 12.5.30) (release,current,testing,stable)
plesk PLESK_12_0_18 (Plesk 12.0.18) (release,current,testing,stable)
plesk PLESK_11_5_30 (Parallels Plesk Panel 11.5.30) (stable,current,release)
plesk PLESK_11_0_9 (Parallels Plesk Panel 11.0.9) (stable)
plesk PLESK_10_4_4 (Parallels Plesk Panel 10.4.4) (stable)
plesk PLESK_10_3_1 (Parallels Plesk Panel 10.3.1) (stable)
plesk PLESK_10_3_0 (Parallels Plesk Panel 10.3.0) (stable)
plesk PLESK_10_2_0 (Parallels Plesk Panel 10.2.0) (stable)
plesk PLESK_10_1_1 (Parallels Plesk Panel 10.1.1) (stable)
plesk PLESK_10_1_0 (Parallels Plesk Panel 10.1.0) (stable)
plesk PLESK_10_0_1 (Parallels Plesk Panel 10.0.1) (stable)
plesk PLESK_10_0_0 (Parallels Plesk Panel 10.0.0) (stable)
plesk PLESK_9_5_4 (Parallels Plesk Panel 9.5.4) (stable)
plesk PLESK_9_5_3 (Parallels Plesk Panel 9.5.3) (stable)
plesk PLESK_9_5_2 (Parallels Plesk Panel 9.5.2) (stable)
plesk PLESK_9_5_1 (Parallels Plesk Panel 9.5.1) (stable)
plesk PLESK_9_5_0 (Parallels Plesk Panel 9.5.0) (stable)
plesk PLESK_9_3_0 (Parallels Plesk Panel 9.3.0) (stable)
plesk PLESK_9_2_3 (Parallels Plesk Panel 9.2.3) (stable)
plesk PLESK_9_2_2 (Parallels Plesk Panel 9.2.2) (stable)
plesk PLESK_9_2_1 (Parallels Plesk Panel 9.2.1) (stable)
plesk PLESK_9_2_0 (Parallels Plesk Panel 9.2.0) (stable)
plesk PLESK_9_0_1 (Parallels Plesk Panel 9.0.1) (stable)
plesk PLESK_9_0_0 (Parallels Plesk Panel 9.0.0) (stable)
plesk PLESK_8_6_0 (Plesk 8.6.0) (stable)
plesk PLESK_8_4_1 (Plesk 8.4.1) (stable)
plesk PLESK_8_4_0 (Plesk 8.4.0) (stable)
plesk PLESK_8_3_0 (Plesk 8.3.0) (stable)
plesk PLESK_8_2_1 (Plesk 8.2.1) (stable)
plesk PLESK_8_2_0 (Plesk 8.2.0) (stable)
plesk PLESK_8_1_1 (Plesk 8.1.1) (stable)
plesk PLESK_8_1_0 (Plesk 8.1.0) (stable)
plesk PLESK_8_0_1 (Plesk 8.0.1) (stable)
plesk PLESK_8_0_0 (Plesk 8.0.0) (stable)
plesk PLESK_7_5_4 (Plesk 7.5.4) (stable)
plesk PLESK_7_1_7 (Plesk 7.1.7) (stable)

 

[MarianV]

cat /usr/local/psa/version
18.0.28 Debian 8.0 1800200720.10

plesk version | grep "Product version"
Product version: Plesk Obsidian 18.0.28.3

 

[IgorG]

Debian 8.0

This version of Debian is not supported: Software Requirements for Plesk Obsidian
That's why you can't upgrade.
Consider dist-upgrading your OS or migrate to a new server with one of the currently supported Operating Systems as per the following list.

 

[MarianV]

I see, will upgrade. Thank you very much hor your help.
Marian