Ask Your Question
0

Error: Failed to synchronize cache for repo 'fedora'

asked 2017-02-07 10:47:44 -0600

FedoraUser7 gravatar image

updated 2017-02-07 11:12:11 -0600

florian gravatar image

Hi,

I am getting this error, when I try to use dnf check-update or any dnf commands. Error: Failed to synchronize cache for repo 'fedora'

after troubleshooting lots of thing. I found changing mirror link to http instead of https.. it works fine.

cat /etc/yum.repos.d/fedora.repo

[fedora]
name=Fedora $releasever - $basearch
failovermethod=priority
#baseurl=http://download.fedoraproject.org/pub/fedora/linux/releases/$releasever/Everything/$basearch/os/
metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-$releasever&arch=$basearch
enabled=1
metadata_expire=14d
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=False
edit retag flag offensive close merge delete

Comments

1

Internet connection down? Mirror server down? Just wait a bit and try again, or run sudo dnf clean all && sudo dnf upgrade. I would not recommend setting the metalink to http instead of https.

florian gravatar imageflorian ( 2017-02-07 11:13:04 -0600 )edit

If the friend's tip above doesn't work, try sudo dnf clean all and remember apply after sudo dnf makecache

lobocode gravatar imagelobocode ( 2017-02-07 12:46:48 -0600 )edit

3 Answers

Sort by ยป oldest newest most voted
1

answered 2017-02-07 18:13:36 -0600

ssieb gravatar image

It sounds like a problem with your network or ssl config. What happens if you go to https://mirrors.fedoraproject.org using a web browser? You can also try adding the -v option to the dnf command to get more details about what is happening.

edit flag offensive delete link more

Comments

I found a resolution by updating below packages

dnf update nss nss-util nss-sysinit nss-tools

FedoraUser7 gravatar imageFedoraUser7 ( 2017-02-17 15:00:43 -0600 )edit
0

answered 2017-05-10 13:53:47 -0600

Please check if update URL's are resolving properly and DNS is working. I had this issue due to DNS. We need better Error Reporting from DNF.

edit flag offensive delete link more
0

answered 2017-11-16 19:14:56 -0600

Wayne Harvey gravatar image

Problem fixed 17th November with a new reinstall then used dnf clean packages and dnf update worked. Not totally convinced that the original problem was not connected to unable to access the update mirrors for some reason on that day 2 days ago.

patience is sometimes not top of my list ....

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2017-02-07 10:47:44 -0600

Seen: 9,482 times

Last updated: Nov 16 '17