An email received from Plesk: pum is called with arguments: ['--list', '--repo-info', '--json']

Follow

Comments

6 comments

  • Avatar
    Universe Media

    I get this error every day so this answer is insufficient as it provides NO solution to the notifications and/or error/potential cause of the error.

    2
    Comment actions Permalink
  • Avatar
    Technique

    this is a daily problem that cannot be ignored...

    0
    Comment actions Permalink
  • Avatar
    Dennis Wendt

    As Plesk Support said, it is a problem in underlying system. I also had this for several days and did the following:

    - I logged in via SSH and (since this is an ubuntu system) ran apt-get update to fetch latest update files

    - I noticed that SSH brought up an error with expired GPG keys and therefor threw an error.

    - I googled and fixed the GPG key error and ran the apt-get update again to verify error is fixed

    Hopefully (but I am very sure it will) tomorrow the permanent error is gone.

    2
    Comment actions Permalink
  • Avatar
    Web Services (Edited )

    Thanks, Dennis.

    In case it helps others, my apt update error was caused by this grafana key change mentioned https://grafana.com/blog/2023/01/12/grafana-labs-update-regarding-circleci-security-updates/

    The GPG key used to sign the APT repository (fingerprint 4E40DDF6D76E284A4A6780E48C8C34C524098CB6) was rotated on 2023-01-12 and replaced with a new key with fingerprint 0E22EB88E39E12277A7760AE9E439B102CF3C0C6.

    I also had to add arch=amd64 in the /etc/apt/sources.list.d/grafana.list file to fix a different warning too. 

    0
    Comment actions Permalink
  • Avatar
    Luiz G

    This issue is related to an incorrect GPG key or apt source. Run an apt-get update to seek for errors, correct the source or gpg key and run plesk sbin pum --check again to check if error persists.  

    0
    Comment actions Permalink
  • Avatar
    Rafael Dominguez Rodriguez

    every day since two months!

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request