Articles in this section

See more

[HUB] Plesk Update Manager (PUM) fails: pum is called with arguments

Avatar
Nelson Leiva
Updated
Follow
Plesk for Linux kb: technical ABT: Group B

Applicable to:

  • Plesk for Linux

Symptoms

Operations involving package installation or update do not perform as expected and results in the error message which can be found in Plesk interface, /var/log/plesk/panel.log or in the server terminal upon running CLI commands. For example:

CONFIG_TEXT: Error: Unable to get packages list: 2017-0101 12:00:00 INFO: pum is called with arguments: ['--list', '--repo-info', '--json'] W: There is no public key available for the following key IDs: EF0F382A1AB66500 MarkUpgrade() called on a non-upgradable pkg: 'dpkg' MarkUpgrade() called on a non-upgradable pkg...

# tail /var/log/plesk/panel.log
ERR [panel] Task failed: id=100, pid=10000, type=pum-update-packages, error=2017-01-01 12:00:00 INFO: pum is called with arguments: ['--update', '--json', '--', 'linux-image-3.16.0-4-amd64', 'linux-libc-dev', ...

# plesk sbin pum --check
INFO: pum is called with arguments: ['--check']
ERROR: Exited with returncode 100. exit status 100

Cause

In general, issues with Plesk Update Manager are caused by the inability of underlying operating system package manager to perform package installation or update.

Troubleshooting

Connect to the server via SSH and run package update manually.

For Debian/Ubuntu:

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

For RHEL/CentOS/CloudLinux:

# yum update -y

Resolution

Correct repository sources or package dependency issues according to the error message displayed upon the attempt to update packages running APT or YUM.

Note: Resolving issues with the operating system installation consistency is an administrative task and should be performed by the system administrator or server owner.

Known Issues

Plesk Update Manager issues can be split into few categories:

Repository misconfiguration or installation sources unavailability:

 

Comments

3 comments

Sort by Date Votes
  • Avatar
    Betafer

    Hello, i got this error from plesk

    Motivo: 2020-07-16 06:25:19 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
    2020-07-16 06:25:21 ERROR: E:The repository 'https://packages.sury.org/php jessie Release' does no longer have a Release file.
    2020-07-16 06:25:21 ERROR: Exited with returncode 1.

    and with

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

    i get

    E: The repository 'https://packages.sury.org/php jessie Release' does no longer have a Release file.
    N: Updating from such a repository can't be done securely, and is therefore disabled by default.
    N: See apt-secure(8) manpage for repository creation and user configuration details.

    How do i exactly fix ?

    Thanks

    0
    Comment actions Permalink
  • Avatar
    Nelson Leiva

    Hello,

    It looks like the repository mentioned in the error is no longer valid or working. Make sure standard default repositories are added to the sources.list. You may refer to the OS vendor documentation for more details about standard repositories required.

    0
    Comment actions Permalink
  • Avatar
    Jorge

    Hello!

    Trying "yum -y update" also results with error:

    http://autoinstall.plesk.com/pool/PSA_18.0.31_4420/extras-rpm-CentOS-7-x86_64/opt/fail2ban/fail2ban-0.10.3.1-2.centos.7%2Bp18.0.32.0%2Bt201026.1619.noarch.rpm: [Errno 14] HTTP Error 404 - Not Found

    Hostname is resolved:

    # host autoinstall.plesk.com
    autoinstall.plesk.com is an alias for 1727842103.rsc.cdn77.org.
    1727842103.rsc.cdn77.org has address 195.181.162.23

     

    What could be the official workaround? 

    Thanks a lot.

     

     

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles