Issue Problems with system updates

[Sascha Schlüter]

Server operating system version

Debian 10.13

Plesk version and microupdate number

Plesk Obsidian, Version 18.0.51 Update #1

I receive system messages from two of my servers every morning, claiming that there are problems with the system updates. I have had those messages sometimes before, but they used to vanish after a couple of days (e.g. when update ressources were not available temporarily).

This time the problem persists...

The e-mails read like this

Grund: 2023-05-12 06:25:36 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2023-05-12 06:25:37 ERROR:
2023-05-12 06:25:37 ERROR: Exited with returncode 1.

The systems affected are running with Debian 10.13 and Plesk Obsidian, Version 18.0.51 Update #1.

Any help to get these thing right are appreciated.
Thanks in advance!

Sascha

 

[MarkM]

Seen this?

https://support.plesk.com/hc/en-us/articles/12376924311831-An-email-received-from-Plesk-pum-is-called-with-arguments-list-repo-info-json-

 

[Peter Debik]

Rather this maybe?

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: https://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...

talk.plesk.com

 

[Sascha Schlüter]

Seen this?

https://support.plesk.com/hc/en-us/articles/12376924311831-An-email-received-from-Plesk-pum-is-called-with-arguments-list-repo-info-json-

Thanks you this hint, but my issue seems to be different. When I run

plesk sbin pum --check'

I receive

2023-05-12 20:51:26 INFO: pum is called with arguments: ['--check']
2023-05-12 20:51:27 ERROR:
2023-05-12 20:51:27 ERROR: Exited with returncode 1.
exit status 1

 

[MarkM]

# apt-get update && apt-get upgrade -y

Something tells me you might have an issue with a certain repo, which if so - doing a system update would throw that as an error.

 

[Sascha Schlüter]

Rather this maybe?

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: https://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...

talk.plesk.com

Thank you, too. I read through the linked article, but the symptoms mentioned seem to not apply to my problem at all...

 

[Sascha Schlüter]

# apt-get update && apt-get upgrade -y

Something tells me you might have an issue with a certain repo, which if so - doing a system update would throw that as an error.

is the recommended command safe in the sense of "it can't get worse"?