• We value your experience with Plesk during 2025
    Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025.
    Please take this short survey:

    https://survey.webpros.com/
  • On Plesk for Linux mod_status is disabled on upgrades to improve Apache security.
    This is a one-time operation that occurs during an upgrade. You can manually enable mod_status later if needed.

Issue ERROR: Apt cache fetch failed.

Looking at log i see i had a problem with an outdated siging key for sury.org repo.
So i executed this command :
Code:
apt-key adv --fetch-keys https://packages.sury.org/php/apt.gpg

I will see tomorrow morning if it solve the problem.
 
If you want to update keys and update + upgrade in one command :
Code:
apt-key adv --fetch-keys https://packages.sury.org/php/apt.gpg && apt update && apt -y upgrade
 
It's seems ok now, but i'm not sure it's because sury signing key update.
There was a plesk update to 18.0.59u2, perhaps they fixed something ...
 
I gave you bad information
the error message this morning was only on one of my VPS
but it wasn't the same error as usual
Raison : 2024-03-06 06:27:05 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2024-03-06 06:27:05 ERROR: Failed to lock directory /var/lib/apt/lists/: E:Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable)
2024-03-06 06:27:05 ERROR: Exited with returncode 1.
so I guess the update also solved my first problem
 
Good morning,
since this weekend, still the messages that have come back
yet we have the latest update
Plesk Obsidian 18.0.59 Update 2 has been installed
if anyone has a solution please
THANKS
Raison : 2024-03-12 06:26:55 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2024-03-12 06:27:26 ERROR: Apt cache fetch failed. Try to run the `apt-get update` command.
2024-03-12 06:27:26 ERROR:
2024-03-12 06:27:26 ERROR: Exited with returncode 1.
 
Hello and thank you for your interest in my problem.

I read your post
but I'm not at Strato
and I have nowhere "pleskupdate" in my files
I did a search with the command: "find / -iname "pleskupdate"
and I found nothing
I went to see "/opt/psa/admin/sbin/pleskupdate" and "/etc/cron.daily/pleskupdate"
and I have nothing
 
I happen to have the same error every other day on several servers.

I checked "/var/log/plesk/install/autoinstaller3.log", but could not see any errors.

Running "apt update" works fine.

Issue - run-parts: /etc/cron.daily/pleskupdate exited with return code 1 does not apply to me, as these servers are root servers, with ordinary
plesk versions installed. There are no customization / relations to Strato or others.

Affected are:

Server1:
Ubuntu 22.04.5 LTS
Product version: Plesk Obsidian 18.0.75.0
OS version: Ubuntu 22.04 x86_64
Build date: 2026/01/02 11:00
Revision: 801e61a105f5d0cc9331ee8f33e76e4c2f4121e9

Server2:
Ubuntu 20.04.6 LTS
Product version: Plesk Obsidian 18.0.75.0
OS version: Ubuntu 20.04 x86_64
Build date: 2026/01/02 11:00
Revision: 801e61a105f5d0cc9331ee8f33e76e4c2f4121e9
 
Do you get the same result when you run apt-get update? If not, what I can suggest as a workaround is to to disable the system updates notification with the following command:

Code:
plesk bin notification --update -code admin_pum_updates -send2email false

What else I can suggest is to changing the time Plesk's daily maintenance task runs. I know that helped users experiencing a similar issue.

On a side note, I would like to add that the case was reviewed by our team (recently as well) and it was not recognized as a Plesk issue - it is suspected to a system related issue.
 
Back
Top