Issue pum is call with arguments / stretch Release' does no longer have a Release file

[Précurseur]

Server operating system version

Ubuntu 20.04.6 LTS

Plesk version and microupdate number

Plesk Obsidian Web Host Edition / Version 18.0.51

Hello,
I have two Plesk server:
Plesk Obsidian Web Host Edition / Version 18.0.51
Version Plesk Obsidian v18.0.51_build1800230310.09 os_Ubuntu 20.04
OS Ubuntu 20.04.6 LTS

A few days ago, I started to receive update failure email notification each day:
For the first serveur:

Some problems occurred with the System Updates tool on your server xxx Please resolve them manually.
Reason: 2023-04-02 06:25:52 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2023-04-02 06:25:54 ERROR:
2023-04-02 06:25:54 ERROR: Exited with returncode 1.

And the second:

Some problems occurred with the System Updates tool on your server xxx. Please resolve them manually.
Reason: 2023-03-30 05:53:06 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2023-03-30 05:53:08 ERROR: E:The repository 'http://autoinstall.plesk.com/pool/PSA_18.0.44_9078 stretch Release' does no longer have a Release file.
2023-03-30 05:53:08 ERROR: Exited with returncode 1.

When I go to "Tools & settings > System updates", I have the message:

Error: Unable to get packages list: 2023-04-03 09:02:11 INFO: pum is called with arguments: ['--list', '--repo-info', '--json'] 2023-04-03 09:02:13 ERROR: 2023-04-03 09:02:13 ERROR: Exited with returncode 1.

In the "All packages" tab, I have the same message "Error: Unable to get packages list..." and the package list is empty.

I don't think I have installed or done something special and why these (slightly different) problems appeared all of a sudden on my two servers.
I have seen some similar posts about "pum is call with arguments" but anything that could help me.

Any advice please ?

 

[Peter Debik]

The missing file is from a much older Plesk version, and it is correct that this file is no longer available. The error message does not make much sense when you are on version 18.0.51, unless a previous update of Plesk did not finish properly and some components were not upgraded. I am not sure how to proceed. I would probably first try to find out more about a previously failed update from /var/log/plesk/install/autoinstaller3.log. Afterwards I'd try to run a Plesk update manually on the console (# plesk installer install-panel-updates) to make sure that all vital components are updated to 18.0.51.

 

[Précurseur]

Thank you for your reply Peter. I have no idea what could have gone wrong during a previous update, if something went wrong at all. And we have the same similar error on two distincts servers. We have two quite standard plesk installs and I don't think we've ever played with custom repositories or something like that. I will take a look at what you said, hoping not to break anything.

 

[Peter Claassen]

I'm experiencing exactly the same errors since a few days.
I saw the same error once last year in October. I believe it automatically went away after one occurence.
This time it's persistent.

 

[Peter Claassen]

Errors came after
127.0.0.1 [2023-04-18 14:19:35] 'New patch installed' ('Update version': '18.0.49.2' => '18.0.51.1')

 

[Précurseur]

Hello,
I didn't had the time to investigate yet, but the second error about "stretch Release' does no longer have a Release file" is not relevant anymore. One of our server is indeed outdated (debian 9) and needs an upgrade.
But the "pum is called with arguments" is still there on the other server.

 

[Peter Claassen]

Strange end of autoinstaller3.log as if hanging there?

/var/log/plesk/install# tail autoinstaller3.log
[2023-04-21 06:31:52.101415] Component plesk/xovi: mode up2date, installed_buildtime=0, available_buildtime=0
[2023-04-21 06:31:52.101453] Component plesk/imunifyav: mode up2date, installed_buildtime=0, available_buildtime=0
[2023-04-21 06:31:52.101490] Component plesk/sslit: mode up2date, installed_buildtime=0, available_buildtime=0
[2023-04-21 06:31:52.101528] Component plesk/letsencrypt: mode up2date, installed_buildtime=0, available_buildtime=0
[2023-04-21 06:31:52.101566] Component plesk/repair-kit: mode up2date, installed_buildtime=0, available_buildtime=0
[2023-04-21 06:31:52.101604] Component plesk/composer: mode up2date, installed_buildtime=0, available_buildtime=0
[2023-04-21 06:31:52.101641] Component plesk/monitoring: mode up2date, installed_buildtime=0, available_buildtime=0
[2023-04-21 06:31:52.101678] Component plesk/log-browser: mode up2date, installed_buildtime=0, available_buildtime=0
[2023-04-21 06:31:52.101717] Component plesk/ssh-terminal: mode up2date, installed_buildtime=0, available_buildtime=0
[2023-04-21 06:31:52.101755] Component plesk/site-import: mode error, installed_buildtime=0, available_buildtime=0

 

[LevelupMedia]

We are having first issue also, since we updated to Plesk Version 18.0.51 Update #1


"Some problems occurred with the System Updates tool on your server xxx Please resolve them manually.
Reason: 2023-04-02 06:25:52 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2023-04-02 06:25:54 ERROR:
2023-04-02 06:25:54 ERROR: Exited with returncode 1."

 

[LevelupMedia]

Resolved - NO_PUBKEY BD11A6AA914BDF7E

Hey! I have an issue with package updates. Since couple days I do receive below errors for all repositories: GPG error: http://autoinstall.plesk.com/PHP73_17 buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E W: An...

talk.plesk.com

sudo wget http://autoinstall.plesk.com/plesk.gpg && apt-key add plesk.gpg
sudo apt clean
sudo apt update


This solved it for me.