Skip to main content

cPanel & WHM update failure in upcp script

Comments

16 comments

  • Rogier Bakx

    Got the same problem on all our cpanel servers.. after yum update (Seems that repos are changed to centos instead of Almalinux)

    0
  • rhm.geerts

    Same problem here, Almalinux 9.

    Error: Failed to download metadata for repo 'EA4-c9': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

    Tried doing a dnf clean all and dnf makecache, but same error.

    If repo's were changed to Centos, then only on cPanel, I don't have that issue on servers with other panel.

    0
  • quietFinn

    We have the same problem, CloudLinux 8 and AlmaLinux 8

     

    0
  • Andreix

    The folders are all empty, there are only files in AlmaLinux10. The CentOS folder is empty on posibly all repos. I checked 2-3 and nothing is there, this is why we get 404.

    I am using Alma 9 and the search is looking for CentOS/9/ .... Probably someone deleted all CentOS repos, I  hope by mistake

    0
  • quietFinn

    Seems to work now.

     

    1
  • rhm.geerts

    Not here yet on Alma 9 and no Cloudlinux. Still the same error.

     

    0
  • albertchu

    It's OK now for me.

    0
  • FlintTown

    Still 404 during anything related to yum. Which breaks EA4 from doing anything as well.

    0
  • FlintTown

    seems to be back up and running

    0
  • rhm.geerts

    Did you do anything special (give some commands), are you running Cloudlinux or not?

     

    0
  • quietFinn

    You can do the usual:
    yum clean all
    yum makecache
    if the problem is still there then makecache fails, but then just wait.

     

     

    0
  • RH

    working for me now, wasn't working for the last few hours.
    I've done a recent yum clean all and then a yum update and it's all working as it should.

    0
  • rhm.geerts

    quietFinn I did that before and still the same error.

    Tried just now again and now it works fine again here too.

    0
  • rbairwell

    The 403 error indicates that the resource was Forbidden (and 404 is, of course, File Not Found). Given it's part of an automatic update process, I would guess some maintenance was happening on those specific servers at the time of the updates and hence why your updates failed. Running the update again could automatically select another server (which might be working) or the "under maintenance" server may be fixed.

    0
  • cPRex Jurassic Moderator

    Hey there!  There were some mirror issues yesterday around the time of this post but they are all resolved at this point.  Let me know if you're still seeing issues!

    0
  • rhm.geerts

    rbairwell as you could see from several posts above, running again did not select another server or another server also gave 404, we all tried several times again.

    cPRex Thank you for confirming there were mirror issues. No problems anyomore here.

    0

Please sign in to leave a comment.