Skip to main content

Cannot upgrade to 11.102.0.8 until needed system packages are installed

Comments

23 comments

  • philbean
    ahhh... I think it may be because I'm still on CentOS.8
    0
  • andrew.n
    yeah that's already EOL :(. If you click on " The last attempt to update cPanel & WHM was blocked" you will see the exact reason. You should go with AlmaLinux 8 instead or CentOS 7 (which is still supported till 2024) however the good news is that you can convert CentOS 8 to AlmaLinux 8 without reinstall as follows:
    0
  • philbean
    OK. Now I'm confused. I thought I was on CentOS 8 but checking shows I'm actually still on 7.9 so it shouldn't be an issue should it ? Clicking on the blocked message just gives me
    FATAL Cannot upgrade to 11.102.0.8 until needed system packages are installed.
    which doesn't help much. Which 'system packages' am I missing ??
    0
  • andrew.n
    Right, If you run /scripts/upcp from command line as root what does it say? If you are not familiar with SSH you can open WHM go to Terminal and type "/scripts/upcp" there.
    0
  • philbean
    it says...
    0
  • andrew.n
    okay. Can you run "yum update" and see how that goes? I bet there is the culprit.
    0
  • philbean
    just got this... [root@vs01 ~]# yum update Loaded plugins: fastestmirror, universal-hooks Loading mirror speeds from cached hostfile * EA4: 185.53.12.144 * cpanel-addons-production-feed: 185.53.12.144 * cpanel-plugins: 185.53.12.144 * epel: mirrors.coreix.net https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/wp-toolkit/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. One of the configured repositories failed (WordPress Toolkit for cPanel), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=wp-toolkit-cpanel ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable wp-toolkit-cpanel or subscription-manager repos --disable=wp-toolkit-cpanel 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=wp-toolkit-cpanel.skip_if_unavailable=true failure: repodata/repomd.xml from wp-toolkit-cpanel: [Errno 256] No more mirrors to try. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/wp-toolkit/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found [root@vs01 ~]#
    0
  • andrew.n
    that's the problem. Try this please: Workaround Add the variable distroverpkg=centos-release within /etc/yum.conf. This will resemble the following: [ root@server ~]# grep distroverpkg /etc/yum.conf distroverpkg=centos-release then run "yum update" again.
    0
  • philbean
    same result from what I can see [root@vs01 ~]# grep distroverpkg /etc/yum.conf distroverpkg=centos-release [root@vs01 ~]# yum update Loaded plugins: fastestmirror, universal-hooks Loading mirror speeds from cached hostfile epel/x86_64/metalink | 31 kB 00:00:00 * EA4: 185.53.12.144 * cpanel-addons-production-feed: 185.53.12.144 * cpanel-plugins: 185.53.12.144 * epel: mirrors.coreix.net EA4 | 2.9 kB 00:00:00 cpanel-addons-production-feed | 2.9 kB 00:00:00 cpanel-plugins | 2.9 kB 00:00:00 base | 3.6 kB 00:00:00 extras | 2.9 kB 00:00:00 mysql-connectors-community | 2.6 kB 00:00:00 mysql-tools-community | 2.6 kB 00:00:00 mysql57-community | 2.6 kB 00:00:00 mysql80-community | 2.6 kB 00:00:00 overviewer | 2.5 kB 00:00:00 updates | 2.9 kB 00:00:00 https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/wp-toolkit/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. One of the configured repositories failed (WordPress Toolkit for cPanel), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=wp-toolkit-cpanel ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable wp-toolkit-cpanel or subscription-manager repos --disable=wp-toolkit-cpanel 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=wp-toolkit-cpanel.skip_if_unavailable=true failure: repodata/repomd.xml from wp-toolkit-cpanel: [Errno 256] No more mirrors to try. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/wp-toolkit/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
    0
  • andrew.n
    I see. Can you run: yum clean all yum update? If still the same can you try the followings: yum remove redhat-lsb-core sh <(curl )
    0
  • philbean
    ran yum clean all and update no change ran the remove and got this [root@vs01 ~]# yum remove redhat-lsb-core Loaded plugins: fastestmirror, universal-hooks No Match for argument: redhat-lsb-core No Packages marked for removal [root@vs01 ~]#
    0
  • andrew.n
    At this point I would need to have a closer look at this to advise further as I'm running out of ideas so 2 options here: 1. EmergencySupport - Cheap Proactive Server Management and One-time Support with cPanel Certified Professional (click on Live Chat at the bottom right) and I will have a look for you for free
    0
  • philbean
    I'll open a ticket. Thanks for your help today. Much appreciated.
    0
  • andrew.n
    No worries, keep us updated what was it.
    0
  • cPRex Jurassic Moderator
    Can you post the ticket number here so I can follow along?
    0
  • Spirogg
    Can you post the ticket number here so I can follow along?

    0
  • philbean
    Sorted. Impressed. cP support are very good. Ticket no.
    0
  • andrew.n
    Thanks for getting back to us. Glad all good now. Take care Phil :)
    0
  • PPNSteve
    We're seeing the same problem on our CentOS 7.9 box as well. Ticket also submitted.. 94429902
    0
  • andrew.n
    @cPRex maybe a support article would be good with the steps for the fix? (just asking :) )
    0
  • cPRex Jurassic Moderator
    This is actually fixed in a release that just happened:
    0
  • aconn21
    I'm also facing a similar issue running Red Hat 7.5, ticket id 94440072
    0
  • aconn21
    My problem was solved by updating the yum config as below: yum-config-manager --enable rhui-rhel-7-server-rhui-optional-rpms
    0

Please sign in to leave a comment.