CentOS upgrade fails

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • sn
    Junior Member
    • Mar 2021
    • 6

    #1

    CentOS upgrade fails

    Hi,

    I keep getting errors when upgrading my centos servers. Why does this happen?
    I use CentOS 6 x86_64 as a xen pv template. cpanel is installed and i use the upgrade script.

    The errors are like this:

    Error Downloading Packages:
    lve-0.9-0.2.el6.x86_64: failed to retrieve getPackage/lve-0.9-0.2.el6.x86_64.rpm from cloudlinux-x86_64-server-6
    error was [Errno 14] PYCURL ERROR 51 - "SSL: certificate subject name xmlrpc.cln.cloudlinux.com does not match target host name ams-proxy.cl-mirror.net\"
  • iseletsk
    Senior Member
    • Dec 2017
    • 1199

    #2
    We are fixing it right now. One of the mirrors has wrong certificate (it was ok for 5.x, but 6.x doens accept it).

    Comment

    • sn
      Junior Member
      • Mar 2021
      • 6

      #3
      Ok.. It seems that the upgrade script select wrong kernels too.
      It should use kernel-xen but it dosen .

      Is there a fix for this also?

      Comment

      • iseletsk
        Senior Member
        • Dec 2017
        • 1199

        #4
        1. Edit /etc/sysconfig/kernel
        Change DEFAULTKERNEL from kernel to kernel-xen
        If you don have that file, create it, and populate it with this:

        # UPDATEDEFAULT=yes
        # new kernels the default
        UPDATEDEFAULT=yes

        # DEFAULTKERNEL specifies the default kernel package type
        DEFAULTKERNEL=kernel-xen

        2. Do:
        yum install kernel-xen

        3. Don skip this step:
        rpm -qa|grep kernel
        Take all non-xen kernels, and for each of them:
        rpm -e kernel-.....
        (full version of a kernel)

        If you leave any non kernel-xen packages, future yum updates will update those packages as well.

        Comment

        • iseletsk
          Senior Member
          • Dec 2017
          • 1199

          #5
          That particular mirror should be back to normal, you should be able to update from it now.

          Comment

          • sn
            Junior Member
            • Mar 2021
            • 6

            #6
            How do i see if its a xen kernel? I see no kernel with xen in the name.

            Comment

            • iseletsk
              Senior Member
              • Dec 2017
              • 1199

              #7
              xen kernel come in a package named:
              kernel-xen

              and when you do uname -r it will show up as:
              2.6.32-231.6.1.lve0.9.8.x86_64xen

              or something similar

              Comment

              • sn
                Junior Member
                • Mar 2021
                • 6

                #8
                Well.. It doesn really seem to work with the xen kernel.

                # yum install kernel-xen
                Loaded plugins: fastestmirror, rhnplugin
                Loading mirror speeds from cached hostfile
                * cloudlinux-x86_64-server-6: ams-proxy.cl-mirror.net
                Setting up Install Process
                Package kernel-2.6.32-231.6.1.lve0.9.8.x86_64 already installed and latest version
                Nothing to do

                # rpm -qa|grep kernel
                kernel-2.6.32-71.29.1.el6.x86_64
                kernel-firmware-2.6.32-231.6.1.lve0.9.8.noarch
                kernel-devel-2.6.32-231.6.1.lve0.9.8.x86_64
                dracut-kernel-004-33.2.el6_0.noarch
                kernel-headers-2.6.32-231.6.1.lve0.9.8.x86_64
                kernel-2.6.32-231.6.1.lve0.9.8.x86_64

                Comment

                • lkanter
                  Member
                  • Nov 2016
                  • 34

                  #9
                  In CL6 regular kernel (without -xen) should be able to act as xen domU kernel, no other kernel is needed.

                  Comment

                  • iseletsk
                    Senior Member
                    • Dec 2017
                    • 1199

                    #10
                    could you post /boot/grub/menu.lst

                    Comment

                    • lkanter
                      Member
                      • Nov 2016
                      • 34

                      #11
                      Please replace "xvda" to "xvde" in both /boot/grub/grub.conf and /etc/fstab and try to boot our kernel - it should boot.

                      Comment

                      • iseletsk
                        Senior Member
                        • Dec 2017
                        • 1199

                        #12
                        Аs a side note -- this is a temporary solution -- we will fix it in the future.

                        Comment

                        Working...