I have problem with a MariaDB variable not taking change

[jamHN]

Hi everyone

I want to tell you that I just installed Cacti version 1.2.14, the installation
I am doing it in Debian 10 Buster, with the Apache server version: Apache / 2.4.38 (Debian),
the MariaDB version I use MariaDB 10.5, when I create the database from
cacti I set it as DEFAULT_CHARACTER_SET_NAME utf8mb4 and DEFAULT_COLLATION_NAME
utf8mb4_unicode_ci, so the whole pre-configuration process is fine, then
that I proceed web to finish the installation via web, in the pre-installation check,
I have some recommendations that I should make in MariaDB before installing Cacti, here
edit the my.cnf file, I add all the variables that I need to modify, but only
there is a variable that is alarmed and it is collation_server, where it says that the
current value is utf8mb4_general_ci and I should change it to utf8mb4_unicode_ci, this change
It is already done in the my.cnf file, MariaDB is restarted, but it does not take the change.

Someone has an idea what is due or what I must modify for the change to apply.

[TheWitness]

Check in your /etc/my.cnf.d directory for another file overwriting the value.

[jamHN]

I explain the following based on your recommendation.

here I do the search for other possible files my.cnf where there are a total of three files as I show

root@server:/etc/mysql# find / -name my.cnf

/etc/mysql/my.cnf
/etc/alternatives/my.cnf
/var/lib/dpkg/alternatives/my.cnf


1) In /etc/mysql/my.cnf all the variables that it is recommended to do in the pre installation are added.


2) In this second file /etc/alternatives/my.cnf the variables that are detailed are the same as /etc/mysql/my.cnf, they are assigned automatically when I edit /etc/mysql/my.cnf


3) In this third file /var/lib/dpkg/alternatives/my.cnf we can see the following

auto
/etc/mysql/my.cnf

/etc/mysql/mariadb.cnf
200
/etc/mysql/my.cnf.fallback
100



what I do not understand is that the other variables are applied in MariaDB, even thinking that it is a Bug, I did the test with several versions of MariaDB and I have no problem.

[Achea9]

Hi,

I know it is a headeck which I also had before.

Very easy and unexpectable, look

character-set-server = utf8mb4
collation-server = utf8mb4_unicode_ci

for Mariadb to accept the format.

cheers

[jamHN]

Add to the my.cnf file what you recommended, restart mariaDB but I still have the same problem, I'll show you how my my.cnf file looks



root@server:/etc/mysql# more my.cnf

[mysqld]

character-set-server = utf8mb4
collation-server = utf8mb4_unicode_ci

[TheWitness]

You are going to have to research your setup. It's not a common setup. MariaDB specifically uses:

/etc/my.cnf.d/server.cnf

For server variables, and that's where you would need to place these settings. So, not sure what bird you've latched onto, but better to stick with RedHat and Debian variants IMHO.

[csh74]

I also ran into this issue after upgrading my MariaDB to a 10.x version... After extensive searching, trial & error, I eventually corrected my issue by adding a new heading within my /etc/my.cnf file.

[mariadb]
collation_server=utf8mb4
character_set_client=utf8mb4_unicode_ci


After a restart of the service, the change was taken.

[TheWitness]

Holy crap! What version?

[csh74]

Version 1.2.12

[TheWitness]

MariaDB version.