• 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

Issue ERROR: Apt cache fetch failed.

N

nMLxTMJTZ

Regular Pleskian
Server operating system version
debian 12
Plesk version and microupdate number
18059
hi, every night i have this error
Code: 
Motivo: 2024-02-23 06:25:49 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2024-02-23 06:25:56 ERROR: Apt cache fetch failed. Try to run the `apt-get update` command.
2024-02-23 06:25:56 ERROR:
2024-02-23 06:25:56 ERROR: Exited with returncode 1.
how i can fix?
i have this problem after i installed mailman
 
Not sure because we install mailman from the system repository; anyway, makes sense to perform some checks to find out the root cause,
I would like to recommend to check the /var/log/plesk/systemupdatestool.log log file for any additional information.
Check the output of the dpkg --audit command.

We know that mailman3 requires more resources,
Compared to Mailman 2, Mailman 3 requires more RAM, and also installs more packages and dependencies. With Mailman 3, it also takes more time to create a mailing list. (c) Mailing Lists
Click to expand...
And just to double check, could you confirm that you have enough RAM on the server?

Anyway, I also going to ask developers what else makes sense to check on the server.
 
AYamshanov said:
Not sure because we install mailman from the system repository; anyway, makes sense to perform some checks to find out the root cause,
I would like to recommend to check the /var/log/plesk/systemupdatestool.log log file for any additional information.
Check the output of the dpkg --audit command.
Click to expand...

Have you tried to run apt-get update? Any result?
Do you have any custom (non system default) repositories configured on the server?
 
Hi, i have two plesk and i have the same error every day
Code: 
Raison : 2024-02-23 06:25:12 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2024-02-23 06:25:13 ERROR: Apt cache fetch failed:
2024-02-23 06:25:13 ERROR:
2024-02-23 06:25:13 ERROR: Exited with returncode 1.
 
Maybe it's not linked to Mailman after all. I suggest to contact support and allow SSH access so that a support engineer can check the issue directly on your server.

To sign-in to support please go to https://support.plesk.com

If you experience login issues, please see this KB article:
https://support.plesk.com/hc/en-us/...rt-plesk-com-and-password-reset-does-not-work

If you bought your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative:
https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk-
 
Good morning
we have been experiencing exactly the same problem every day on 2 VPS
Product: Plesk Obsidian 18.0.59
OS: Debian 10.13
Thanks for your help
Raison : 2024-02-26 06:25:47 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2024-02-26 06:25:48 ERROR: Apt cache fetch failed. Try to run the `apt-get update` command.
2024-02-26 06:25:48 ERROR:
2024-02-26 06:25:48 ERROR: Exited with returncode 1.
Click to expand...
 
I would like to specify
that we have a 3rd VPS with the same configuration
on which we have not had a problem in the last 3 days
 
Good morning
if this can help solve our problems
when the update launches every day automatically
I receive the error message by email
Raison : 2024-02-26 06:25:47 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2024-02-26 06:25:48 ERROR: Apt cache fetch failed. Try to run the `apt-get update` command.
2024-02-26 06:25:48 ERROR:
2024-02-26 06:25:48 ERROR: Exited with returncode 1.
Click to expand...
and in the file /var/log/plesk/install/autoinstaller3.log
there is the error
Err:20 https://dlm.mariadb.com/repo/mariadb-server/10.6/repo/debian buster InRelease
502 Bad Gateway [IP: ...... 443]
Err:21 https://dlm.mariadb.com/repo/maxscale/latest/apt buster InRelease
502 Bad Gateway [IP: ...... 443]
Reading package lists...
W: Failed to fetch https://dlm.mariadb.com/repo/mariadb-server/10.6/repo/debian/dists/buster/InRelease 502 Bad Gateway [IP: ....... 443]
W: Failed to fetch https://dlm.mariadb.com/repo/maxscale/latest/apt/dists/buster/InRelease 502 Bad Gateway [IP: ..... 443]
W: Some index files failed to download. They have been ignored, or old ones used instead.
Click to expand...
on the other hand if I go to Plesk and manually click on "Check for updates"
the file /var/log/plesk/install/autoinstaller3.log
updates and there is no longer the error message ....mariadb...
everything went correctly
 
Guys, I would recommend to check /var/log/plesk/install/autoinstaller3.log too. And post information about used OS on your server (is it only Debian 12?).

Err:20 https://dlm.mariadb.com/repo/mariadb-server/10.6/repo/debian buster InRelease
Click to expand...
Was the repository added manually? Asking because I am not sure that it is a part of default repositories.

Was someone able to contact with the Plesk Support team? I am asking because investigating on the affected server directly usually helps faster and with more details find a root cause. If yes, do you already have an answer? You also could share a support ticket number with me, will check how it is going.
 
Good morning,
in my case Debian 10.13
and we have not yet contacted Plesk support
Err:20 https://dlm.mariadb.com/repo/mariadb-server/10.6/repo/debian buster InRelease
Click to expand...
no this was not added manually, when we look at autoinstaller3.log, it goes back to December 2023, and this line is already present and without error for several days
in autoinstaller3.log, this morning I see that auto install was launched twice automatically
1st time with an error, email received
and a 2nd time without the error, everything went correctly
I didn't need to run the update search manually in Plesk
Thanks for your help
 
voelu28 said:
Have the same problem everyday. Ubuntu 20.04.6 LTS
Click to expand...
Code: 
Reading package lists...
W: Failed to fetch https://dlm.mariadb.com/repo/maxscale/latest/apt/dists/focal/InRelease  502  Bad Gateway [IP: 2606:4700::6811:bf0e 443]
W: Some index files failed to download. They have been ignored, or old ones used instead.
autoinstaller: read output of apt-cache policy
 
This what i have in source.list :
Code: 
deb http://deb.debian.org/debian bullseye main
deb-src http://deb.debian.org/debian bullseye main
deb http://security.debian.org/debian-security bullseye-security main
deb-src http://security.debian.org/debian-security bullseye-security main
deb http://deb.debian.org/debian bullseye-updates main
deb-src http://deb.debian.org/debian bullseye-updates main

And in sources.list.d folder
Code: 
-rw-r--r-- 1 root root  49 Oct 20  2022 php.list
-rw-r--r-- 1 root root 110 Oct 31 06:27 plesk-ext-grafana.list
-rw-r--r-- 1 root root 451 Mar  1 06:25 plesk.list

php.list :
Code: 
deb https://packages.sury.org/php/ bullseye main
 
You must log in or register to reply here.

Similar threads

brainforge
Resolved System updates have started failing.
Replies
2
Views
339
brainforge
brainforge
I
Issue in system updates
Replies
0
Views
220
Inma
I
D
Issue Apt cache fetch failed
Replies
3
Views
1K
Donnerkeil
D
D
Resolved Daily update check errors
Replies
2
Views
430
dgarcia90
D
K
Issue Docker containers don't start after plesk/extension upgrades
Replies
0
Views
642
kassi
K
Back
Top