• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Resolved Error Message Package Update Manager notification

hume1991

Basic Pleskian
I received the following email from my server:

Please resolve them manually.

Reason: 2017-06-02 00:04:22 INFO: pum is called with arguments: ['--update', '--json']
2017-06-02 00:04:30 INFO: updating packages: isc-dhcp-common libldap-2.4-2 ldap-utils isc-dhcp-client libpq5
2017-06-02 00:04:30 ERROR: Failed to fetch http://ubuntu.mirror.serverloft.de/...p/ldap-utils_2.4.31-1+nmu2ubuntu8.4_amd64.deb 404 Not Found
Failed to fetch http://ubuntu.mirror.serverloft.de/...ibldap-2.4-2_2.4.31-1+nmu2ubuntu8.4_amd64.deb 404 Not Found
Failed to fetch http://ubuntu.mirror.serverloft.de/.../isc-dhcp-client_4.2.4-7ubuntu12.10_amd64.deb 404 Not Found
Failed to fetch http://ubuntu.mirror.serverloft.de/.../isc-dhcp-common_4.2.4-7ubuntu12.10_amd64.deb 404 Not Found
Failed to fetch http://ubuntu.mirror.serverloft.de/...ql-9.3/libpq5_9.3.17-0ubuntu0.14.04_amd64.deb 404 Not Found

2017-06-02 00:04:30 ERROR: Exited with returncode 1.

What does this message mean? Was the update server unavailable? Other problems?
 
Hi hume1991,

your issue is caused by a mirror failure from "ubuntu.mirror.serverloft.de", which should be "normally" corrected during the next few hours or the next day. Just ignore it for the moment and wait for the next scheduled update/upgrade, or try the command
Code:
aptitude upgrade
over the command line ( logged in as user "root" over SSH ). If you experience such an issue, just try the upgrade a few hours later again, untill you succeed. ;)

Apart from that, you issue is absolutely not "Plesk - related" and such a thread should be posted at: => Home >Forum > General Discussion > Open Topics
 
Back
Top