Skip to main content

MySQL 8.4. Mirror problems headers content lenght

Answered
galileuNet

We have a VPS with WHM. Last day we updgrade MySQL 8.0 to MySQL 8.4.

All works correctly but after run a yum / dnf update it returns this error:

[MIRROR] mysql84-community-release-el8-2.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 15440 but expected size is: 15196
.
.
.

[FAILED] mysql84-community-release-el8-2.noarch.rpm: No more mirrors to try - All mirrors were already tried without success

We Clear the Package Cache 
yum clean all
rm -rf /var/cache/yum/*
yum makecache

Also with dnf

But when we re run yum update / dnf update it shows the same problem?

Con you help us?

Comments

14 comments

Date Votes
  • galileuNet

    Hello!
    I search for a solution, and I found to make a reinstall. Can I do this? 

    dnf reinstall https://repo.mysql.com/mysql84-community-release-el8-2.noarch.rpm

    It works? It's secure?

    Thanks


     

    0
  • cPRex Jurassic Moderator

    Hey there!  The "Interrupted by header callback" error is usually just a temporary networking issue, so I wouldn't recommend reinstalling any packages because of that.

    Are you able to run "dnf update" on the machine without an issue at this time?  Can you also confirm that you used the WHM interface to perform the update to MySQL 8.4?

    0
  • galileuNet
    • Edited

    Hello cPRex! 
    I confirm you I used WHM interface to perform the update last Friday.
    I run "dnf update" again and continues with the same issue:

    [MIRROR] mysql84-community-release-el8-2.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 15440 but expected size is: 15196
    [MIRROR] mysql84-community-release-el8-2.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 15440 but expected size is: 15196
    [MIRROR] mysql84-community-release-el8-2.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 15440 but expected size is: 15196
    [MIRROR] mysql84-community-release-el8-2.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 15440 but expected size is: 15196
    [FAILED] mysql84-community-release-el8-2.noarch.rpm: No more mirrors to try - All mirrors were already tried without success
    (7-8/8): kernel-core-4.18.0-553.109.1.el8_10.x86_64.rpm             34% [======================-                                            ]  15 MB/s |  67 MB     00:08 ETA
    The downloaded packages were saved in cache until the next successful transaction.
    You can remove cached packages by executing 'dnf clean packages'.
    Error: Error downloading packages:
      mysql84-community-release-el8-2.noarch: Cannot download, all mirrors were already tried without success

    The repo is this? https://repo.mysql.com/mysql84-community-release-el8-2.noarch.rpm, I think...

    Thanks for your help!

    0
  • cPRex Jurassic Moderator

    Thanks for that clarification.

    When I've seen this happen before the repository file itself didn't include the "s" in https, leading to that error.  Can you check the repository file in your system in /etc/yum.repos.d/ and confirm that it does indeed use the secure https?

    0
  • galileuNet

    Hello cPRex!
    The repository file is this: mysql-community.repo?
    When I edit , this is the content: 

    [mysql80-community]
    name=MySQL 8.0 Community Server
    baseurl=http://repo.mysql.com/yum/mysql-8.0-community/el/8/$basearch/
    enabled=0
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2023
           file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2022
           file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql

    [mysql-innovation-community]
    name=MySQL Innovation Release Community Server
    baseurl=http://repo.mysql.com/yum/mysql-innovation-community/el/8/$basearch
    enabled=0
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2023
           file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2022

    [mysql-8.4-lts-community]
    name=MySQL 8.4 LTS Community Server
    baseurl=http://repo.mysql.com/yum/mysql-8.4-community/el/8/$basearch
    enabled=1
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2023

    [mysql-connectors-community]
    name=MySQL Connectors Community
    baseurl=http://repo.mysql.com/yum/mysql-connectors-community/el/8/$basearch/
    enabled=1
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2023
           file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2022
           file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql

    [mysql-tools-community]
    name=MySQL Tools Community
    baseurl=http://repo.mysql.com/yum/mysql-tools-community/el/8/$basearch/
    enabled=0
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2023
           file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2022
           file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql

    [mysql-tools-innovation-community]
    name=MySQL Tools Innovation Community
    baseurl=http://repo.mysql.com/yum/mysql-tools-innovation-community/el/8/$basearch/
    enabled=0
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2023
           file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2022

    [mysql-tools-8.4-lts-community]
    name=MySQL Tools 8.4 LTS Community
    baseurl=http://repo.mysql.com/yum/mysql-tools-8.4-community/el/8/$basearch
    enabled=1
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2023

    [mysql-cluster-8.0-community]
    name=MySQL Cluster 8.0 Community
    baseurl=http://repo.mysql.com/yum/mysql-cluster-8.0-community/el/8/$basearch/
    enabled=0
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2023
           file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2022
           file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql

    [mysql-tools-8.4-lts-community]
    name=MySQL Tools 8.4 LTS Community
    baseurl=http://repo.mysql.com/yum/mysql-tools-8.4-community/el/8/$basearch
    enabled=1
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2023

    [mysql-cluster-8.0-community]
    name=MySQL Cluster 8.0 Community
    baseurl=http://repo.mysql.com/yum/mysql-cluster-8.0-community/el/8/$basearch/
    enabled=0
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2023
           file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2022
           file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql

    [mysql-cluster-innovation-community]
    name=MySQL Cluster Innovation Release Community
    baseurl=http://repo.mysql.com/yum/mysql-cluster-innovation-community/el/8/$basearch
    enabled=0
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2023
           file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2022

    [mysql-cluster-8.4-lts-community]
    name=MySQL Cluster 8.4 LTS Community
    baseurl=http://repo.mysql.com/yum/mysql-cluster-8.4-community/el/8/$basearch
    enabled=0
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2023

     

    As I can see all baseurl points to "http:" withouy "s". This is worng,so? 
    Can I fix it? Or wait intil cPanel/WHM salve this?

    Thanks a lot! 

    Marc

     

    0
  • cPRex Jurassic Moderator

    That's correct - just add the "s" to the URL so they are all "https" and then try again.  Can you do that and see if the updates work well after that?

    0
  • galileuNet

    Hello cPRex!!
    I implemented this modification adding the "s" in all URLs (http)s, and I ran the "dnf update" again, and everything went well!! Hooray!
    You're a genius!
    Thank you so much for your help! 

    Do you know if this "issue" will be resolved in future versions?

    Marc

    0
  • cPRex Jurassic Moderator

    I'm glad to hear things are working well for you now!  It's my understanding that the missing "s" only happens on certain systems as this is not a widespread issue, and these packages are handled by MySQL directly and not cPanel, so there isn't anything we can fix on our side to ensure this doesn't happen.  You're only the second person to report this behavior so hopefully it doesn't become a larger issue.

    0
  • galileuNet

    Hello cPRex
    Ok, I understand your comments on that.
    Thank you very much for your help.

    Marc

    0
  • cPRex Jurassic Moderator

    You're very welcome!

    0
  • M van
    • Edited

    I also had the same problem on my servers. I found that performing a dnf update of the release package directly from the mysql repo url fixed the problem for me.

    dnf update https://repo.mysql.com/yum/mysql-8.4-community/el/8/x86_64/mysql84-community-release-el8-2.noarch.rpm

    0
  • galileuNet
    • Edited

    Hello!
    I have the same problem on other server.
    I try to fix it edditing the etc/yum.repos.d/mysql-community.repo  file changing http for https but, in this case, it doesn't work.
    I clean all, remove files and make cache again with :

    dnf clean all
    rm -rf /var/cache/dnf/*
    dnf makecache

    I re-run dnf update but it returns same issue, again and again:

    [MIRROR] mysql84-community-release-el8-2.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 15440 but expected size is: 15196

    I solve running "dnf update https://repo.mysql.com/yum/mysql-8.4-community/el/8/x86_64/mysql84-community-release-el8-2.noarch.rpm" as explained M van, but I think there is something I forget or something I do it wrong.

    Any solution in this case? How can I check what's wrong?

    Thanks!!

    0
  • cPRex Jurassic Moderator

    galileuNet - since we're only seeing this on a very small number of servers (we have two reports outside of this Forums thread) it doesn't seem to be a widespread issue.

    If both those systems were created at the same host or from the same image that could explain the behavior, but in all cases now it seems to be resolved by adding the "s" of by performing the update you did.

    If you'd like us to look at this issue a bit more in-depth you're always welcome to create a ticket so this can be investigated directly on the machine.

    0
  • galileuNet

    Hello!
    Ok, I understand. 
    I try to solved It by my side.

    Thanks a lot for your help

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post