# Rocky 9 mirrors out of sync? .22 kernel not consistently present

**URL:** <https://forums.rockylinux.org/t/rocky-9-mirrors-out-of-sync-22-kernel-not-consistently-present/18921>\
**Category:** Rocky Linux Help & Support\
**Tags:** rocky-linux-9\
**Created:** [June 24, 2025, 10:22am UTC](https://forums.rockylinux.org/t/rocky-9-mirrors-out-of-sync-22-kernel-not-consistently-present/18921 "2025-06-24T10:22:30Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![sweh](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/sweh/32/1287_2.png) [@sweh](https://forums.rockylinux.org/u/sweh)\
**Post date:** [June 24, 2025, 10:22am UTC](https://forums.rockylinux.org/t/rocky-9-mirrors-out-of-sync-22-kernel-not-consistently-present/18921/1 "2025-06-24T10:22:30Z")

</div>

5 days ago the .22 kernel was released ( [Kernel , kernel devel and kernel headers are mismatch - #6 by nazunalika](https://forums.rockylinux.org/t/kernel-kernel-devel-and-kernel-headers-are-mismatch/18863/6) ).

I’m thinking this sync issue may still be present.

In my homelab, on my Rocky9 machines, I have a nightly cron job that mails me when patches are available. In theory, for kernel updates, I should be getting consistent results across all the machines. But only a subset are reporting. And on those when I come to an upgrade I either get 404 errors or (after a `dnf clean all`) the repo server doesn’t think the .22 kernel is available.

Of my 6 machines, 1 is fully patched, 2 have the .22 headers but not any of the other files (so there’s a mismatch between headers and kernel), and the remaining 3 don’t have any .22 files and only have .21.

I know I could remove the mirrorlist and just use baseurl, but I figure that if I’m seeing this issue across multiple installs then others might be as well.

---

<div class="post-metadata">

**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\
**Post date:** [June 24, 2025, 10:39am UTC](https://forums.rockylinux.org/t/rocky-9-mirrors-out-of-sync-22-kernel-not-consistently-present/18921/2 "2025-06-24T10:39:39Z")

</div>

Yes, it’s still present. I don’t even see the kernel-headers for the .22 kernel, nor any others to be honest.

Seems that the Rocky mirrors are in a bit of a state right now because whoever is managing them isn’t syncing them properly or not frequently enough 🤷

Two of my machines do have the .22 kernel, installed six days ago.

---

<div class="post-metadata">

**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\
**Post date:** [June 24, 2025, 12:00pm UTC](https://forums.rockylinux.org/t/rocky-9-mirrors-out-of-sync-22-kernel-not-consistently-present/18921/3 "2025-06-24T12:00:48Z")

</div>

Neil is checking into it, so we should have some info soon.

---

<div class="post-metadata">

**Author:** ![House\_Blend](https://avatars.discourse-cdn.com/v4/letter/h/96bed5/32.png) [@House\_Blend](https://forums.rockylinux.org/u/House_Blend)\
**Post date:** [June 24, 2025, 6:25pm UTC](https://forums.rockylinux.org/t/rocky-9-mirrors-out-of-sync-22-kernel-not-consistently-present/18921/4 "2025-06-24T18:25:30Z")

</div>

@sweh Thanks for bringing this up. I observed the same issue. I manage 3 rocky9 machines. When I’ve noticed out-of-sync differences from dnf among the 3 in the past, I’ve generally been able to fix it by running a ‘dnf clean all’ or waiting a day before doing an update.

But there appears to be something seriously broken with mirror synchronization right now.

One machine saw the .22 kernel on June 19. I waited, wanting to keep all 3 on the same kernel, but the next day, it must have chosen a different mirror, because it was no longer available. The next several days were bizarre: now-you-see-me-now-you-don’t on all three machines, and never consistently the same across all three.

On Monday the 23rd I got irritated enough to browse through the mirror database to find one that was geographically nearby and had the .22 kernel (including the kernel-devel package that I needed from the appstream repo). It took me several rounds of trial and error and reading the dnf manpage to figure out how to _temporarily_ use an alternate mirror without changing any of the existing config files.

I’m offering it here in case it helps others, or if experts want to critique it.

```auto
URLA="https://example.com/rocky/9.6/AppStream/x86_64/os/"
URLB="https://example.com/rocky/9.6/BaseOS/x86_64/os/"

dnf --disablerepo="*" \
    --repofrompath appstream-tmp,${URLA} \
    --repofrompath baseos-tmp,${URLB} \
    update

```

I hope it is obvious that the above URLs are fake – you’ll have to find mirror URLs that work for you. FWIW I’m located in the US/Eastern time zone, so there are lots of mirrors for me to choose from that are geographically nearby.

---

<div class="post-metadata">

**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\
**Post date:** [June 25, 2025, 7:12am UTC](https://forums.rockylinux.org/t/rocky-9-mirrors-out-of-sync-22-kernel-not-consistently-present/18921/5 "2025-06-25T07:12:14Z")

</div>

This should be fixed now. The problem was about 50% of the mirrors weren’t synced for some reason, but this was resolved yesterday by the infra team and the mirrors now seem to have synced.

There might still be some that haven’t caught up yet, but generally it should now be OK.

---

<div class="post-metadata">

**Author:** ![sweh](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/sweh/32/1287_2.png) [@sweh](https://forums.rockylinux.org/u/sweh)\
**Post date:** [June 26, 2025, 1:07am UTC](https://forums.rockylinux.org/t/rocky-9-mirrors-out-of-sync-22-kernel-not-consistently-present/18921/6 "2025-06-26T01:07:19Z")

</div>

Yup, all my machines got the .22 kernel update. Thanks!

---

<div class="post-metadata">

**Author:** ![jessevf](https://avatars.discourse-cdn.com/v4/letter/j/ac8455/32.png) [@jessevf](https://forums.rockylinux.org/u/jessevf)\
**Post date:** [June 27, 2025, 12:52am UTC](https://forums.rockylinux.org/t/rocky-9-mirrors-out-of-sync-22-kernel-not-consistently-present/18921/7 "2025-06-27T00:52:55Z")

</div>

It’s Thursday evening 06/26 and I’m hitting this on all my new builds today, it is not fixed.

```auto
[MIRROR] kernel-modules-core-5.14.0-570.22.1.el9_6.x86_64.rpm: Curl error (18): Transferred a partial file for http://dl.rockylinux.org/pub/rocky/9/BaseOS/x86_64/os/Packages/k/kernel-modules-core-5.14.0-570.22.1.el9_6.x86_64.rpm [transfer closed with 30977213 bytes remaining to read]
[MIRROR] findutils-4.8.0-7.el9.x86_64.rpm: Status code: 504 for http://dl.rockylinux.org/pub/rocky/9/BaseOS/x86_64/os/Packages/f/findutils-4.8.0-7.el9.x86_64.rpm (IP: 199.232.198.132)
[MIRROR] libnfnetlink-1.0.1-23.el9_5.x86_64.rpm: Status code: 504 for http://dl.rockylinux.org/pub/rocky/9/BaseOS/x86_64/os/Packages/l/libnfnetlink-1.0.1-23.el9_5.x86_64.rpm (IP: 199.232.198.132)
[MIRROR] kernel-modules-core-5.14.0-570.22.1.el9_6.x86_64.rpm: Curl error (18): Transferred a partial file for http://dl.rockylinux.org/pub/rocky/9/BaseOS/x86_64/os/Packages/k/kernel-modules-core-5.14.0-570.22.1.el9_6.x86_64.rpm [transfer closed with 22588605 bytes remaining to read]
[FAILED] kernel-modules-core-5.14.0-570.22.1.el9_6.x86_64.rpm: No more mirrors to try - All mirrors were already tried without success
Error: Error downloading packages:
  kernel-modules-core-5.14.0-570.22.1.el9_6.x86_64: Cannot download, all mirrors were already tried without success

```

---

<div class="post-metadata">

**Author:** ![label](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@label](https://forums.rockylinux.org/u/label)\
**Post date:** [June 27, 2025, 6:10am UTC](https://forums.rockylinux.org/t/rocky-9-mirrors-out-of-sync-22-kernel-not-consistently-present/18921/8 "2025-06-27T06:10:14Z")

</div>

Your errors are unrelated to the mirrors syncing. You are connecting to our mirror ([dl.rockylinux.org](http://dl.rockylinux.org)) and you’re receiving 504’s or partial downloads. However, that is not the behavior I am seeing in my own systems.

```auto
[label@sani tmp]$ wget http://dl.rockylinux.org/pub/rocky/9/BaseOS/x86_64/os/Packages/k/kernel-modules-core-5.14.0-570.22.1.el9_6.x86_64.rpm http://dl.rockylinux.org/pub/rocky/9/BaseOS/x86_64/os/Packages/f/findutils-4.8.0-7.el9.x86_64.rpm http://dl.rockylinux.org/pub/rocky/9/BaseOS/x86_64/os/Packages/l/libnfnetlink-1.0.1-23.el9_5.x86_64.rpm http://dl.rockylinux.org/pub/rocky/9/BaseOS/x86_64/os/Packages/k/kernel-modules-core-5.14.0-570.22.1.el9_6.x86_64.rpm
Saving 'findutils-4.8.0-7.el9.x86_64.rpm'
HTTP response 200 OK [http://dl.rockylinux.org/pub/rocky/9/BaseOS/x86_64/os/Packages/f/findutils-4.8.0-7.el9.x86_64.rpm]
HTTP response 200 OK [http://dl.rockylinux.org/pub/rocky/9/BaseOS/x86_64/os/Packages/k/kernel-modules-core-5.14.0-570.22.1.el9_6.x86_64.rpm]
kernel-modules-core- 100% [==================================================================================================================================================================>] 30.54M 2.67MB/s

                          [Files: 3 Bytes: 31.09M [2.71MB/s] Redirects: 0 Todo: 0 Errors: 0 ]
[label@sani tmp]$ ls -ltr | grep el9
-rw-r--r--. 1 label label 549239 Nov 4 2024 findutils-4.8.0-7.el9.x86_64.rpm
-rw-r--r--. 1 label label 29132 Feb 4 02:44 libnfnetlink-1.0.1-23.el9_5.x86_64.rpm
-rw-r--r--. 1 label label 32025789 Jun 18 19:49 kernel-modules-core-5.14.0-570.22.1.el9_6.x86_64.rpm

```

Are you going outbound through a proxy or some sort of filter?

---

<div class="post-metadata">

**Author:** ![jessevf](https://avatars.discourse-cdn.com/v4/letter/j/ac8455/32.png) [@jessevf](https://forums.rockylinux.org/u/jessevf)\
**Post date:** [June 27, 2025, 6:28am UTC](https://forums.rockylinux.org/t/rocky-9-mirrors-out-of-sync-22-kernel-not-consistently-present/18921/9 "2025-06-27T06:28:29Z")

</div>

No, but it may have been a temporary issue this evening, though we had the same issue throughout the last week off and on. I did notice this evening that [mirrors.rockylinux.org](http://mirrors.rockylinux.org) was throwing a 504, after I had given up and went looking to create a mirror of our own. I noticed that came online an hour or so later and updates were pulled down.

Why wouldn’t it try any other mirror besides [dl.rockylinux.org](http://dl.rockylinux.org)? These are stock boxes. I assumed from the “No more mirrors to try - All mirrors were already tried without success” error that it had tried other mirrors, but is that not the case?

---

<div class="post-metadata">

**Author:** ![sweh](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/sweh/32/1287_2.png) [@sweh](https://forums.rockylinux.org/u/sweh)\
**Post date:** [June 27, 2025, 10:46am UTC](https://forums.rockylinux.org/t/rocky-9-mirrors-out-of-sync-22-kernel-not-consistently-present/18921/10 "2025-06-27T10:46:42Z")

</div>

There _do_ seem to be continuing issues. I noticed this yesterday but waited a day to see if it happened again.

For example, on one of my machines, 3 hours ago it told me:

```auto
Subject: Patches needed

NetworkManager.x86_64 1:1.52.0-4.el9_6 baseos
NetworkManager-libnm.x86_64 1:1.52.0-4.el9_6 baseos
NetworkManager-team.x86_64 1:1.52.0-4.el9_6 baseos
NetworkManager-tui.x86_64 1:1.52.0-4.el9_6 baseos
bind-libs.x86_64 32:9.16.23-29.el9_6 appstream
bind-license.noarch 32:9.16.23-29.el9_6 appstream
bind-utils.x86_64 32:9.16.23-29.el9_6 appstream
container-selinux.noarch 4:2.237.0-1.el9_6 appstream
elfutils-debuginfod-client.x86_64 0.192-6.el9_6 baseos
elfutils-default-yama-scope.noarch 0.192-6.el9_6 baseos
elfutils-libelf.x86_64 0.192-6.el9_6 baseos
elfutils-libs.x86_64 0.192-6.el9_6 baseos
emacs-filesystem.noarch 1:27.2-14.el9_6.2 appstream
iputils.x86_64 20210202-11.el9_6.1 baseos
kpartx.x86_64 0.8.7-35.el9_6.1 baseos
krb5-libs.x86_64 1.21.1-8.el9_6 baseos
ksh.x86_64 3:1.0.6-7.el9_6.1 appstream
libarchive.x86_64 3.5.3-5.el9_6 baseos
libdb.x86_64 5.3.28-57.el9_6 baseos
libldb.x86_64 4.21.3-5.el9_6 baseos   
linux-firmware.noarch 20250513-151.1.el9_6 baseos   
linux-firmware-whence.noarch 20250513-151.1.el9_6 baseos   
microcode_ctl.noarch 4:20250211-1.20250512.1.el9_6 baseos   
pam.x86_64 1.5.1-25.el9_6 baseos
systemd.x86_64 252-51.el9_6.1 baseos
systemd-libs.x86_64 252-51.el9_6.1 baseos
systemd-pam.x86_64 252-51.el9_6.1 baseos
systemd-rpm-macros.noarch 252-51.el9_6.1 baseos   
systemd-udev.x86_64 252-51.el9_6.1 baseos

```

But when I just now tried a `dnf clean all; dnf -y update` then it said

```auto
55 files removed
Docker CE Stable - x86_64 163 kB/s | 74 kB 00:00
Extra Packages for Enterprise Linux 9 - x86_64 14 MB/s | 20 MB 00:01
Extra Packages for Enterprise Linux 9 openh264 4.7 kB/s | 2.5 kB 00:00
MariaDB 198 kB/s | 623 kB 00:03
Rocky Linux 9 - BaseOS 2.3 MB/s | 2.5 MB 00:01
Rocky Linux 9 - AppStream 11 MB/s | 9.6 MB 00:00
Rocky Linux 9 - Extras 94 kB/s | 17 kB 00:00
Dependencies resolved.
Nothing to do.
Complete!

```

I re-ran that command and it found 6 patches

```auto
Upgraded:
  bind-libs-32:9.16.23-29.el9_6.x86_64                                          
  bind-license-32:9.16.23-29.el9_6.noarch                                       
  bind-utils-32:9.16.23-29.el9_6.x86_64                                         
  container-selinux-4:2.237.0-1.el9_6.noarch                                    
  emacs-filesystem-1:27.2-14.el9_6.2.noarch                                     
  ksh-3:1.0.6-7.el9_6.1.x86_64   

```

On another machine that I tried to patch at the same time I got lots of 404 errors, before it successfully downloaded 23 rpms. Just trying to get `systemd-udev-252-51.el9_6.1.x86_64.rpm` hit 13 404s

eg

```auto
[MIRROR] systemd-udev-252-51.el9_6.1.x86_64.rpm: Status code: 404 for https://mirror.servaxnet.com/rocky-linux/9.6/BaseOS/x86_64/os/Packages/s/systemd-udev-252-51.el9_6.1.x86_64.rpm (IP: 162.255.226.75)
[MIRROR] systemd-udev-252-51.el9_6.1.x86_64.rpm: Status code: 404 for https://rocky-linux-us-west1.production.gcp.mirrors.ctrliq.cloud/pub/rocky//9.6/BaseOS/x86_64/os/Packages/s/systemd-udev-252-51.el9_6.1.x86_64.rpm (IP: 34.49.195.49)
[MIRROR] systemd-udev-252-51.el9_6.1.x86_64.rpm: Status code: 404 for http://ash.mirrors.clouvider.net/rocky/9.6/BaseOS/x86_64/os/Packages/s/systemd-udev-252-51.el9_6.1.x86_64.rpm (IP: 45.250.25.130)
[MIRROR] systemd-udev-252-51.el9_6.1.x86_64.rpm: Status code: 404 for https://pit.mirror.jurassicinnovations.com/rocky/9.6/BaseOS/x86_64/os/Packages/s/systemd-udev-252-51.el9_6.1.x86_64.rpm (IP: 193.30.34.70)
[MIRROR] systemd-udev-252-51.el9_6.1.x86_64.rpm: Status code: 404 for https://rocky-linux-us-west4.production.gcp.mirrors.ctrliq.cloud/pub/rocky//9.6/BaseOS/x86_64/os/Packages/s/systemd-udev-252-51.el9_6.1.x86_64.rpm (IP: 35.186.229.59)
[MIRROR] systemd-udev-252-51.el9_6.1.x86_64.rpm: Status code: 404 for http://nyc.mirrors.clouvider.net/rocky/9.6/BaseOS/x86_64/os/Packages/s/systemd-udev-252-51.el9_6.1.x86_64.rpm (IP: 94.154.159.241)
[MIRROR] systemd-udev-252-51.el9_6.1.x86_64.rpm: Status code: 404 for https://rocky-linux-us-south1.production.gcp.mirrors.ctrliq.cloud/pub/rocky//9.6/BaseOS/x86_64/os/Packages/s/systemd-udev-252-51.el9_6.1.x86_64.rpm (IP: 34.36.6.112)
[MIRROR] systemd-udev-252-51.el9_6.1.x86_64.rpm: Status code: 404 for https://rocky-linux-us-east4.production.gcp.mirrors.ctrliq.cloud/pub/rocky//9.6/BaseOS/x86_64/os/Packages/s/systemd-udev-252-51.el9_6.1.x86_64.rpm (IP: 34.49.194.122)
[MIRROR] systemd-udev-252-51.el9_6.1.x86_64.rpm: Status code: 404 for https://mirror.web-ster.com/rocky/9.6/BaseOS/x86_64/os/Packages/s/systemd-udev-252-51.el9_6.1.x86_64.rpm (IP: 65.182.224.39)
[MIRROR] systemd-udev-252-51.el9_6.1.x86_64.rpm: Status code: 404 for https://rocky-linux-us-east5.production.gcp.mirrors.ctrliq.cloud/pub/rocky//9.6/BaseOS/x86_64/os/Packages/s/systemd-udev-252-51.el9_6.1.x86_64.rpm (IP: 34.144.209.88)
[MIRROR] systemd-udev-252-51.el9_6.1.x86_64.rpm: Status code: 404 for https://rocky-linux-us-central1.production.gcp.mirrors.ctrliq.cloud/pub/rocky//9.6/BaseOS/x86_64/os/Packages/s/systemd-udev-252-51.el9_6.1.x86_64.rpm (IP: 34.49.215.167)
[MIRROR] systemd-udev-252-51.el9_6.1.x86_64.rpm: Status code: 404 for http://mirror.cs.vt.edu/pub/rocky/9.6/BaseOS/x86_64/os/Packages/s/systemd-udev-252-51.el9_6.1.x86_64.rpm (IP: 128.173.237.17)
[MIRROR] systemd-udev-252-51.el9_6.1.x86_64.rpm: Status code: 404 for https://rocky-linux-us-west2.production.gcp.mirrors.ctrliq.cloud/pub/rocky//9.6/BaseOS/x86_64/os/Packages/s/systemd-udev-252-51.el9_6.1.x86_64.rpm (IP: 34.36.50.162)
(3/23): systemd-udev-252-51.el9_6.1.x86_64.rpm 881 kB/s | 1.9 MB 00:02

```

---

<div class="post-metadata">

**Author:** ![sweh](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/sweh/32/1287_2.png) [@sweh](https://forums.rockylinux.org/u/sweh)\
**Post date:** [June 30, 2025, 11:19am UTC](https://forums.rockylinux.org/t/rocky-9-mirrors-out-of-sync-22-kernel-not-consistently-present/18921/11 "2025-06-30T11:19:47Z")

</div>

Update: yesterday all my machines got patches, but there were still a few 404s in the output, but they seemed to work. Today none of the machines are saying they need patches, so maybe it’s all working again 🙂

---

<div class="post-metadata">

**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\
**Post date:** [June 30, 2025, 11:37am UTC](https://forums.rockylinux.org/t/rocky-9-mirrors-out-of-sync-22-kernel-not-consistently-present/18921/12 "2025-06-30T11:37:27Z")

</div>

I’ve been following the propagation here: [Propagation - Mirror Manager](https://mirrors.rockylinux.org/mirrormanager/propagation)

You can see when updates are pushed that it hits about 50% or lower, and the following day the majority of it is green and up-to-date. So looks like it’s a lot better now.

---

<div class="post-metadata">

**Author:** ![sweh](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/sweh/32/1287_2.png) [@sweh](https://forums.rockylinux.org/u/sweh)\
**Post date:** [July 3, 2025, 12:39am UTC](https://forums.rockylinux.org/t/rocky-9-mirrors-out-of-sync-22-kernel-not-consistently-present/18921/13 "2025-07-03T00:39:39Z")

</div>

It’s been below 50% for the past 2 days; I’m again seeing inconsistencies; eg with the “sudo” package which was released at least 2 days ago.

---

<div class="post-metadata">

**Author:** ![label](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@label](https://forums.rockylinux.org/u/label)\
**Post date:** [July 3, 2025, 3:55am UTC](https://forums.rockylinux.org/t/rocky-9-mirrors-out-of-sync-22-kernel-not-consistently-present/18921/14 "2025-07-03T03:55:52Z")

</div>

The propagation report is based on repomd.xml, not individual packages.

With that said, we have several mirrors who seem to always be out of sync. We’re going to be contacting them soon to see what can be done about their rsync policies.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/1X/91b7219eec10e30013422e4df76c1d898711a5d5.svg) [@system](https://forums.rockylinux.org/u/system)\
**Post date:** [September 1, 2025, 3:56am UTC](https://forums.rockylinux.org/t/rocky-9-mirrors-out-of-sync-22-kernel-not-consistently-present/18921/15 "2025-09-01T03:56:29Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.