Invalid MariaDB release configured, please change 'mariadb' line in options.conf

S

sec-is

Verified User
Joined
Feb 14, 2020
Messages
96
I am trying to install DA, however I got stopped at
>> Invalid MariaDB release configured, please change 'mariadb' line in options.conf
This is a legacy license (if that would matter), and in options.conf (copied from the current working server) I have:
mariadb=10.5
mysql_inst=mariadb
(left away all other lines for clarity).

I checked in a working D.A. for all versions available ( :2222/evo/admin/custombuild/customize-versions )
mariadb10.11 10.11.9
mariadb10.3 10.3.39
mariadb10.4 10.4.34
mariadb10.5 10.5.26
mariadb10.6 10.6.19
mariadb11.4 11.4.3

Why does DA not want to install 10.5? It should work out of the box.

I had this before and was not able to manage this, but I do not want to be forced to a newer version.

And this does not help either:
#da build versions
Invalid MariaDB release configured, please change 'mariadb' line in options.conf

If I look for myself:
# grep maria versions.txt
mariadb10.3:10.3.39:
mariadb10.4:10.4.34:
mariadb10.5:10.5.26:
mariadb10.6:10.6.19:
mariadb10.11:10.11.9:
mariadb11.4:11.4.3:

Any help would be appreciated! I am stuck with a fresh and expensive dedicated server which can not be installed.
 
sec-is said:
>> Invalid MariaDB release configured, please change 'mariadb' line in options.conf
Click to expand...
Have you manually entered that? Maybe some odd thing happened. Did you try this already?

da build set mariadb 10.5
da build set mysql_inst mariadb

This will at least make sure no odd characters or something happen.
 
#da build set mariadb 10.5
mariadb is already set to 10.5

Helaas. Unfortunately.

You gave me an idea. (do not forget, nothing was installed, not even exim)

# da build set mariadb 10.6
Changed mariadb option from 10.5 to 10.6
# da build set mariadb 10.5
10.5 is not a valid setting for mariadb option.

Even though versions show it is an option, it is not valid.

Bug?
 
This is on a running server (Almalinux 8):
# da build set mysql_inst mariadb
mysql_inst is already set to mariadb
# da build opt_help|grep maria
mariadb: 10.3, 10.4, 10.5, 10.6. Current value: 10.6. Default value: 10.6.
mysql_inst: mysql, mariadb, no. Current value: mariadb. Default value: mariadb.

This is on the new to install server (Almalinux 9):
# da build set mysql_inst mariadb
mysql_inst is already set to mariadb

# da build opt_help|grep maria
mariadb: 10.6. Current value: 10.5. Default value: 10.6.
mysql_inst: mysql, mariadb, no. Current value: mariadb. Default value: mariadb.

It looks like I am forced to install version 10.6, which I do not want to install.
But why am I forced? And how can this be changed?

Or is there a restriction because I am running the new server on Almalinux 9, and does the O.S. not allow to install a version below 10.6?
I seem to recall DA is using the O.S. to install mysql/mariadb. That might be the reason of this all. Which I am not too happy about, clearly.

I googled around and found this page
access.redhat.com

Red Hat Enterprise Linux Application Streams Life Cycle - Red Hat Customer Portal

Access Red Hat’s knowledge, guidance, and support through your subscription.
access.redhat.com access.redhat.com
At "RHEL 9 Full Life Application Streams Release Life Cycle" I found:

Application StreamRelease DateRetirement DateRelease
MariaDB 10.5May 2022May 20329.0

I really do not understand what is wrong with installing 10.5 via Direct Admin.
 
sec-is said:
I really do not understand what is wrong with installing 10.5 via Direct Admin.
Click to expand...
If you put in a complete options.conf with mariadb 10.5 before starting the setup, it should work.
So if it doesn't at this time, this sounds like a bug to me.

You are allowed to send in a ticket for bugs on legacy license. Maybe you can also send a pm to @fln or @smtalk to confirm if this might be a bug.
As for mariadb itself, it's june 2025 so well.... certainly not EOL yet, no matter where you look.
 
Not all MariaDB versions are supported on all of the systems:
  • RHEL 9 and systems supports only MariaDB 10.6 and higher.
  • All distros on ARM systems supports MariaDB 10.6 or higher.
  • Debian/Ubuntu and RHEL 8 supports MariaDB 10.3 and higher.
I would guess you are using RHEL 9 system. I am not sure why there is restriction on minimum version for RHEL 9 systems, but I know this restriction was always there (well it was there since DA started supporting RHEL 9).
 
I have made a quick test of running our MariaDB test suite on RHEL 9, AlamaLinux 9, Rocky Linux 9, CentOS Stream 9 with MariaDB 10.3, MariaDB 10.4, and MariaDB 10.5 (plus upgrade tests migrating one MariaDB version to another) and everything works fine.

I see no reason to keep this restriction. Unless we find any issues, we will most likely remove the minimum MariaDB 10.6 restriction in the DirectAdmin 1.670 release.

It might be useful to run MariaDB 10.5 because it matches the release that is provided by the distro packages. This would allow easy migration between CB and distro-managed MariaDB versions.
 
Is 1.67 soon to be released, can I benefit from this?
Or can I test it out for you, beta testing? That would speed up things for me as well.
I installed Almalinux 8 earlier today, not anticipating this quock turnaround.
I'd rather run Almalinux 9 and can wait for this update (in terms of days).
 
Last edited:
Version 1.670 RC in beta will be released tomorrow or in the next couple of days. The minimum version restriction is already removed and will be auto-released with the next alpha build (alpha gets automatic releases daily at ~02:00 UTC).
 
after
export DA_CHANNEL="alpha"
I was able to install D.A. and with mariadb 10.5
Glad this is fixed, thank you.
 
You must log in or register to reply here.
Back
Top