MariaDB update is not shown in 'Edit Database Configuration'

jndawson

• July 15, 2025 18:36

Updated MariaDB from v.10.6.22 to v.11.4.7 on an AL/CL 8 server w/ cPanel v.128.0.15:

The installation of MySQL for db_governor completed
---
metadata:
  command: configureservice
  reason: Enabled monitoring for mysql.
  result: 1
  version: 1
Giving the MySQL service time to start before checking its status (15 sec)
Saving current enabled module: mariadb:cl-MariaDB1104
Installation of MySQL for db_governor completed
Cached module: mariadb:cl-MariaDB1104
[ Tue Jul 15 11:20:10 ]
[ root@cp2 ~># mariadb --version
mariadb from 11.4.7-MariaDB, client 15.2 for Linux (x86_64) using readline 5.1

Checking WHM > Edit Database Configuration shows:

Configuration Settings for MariaDB 10.6.22

Restarting MariaDB doesn't change it. How to get the UI to match the installation?

 

• 

  cPRex Jurassic Moderator

  • July 15, 2025 18:47

  Hey there!  Since this work was performed through the CloudLinux DBGovernor tool, the interface cache just likely needs a bit of time to catch up.

  You could try running /scripts/upcp to force the update, but I would guess this will happen overnight automatically as well.

  0
• 

  jndawson

  • July 15, 2025 18:55

  Howdy cPRex,

  We're running that now.

  Interestingly, we're about to elevate to CL9, and we removed the files identified in the alt-common error, but they were all reinstalled when upgrading MariaDB. So, guess we'll remove them again.

  Jim

  1
• 

  cPRex Jurassic Moderator

  • July 15, 2025 18:57

  Let me know how it goes!

  0
• 

  jndawson

  • July 15, 2025 18:57

  Nope, /scripts/upcp completed, no change in the UI.

  0
• 

  jndawson

  • July 15, 2025 19:27

  checked versionlock

  [ Tue Jul 15 12:22:23 ]
  [ root@cp2 ~># dnf versionlock list | grep mariadb
  [ Tue Jul 15 12:25:58 ]

  Also tried /scripts/update_db_cache and /scripts/restartsrv_cpsrvd; still seeing incorrect mariadb version.

  0
• 

  cPRex Jurassic Moderator

  • July 15, 2025 19:38

  Thanks for confirming.  I've also done tests on my end to confirm this issue and I've created case CPANEL-48226 to have our team take care of that.

  I also confirmed that this behavior is exclusive to the DB Governor tool, as the same behavior does not happen on a standard AlmaLinux machine using the WHM >> Upgrade Database Version tool.

  I've also linked this thread to that case so I'll be sure to post updates as I get them.

  0
• 

  jndawson

  • July 16, 2025 02:45

  Just checked and the correct version displays; we did nothing, so some background script must have run.

  0
• 

  cPRex Jurassic Moderator

  • July 16, 2025 14:09

  I did update the case with you saying that it eventually works, so there must be some type of caching update between cPanel and DB Governor that gets triggered outside of the cPanel update system.

  It should be an easy fix once the team has a chance to check it out.

  0

Please sign in to leave a comment.