MariaDB 10.11 not available in CustomBuild on AlmaLinux 9.8

kapaweb

Verified User
Joined
Apr 22, 2021
Messages
32
Hello,

I have just installed a new server with:

  • AlmaLinux 9.8
  • DirectAdmin 1.706
  • CustomBuild 2.0.0
  • MariaDB 10.6.27
I need to upgrade Moodle to version 5.2, which requires MariaDB 10.11 or newer.

However, CustomBuild only shows MariaDB versions up to 10.6:

[root@server ~]# da build opt_help full | grep -A5 -B2 -E '^mysql=|mysql_inst'<br><br>mysql: 8.0. Current value: 8.0. Default value: 8.0. Description: MySQL version.<br>mariadb: 10.4, 10.5, 10.6. Current value: 10.6. Default value: 10.6. Description: MariaDB version.<br>mysql_inst: mysql, mariadb, no. Current value: mariadb. Default value: mariadb. Description: Enables management of MySQL/MariaDB using CustomBuild.<br>mysql_backup: yes, no. Current value: yes. Default value: yes. Description: Backups MySQL databases before the installation of MySQL/MariaDB server.<br>mysql_backup_gzip: yes, no. Current value: no. Default value: no. Description: Compress MySQL database backups.<br>mysql_backup_dir: userinput. Current value: /usr/local/directadmin/custombuild/mysql_backups. Default value: /usr/local/directadmin/custombuild/mysql_backups. Description: Sets full path for mysql_backup option were MySQL backups should be placed.<br>mysql_force_compile: yes, no. Current value: no. Default value: no. Description: Force compilation of MySQL/MariaDB instead of using system packages (RPM, DEB)
DirectAdmin and CustomBuild are already up to date:
DirectAdmin 1.706
CustomBuild 2.0.0


When I run:

da build set mariadb 10.11
CustomBuild reports that 10.11 is not a valid value.

I understand that DirectAdmin generally supports MariaDB 10.11, so I am trying to understand why it is not available on this installation.

Is MariaDB 10.11 currently unsupported on AlmaLinux 9.8 through CustomBuild, or is there an additional configuration, repository, channel, or license setting that I need to enable?

What is the recommended and supported way to upgrade this server from MariaDB 10.6 to MariaDB 10.11 without breaking DirectAdmin package management?

Thank you.
 
Does this mean that the lifetime licenses we previously purchased are effectively becoming obsolete, since they will no longer support newer MariaDB, OS, php etc. versions?

Will legacy lifetime licenses continue receiving support for current operating systems, database versions, and security updates, or will upgrading to a subscription license eventually become mandatory?
 
his mean that the lifetime licenses we previously purchased are effectively becoming obsolete, since they will no longer support newer MariaDB,
Yes

You can upgrade your legacy license to a full license with reduced fee of 15 Dollar /month
 
When I purchased these lifetime licenses, they were explicitly advertised as including automatic upgrades and updates.

The archived DirectAdmin pricing page from April 10, 2019 shows the Lifetime license with:

  • Automatic upgrades / updates
  • Protection against price increases
  • Only technical support was limited to 90 days
Archive:
https://web.archive.org/web/20190410091021/https://directadmin.com/pricing.php

Furthermore, in DirectAdmin’s official announcement on July 1, 2019, DirectAdmin Sales stated:

“We are not going to start charging for updates. A promise is a promise.”

The same announcement also states:

“Unlimited updates is something we promised.”

I am not requesting technical support or additional Pro Pack features. I am asking why essential software updates, such as support for newer MariaDB versions, are now being withheld from licenses that were sold with lifetime/unlimited updates.

How is this consistent with the original terms and promises under which these licenses were purchased?
 
You are right, please search on this forum, lot of threads are opened about this with more than 10 pages discussions but this is not changing anything about it I am afraid
Take tour loss and purchase the special offer for the legacy licenses (15 dollar in place of 30 dollar)
 
Welcome to 2026..... We do not own anything these days: video games, software, blah..... If a company goes out of business, so does yours.
 
but agreements are still agreements and should be honored.
You might want to check your license agreement then, because in there it's not specified, and website advertisements do unfortunatelly not count as agreements.
Also the term "lifetime" has various definitions especially with software.

And it's still working and you can still update.

I'm also not happy about it, like a lot of us, but it is what it is. So best to search and read previous discussions about it, all is already said and done multiple times. Even about agreements, no use starting another one.
 
Hello,

Thank you for your response.

In this case, the restriction appears to be directly related to the license check, not to CustomBuild or the MariaDB installation process.

I upgraded MariaDB manually from 10.6 to 10.11.18, without using DirectAdmin or CustomBuild. MariaDB itself is running normally and accepting connections:

<span>Version: '10.11.18-MariaDB'<br>Status: ready for connections<br>Active: active (running)</span>
DirectAdmin also starts and runs, but its license check repeatedly returns the following error:

<span>checking license error=transient license check failure:<br>legacy code-base does not support this MariaDB version,<br>downgrade MariaDB or upgrade DirectAdmin license</span>
Before the manual upgrade, the same server and license worked normally with MariaDB 10.6.

This message explicitly occurs during the license check and instructs me to upgrade the DirectAdmin license. Therefore, it does not appear to be simply a case of DirectAdmin encountering an unfamiliar database version for data-safety reasons.

Could you please escalate this to a developer and clarify:

  1. Why does the license check fail solely because MariaDB 10.11 is installed?
  2. Is the MariaDB version being checked by the licensing system?
  3. How can I configure DirectAdmin to continue operating with the manually installed MariaDB version?
  4. What exact value should be used for the <span>mysql=</span> setting in <span>directadmin.conf</span>?
  5. If no intentional restriction exists, is this behavior a bug that can be corrected in the legacy codebase?
The database upgrade was completed successfully and MariaDB is functioning correctly. The only reported failure is the DirectAdmin legacy license check.

Kind regards,

Konstantinos
 
Again, please read threads about it, all of that is spoken of and answered before. I will do a part once more.

1.) It's part of the legacy declaring of lifetime licenses where no new features are given anymore. Development to have DA working with the new MariaDB versions (and Mysql too and OS too) is seen as new features and thus not given anymore.
2.) The MariaDB version is checked by custombuild which is build into DA nowadays. Not sure about licensing system itself probably too.
3.) Don't know
4.) Don't know
5.) The restriction is intentional. You're free to use any Mysql or Mariadb version with a legacy license, but you can't use DA to configure things for it. Or maybe when configuring some scripts yourself via phpmyadmin or whatever.

Maybe somebody of dev or sales or support will answer too, might also be not the case either anymore.
 
Back
Top