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:
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
In general, issues with Plesk Update Manager are caused by the inability of underlying operating system package manager to perform package installation or update.
Connect to the server via SSH and run package update manually.
# apt-get update && apt-get upgrade -y
# yum update -y
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.
Plesk Update Manager issues can be split into few categories:
Repository misconfiguration or installation sources unavailability:
- Packages update fails: Failed to fetch URL. Some index files failed to download
- Cannot install system updates via Plesk: [Errno 256] No more mirrors to try
- Packages update fails: Failed to fetch URL. Connection failed