Mirror Sync Strategy Or Problem?

Home » CentOS » Mirror Sync Strategy Or Problem?
CentOS 4 Comments

Hello, I have a CentOS 7 server, right installed. I notice that some packages that are present at http://mirror.CentOS.org/CentOS/7/updates/x86_64/Packages/
are not present yet at some other mirrors (that are the ones my fastestmirror plugin picks up… even after a clean):
or http://ct.mirror.garr.it/mirrors/CentOS/7/updates/x86_64/Packages/

For example packages like glibc, bash and dbus have updates dated 02 August on the main mirror site but not yet at the other two sites. if in CentOS-Base.repo file, [updates] section, I use baseurl instead of mirrorlist entry and run

sudo yum clean all sudo yum update

I then get these packages’ list:
Dependencies Resolved

==================================================================================================================== Package Arch Version Repository Size
bash x86_64
4.2.46-20.el7_2 updates 1.0 M
dbus x86_64
1:1.6.12-14.el7_2 updates 306 k dbus-libs x86_64
1:1.6.12-14.el7_2 updates 151 k dbus-x11 x86_64
1:1.6.12-14.el7_2 updates 46 k device-mapper-persistent-data x86_64
0.6.2-1.el7_2 updates 366 k glibc x86_64
2.17-106.el7_2.8 updates 3.6 M
glibc-common x86_64
2.17-106.el7_2.8 updates 11 M
gssproxy x86_64
0.4.1-8.el7_2 updates 84 k initscripts x86_64
9.49.30-1.el7_2.3 updates 429 k iscsi-initiator-utils x86_64 updates 419 k iscsi-initiator-utils-iscsiuio x86_64 updates 82 k libblkid x86_64
2.23.2-26.el7_2.3 updates 167 k libgovirt x86_64
0.3.3-1.el7_2.4 updates 64 k libgudev1 x86_64
219-19.el7_2.12 updates 66 k libmount x86_64
2.23.2-26.el7_2.3 updates 169 k libsss_idmap x86_64
1.13.0-40.el7_2.12 updates 104 k libsss_nss_idmap x86_64
1.13.0-40.el7_2.12 updates 103 k libtiff x86_64
4.0.3-25.el7_2 updates 169 k libuuid x86_64
2.23.2-26.el7_2.3 updates 74 k mdadm x86_64
3.3.2-7.el7_2.1 updates 393 k microcode_ctl x86_64
2:2.1-12.el7_2.1 updates 535 k open-vm-tools x86_64
9.10.2-5.el7_2 updates 472 k open-vm-tools-desktop x86_64
9.10.2-5.el7_2 updates 161 k sssd-client x86_64
1.13.0-40.el7_2.12 updates 158 k systemd x86_64
219-19.el7_2.12 updates 5.1 M
systemd-libs x86_64
219-19.el7_2.12 updates 358 k systemd-python x86_64
219-19.el7_2.12 updates 99 k systemd-sysv x86_64
219-19.el7_2.12 updates 53 k util-linux x86_64
2.23.2-26.el7_2.3 updates 1.9 M

Transaction Summary
====================================================================================================================Upgrade 29 Packages

Total download size: 28 M
Is this ok [y/d/N]:

What are typical delays in mirrors’ sync? Or is there any problem in mirrors updates?

Thanks, Gianluca

4 thoughts on - Mirror Sync Strategy Or Problem?

  • Thanks for the link I didn’t know, Tom

    One mirror says:
    6hours 3hours ok

    The other one:
    4hours 40minutes ok

    I’m not sure I completely understand exact meaning of columns…

    For sure 9 hours ago none of them contained August updates inside the directories I linked before…

  • –avoloGBRCpCcdICXIsgIPQMgVlHl8QSl8
    Content-Type: text/plain; charset=windows-1252
    Content-Transfer-Encoding: quoted-printable

    External Mirrors sync at whatever period they choose. It could be daily or multiple times per day.

    It can certainly take up to 24 hours for the majority of external mirrors to be updated.

    Our script to verify mirrors can take 3-4 hours to run as well to develop a new mirrorlist.

    Yesterday at 2200 UTC, we released 24 SRPMs worth of updates. That is a significant amount of information. (around 200 RPMs and 150-200 MB of info). Based on the 24 hour period I usually use, I would expect most mirror to be updated by 2200 UTC today (still 11 hours from now).


  • Thanks for clarification of the workflow Johnny. I’m just realizing now that in effect when I worked on this new system (too late in time as usual.. ;-) my mind was ahead one week (holidays needed for sure…) and I thought 7 days had passed from release of the packages in question… instead I was referring to packages released the same day !
    I beg my pardon to the cited mirrors maintainers… m(_ _)m

    Actually the source of the total following confusion was me checking that after the system update I had a relative “old” kernel in terms of release date (it seems latest released is kernel-3.10.0-327.22.2.el7.x86_64.rpm released on 2016-06-23.. I hope my eyes are better today…) and I wanted to crosscheck comparing mirror contents… and then the misunderstanding

    Also because on RHN portal I saw that apparently a kernel-3.10.0-327.28.2.el7.x86_64.rpm was released with changelog dated on 27/06…. but checking better I see now that Red Hat actually has just released it yesterday as from:

    thanks again to all