• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

PUM Failure

trialotto

Golden Pleskian
Plesk Guru
Username:

TITLE

PUM Failure

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Product version: Plesk Obsidian 18.0.51.0
OS version: Ubuntu 18.04 x86_64
Build date: 2023/03/10 16:00
Revision: 7de3d6afacb31f7ca7bdc07684f3b689cb7b0ef6

PROBLEM DESCRIPTION

Plesk Update Manager fails with notification

51003:W: Failed to fetch http://autoinstall.plesk.com/KAV_8.5.1/dists/bionic/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E

and associated email notifications (each day) of the kind

Hello, Administrator
Some problems occurred with the System Updates tool on your server web.plesk.pro. Please resolve them manually.

Reason: 2023-03-31 06:25:35 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2023-03-31 06:25:37 ERROR:
2023-03-31 06:25:37 ERROR: Exited with returncode 1.

STEPS TO REPRODUCE

STR : None

CHECK :
Run commands

1 - plesk sbin pum --check

2 - grep -i -n5 NO_PUBKEY /var/log/plesk/install/autoinstaller3.log

ACTUAL RESULT

COMMAND 1 : plesk sbin pum --check

RESULT :
2023-03-31 06:54:50 INFO: pum is called with arguments: ['--check']
2023-03-31 06:54:51 ERROR:
2023-03-31 06:54:51 ERROR: Exited with returncode 1.
exit status 1

COMMAND 2 : grep -i -n5 NO_PUBKEY /var/log/plesk/install/autoinstaller3.log

RESULT :
....
51003:W: Failed to fetch http://autoinstall.plesk.com/KAV_8.5.1/dists/bionic/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E
51004-W: Some index files failed to download. They have been ignored, or old ones used instead.
.....

EXPECTED RESULT

NA

ANY ADDITIONAL INFORMATION

None

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Have you seen this?
 
Have you seen this?
Dear Peter,

I have seen that thread and, more important, the KB article https://support.plesk.com/hc/en-us/articles/12377139806359

The thing is that it should not occur and, if these issues with keys (or signatures) occur, that Plesk should issue an update immediately.

All things considered, Plesk should work "out of the box".

The most recent update of Plesk 18.0.51 #MU1 does not resolve the issue.

I have just checked, but the Plesk 18.0.49 #MU2 release does not have the issue at all.

In essence, it is a bit surprising that the issue exists ....... and persists.

Kind regards...

PS I am not adding pubkeys for two reasons : (1) it is a principle - Plesk Team should improve this (major/minor) issue ..... and (2) it is handy for testing.
 
@Peter Debik

This is what I mean by "Plesk Team should solve this isse" - it is their dominion and it is SIMPLE.

SOLUTION :

Change contents of file /etc/apt/sources.list.d/plesk-ext-kaspersky-av.list to :

deb [arch=amd64 signed-by=/etc/apt/keyrings/plesk.gpg] Index of /KAV_8.5.1 bionic all

NOTE : thanks to recent (micro-)updates, some other servers were affected in a similar way ......... let me check that too, just give me some minutes.

ADDITION : checked the other (problematic) servers, same solution applies!

Kind regards...

PS Can the automatic http conversion be dropped somehow? the text "Index of /KAV_8.5.1" is not really appropriate, but it will not change....
 
Last edited:
Back
Top