Announcement

Collapse
No announcement yet.

Upgrading to MariaDB 11.4 issue

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Upgrading to MariaDB 11.4 issue

    I'm trying to update to MariaDB 11.4 from 10.11 on CL9. I'm using:
    /usr/share/lve/dbgovernor/mysqlgovernor.py --mysql-version=mariadb1104
    /usr/share/lve/dbgovernor/mysqlgovernor.py --install

    It never completes, but gives the output:

    Code:
    !!!Before making any changes to the database, make sure that you have a backup copy of users' data!!!
    Instruction: how to create a whole-database backup - http://docs.cloudlinux.com/index.html?backing_up_mysql.html
    Do you confirm that you've made a full backup of your MySQL databases? [y/n] y
    Saving current enabled module: mariadb:cl-MariaDB1011
    Cached module: mariadb:cl-MariaDB1011
    Start downloading current installed packages
    Package /usr/share/lve/dbgovernor/tmp/governor-tmp/old/cl-MariaDB1011-libs-10.11.11-1.module_el9.5.0+228+b70fdeb2.x86_64.rpm was loaded
    Package /usr/share/lve/dbgovernor/tmp/governor-tmp/old/cl-MariaDB1011-10.11.11-1.module_el9.5.0+228+b70fdeb2.x86_64.rpm was loaded
    Package /usr/share/lve/dbgovernor/tmp/governor-tmp/old/cl-MariaDB1011-devel-10.11.11-1.module_el9.5.0+228+b70fdeb2.x86_64.rpm was loaded
    Package /usr/share/lve/dbgovernor/tmp/governor-tmp/old/mysqlclient21-8.0.35-1.el9.cloudlinux.x86_64.rpm was loaded
    Package /usr/share/lve/dbgovernor/tmp/governor-tmp/old/mysqlclient18-5.5.62-4.el9.cloudlinux.x86_64.rpm was loaded
    Package /usr/share/lve/dbgovernor/tmp/governor-tmp/old/cl-MariaDB1011-server-10.11.11-1.module_el9.5.0+228+b70fdeb2.x86_64.rpm was loaded
    Package /usr/share/lve/dbgovernor/tmp/governor-tmp/old/cl-MariaDB-meta-client-10.11.11-1.module_el9.5.0+228+b70fdeb2.x86_64.rpm was loaded
    Package /usr/share/lve/dbgovernor/tmp/governor-tmp/old/cl-MariaDB-meta-10.11.11-1.module_el9.5.0+228+b70fdeb2.x86_64.rpm was loaded
    Package /usr/share/lve/dbgovernor/tmp/governor-tmp/old/cl-MariaDB-meta-devel-10.11.11-1.module_el9.5.0+228+b70fdeb2.x86_64.rpm was loaded
    Started downloading packages for the new installation
    This system is receiving updates from CloudLinux Network server.
    164 files removed
    WARNING!!!! Package cl-MariaDB-meta was not downloaded
    WARNING!!!! Package cl-MariaDB-meta-client was not downloaded
    WARNING!!!! Package cl-MariaDB-meta-devel was not downloaded
    Package /usr/share/lve/dbgovernor/tmp/governor-tmp/new/mysqlclient18-5.5.62-4.el9.cloudlinux.x86_64.rpm was loaded
    Package /usr/share/lve/dbgovernor/tmp/governor-tmp/new/mysqlclient21-8.0.35-1.el9.cloudlinux.x86_64.rpm was loaded
    Package /usr/share/lve/dbgovernor/tmp/governor-tmp/new/libaio-0.3.111-13.el9.x86_64.rpm was loaded
    Installation of MySQL packages will not be completed because not all of the new packages have been downloaded​
    What can I do to resolve?

  • #2
    Please ensure you have a databases backup before the upgrade just to be safe.

    It seems the main issue is this:
    Cached module: mariadb:cl-MariaDB1011
    I believe you have to clear/reset module first, please run:
    Code:
    dnf module reset mariadb -y​
    Then try again.

    Comment


    • #3
      That worked. Thanks!

      I was only doing this on a test server, so backing up wasn't critical. But when I did try to run the backup script it references, it said the script doesn't work on CL9. Is there a way to do this in CL9?

      Code:
      package pv is not installed
      
      Checking if the "pv" package is installed in the system...
      
      
      !!!The script doesn't support the 9 version of the operating system!!!​

      Comment


      • #4
        What is this backup script?

        Comment


        • #5
          This one: /usr/share/lve/dbgovernor/scripts/mysql_backup.sh​

          It was mentioned in the link http://docs.cloudlinux.com/index.htm..._up_mysql.html which was mentioned in the output of /usr/share/lve/dbgovernor/mysqlgovernor.py --install

          Comment


          • #6
            Ah, thanks for the information, it seems this is the first report about such case. I have filled a bugrport with ID: CLOS-3399

            Comment

            Working...
            X