Skip to main content

[solved] cPanel Elevate Error with MySQL Server Not Working

Answered

Comments

6 comments

  • Mufasa

    How can I resolve this issue? Any support is appreciated

    0
  • Mufasa

    Upon running: 

    /scripts/elevate-cpanel --check

    I got this message:

    [root@huda2 ~]# /scripts/elevate-cpanel --check

    ** Warning **: your system does not have enough disk space available to update to AlmaLinux 8




    - /boot needs 120 M => available 84 M




    * 2024-06-20 23:43:25 [WARN] *** Elevation Blocker detected: ***

      disk space issue

    * 2024-06-20 23:43:32 [INFO] Successfully verified signature for cpanel (key types: release).

    * 2024-06-20 23:43:32 [WARN] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.

      We temporarily will enable it when it is needed to be enabled,

      but we reccomend starting the process with MySQL enabled.

    * 2024-06-20 23:43:38 [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.

    * 2024-06-20 23:43:38 [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Hg02r6KR3z/ea_profile.json

    * 2024-06-20 23:43:38 [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Hg02r6KR3z/ea_profile.json at /scripts/elevate-cpanel line 5775.

    * 2024-06-20 23:43:38 [WARN] Please fix the detected issues before performing the elevation process.

      Read More: https://cpanel.github.io/elevate/blockers/

     

    Here is the boot content, is there anything I get remove to free up some space to continue the elevate process?

    [root@huda2 /]# cd boot

    [root@huda2 boot]# ls

    config-3.10.0-1160.119.1.el7.x86_64                      lost+found

    config-3.10.0-1160.25.1.el7.x86_64                       symvers-3.10.0-1160.119.1.el7.x86_64.gz

    config-3.10.0-1160.41.1.el7.x86_64                       symvers-3.10.0-1160.25.1.el7.x86_64.gz

    config-3.10.0-1160.42.2.el7.x86_64                       symvers-3.10.0-1160.41.1.el7.x86_64.gz

    efi                                                      symvers-3.10.0-1160.42.2.el7.x86_64.gz

    grub                                                     System.map-3.10.0-1160.119.1.el7.x86_64

    grub2                                                    System.map-3.10.0-1160.25.1.el7.x86_64

    initramfs-0-rescue-9063ac396d784f4c997ceacdd0590c25.img  System.map-3.10.0-1160.41.1.el7.x86_64

    initramfs-3.10.0-1160.119.1.el7.x86_64.img               System.map-3.10.0-1160.42.2.el7.x86_64

    initramfs-3.10.0-1160.119.1.el7.x86_64kdump.img          vmlinuz-0-rescue-9063ac396d784f4c997ceacdd0590c25

    initramfs-3.10.0-1160.25.1.el7.x86_64.img                vmlinuz-3.10.0-1160.119.1.el7.x86_64

    initramfs-3.10.0-1160.25.1.el7.x86_64kdump.img           vmlinuz-3.10.0-1160.25.1.el7.x86_64

    initramfs-3.10.0-1160.41.1.el7.x86_64.img                vmlinuz-3.10.0-1160.41.1.el7.x86_64

    initramfs-3.10.0-1160.42.2.el7.x86_64.img                vmlinuz-3.10.0-1160.42.2.el7.x86_64

    initramfs-3.10.0-1160.42.2.el7.x86_64kdump.img
    0
  • Mufasa

    Removed those dump img from boot to free up some space then continued the process.

    dump.img

    Now the problem is solved and elevate process 

    [root@huda2 ~]# /scripts/elevate-cpanel --status

    success
    0
  • Mufasa

    Now I have only one issue. MySQL/MariaDB is not working and the service is not showing up at-all.

    When I navigate to "Upgrade Database Version" under WHM. I get the following:

    Your server’s database service is disabled. You cannot use the Upgrade Database Version feature while your server is in this state. For information on upgrading the database version on your server, read our Service Manager documentation.
    Log file for /var/log/mysqld.log :
    [root@huda2 ~]# tail -f /var/log/mysqld.log

    2024-06-20 23:18:00 0 [Note] InnoDB: FTS optimize thread exiting.

    2024-06-20 23:18:00 0 [Note] InnoDB: Starting shutdown...

    2024-06-20 23:18:00 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool

    2024-06-20 23:18:00 0 [Note] InnoDB: Restricted to 2016 pages due to innodb_buf_pool_dump_pct=25

    2024-06-20 23:18:00 0 [Note] InnoDB: Buffer pool(s) dump completed at 240620 23:18:00

    2024-06-20 23:18:00 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"

    2024-06-20 23:18:00 0 [Note] InnoDB: Shutdown completed; log sequence number 160390960278; transaction id 232113351

    2024-06-20 23:18:00 0 [Note] Event Scheduler: Purging the queue. 0 events

    2024-06-20 23:18:00 0 [Note] /usr/sbin/mariadbd: Shutdown complete
     I also tried running this command
    whmapi1 configureservice service=mysql enabled=1 monitored=1

    I got the following:

    --- 
    metadata:
      command: configureservice
      reason: "Failed to enable mysql.\nmysql not enabled successfully"
      result: 0
      version: 1

    When run the following:

    # ps aux | grep mysql

    I get this:

    root        5051  0.0  0.0 222020  1124 pts/0    S+   02:07   0:00 grep --color=auto mysql
     
     

    All databases exist. It is just MySQL server won't start. So how can I resolve this issue? 

     

    0
  • Mufasa

    Problem solved after upgrading MariaDB via the command line using this article:

    https://support.cpanel.net/hc/en-us/articles/4418179691415-How-to-upgrade-MySQL-MariaDB-on-the-command-line

     

    1
  • cPRex Jurassic Moderator

    Thanks for sharing the solution!

    0

Please sign in to leave a comment.