• 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
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Resolved Error Message Package Update Manager notification

hume1991

New 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