MariaDB my.cnf why is it differ much after install and your template?

Centmin Mod 123.09beta01 and higher will install the base template, then dynamically update it to auto optimize it for server environment it detects etc. So different servers may end up with different /etc/my.cnf settings

 

It may as Centmin Mod auto optimisation routine also measures disk I/O performance and adjusts settings appropriately for your disk speeds.

You may have some backed up /etc/my.cnf when centmin mod initially installed your server - so I'd check those files to make sure if one doesn't have the rest of your my.cnf settings first though you maybe missing the changes auto applied on updates.

Code (Text):

ls -lahrt /etc/ | grep my.
-rw-r--r--.  1 root  root  202 Feb  4 02:30 my.cnf.rpmnew
-rw-r--r--.  1 root  root  570 Mar 11 16:11 my.cnf-original
-rw-r--r--.  1 root  root 4.0K Mar 11 16:11 my.cnf-newold
drwxr-xr-x.  2 root  root 4.0K Mar 11 16:13 my.cnf.d
-rw-r--r--.  1 root  root 5.1K Mar 11 16:13 my.cnf-setiobackup
-rw-r--r--.  1 root  root 5.1K Mar 12 16:24 my.cnf

• my.cnf-original is one before centmin mod install
• my.cnf-newold is one after mariadb initial version or upgraded version was installed before centmin mod applied settings
• my.cnf-setiobackup is one before tools/setio.sh runs to optimise mysql disk related variable settings
• my.cnf existing live /etc/my.cnf

 

MariaDB 10.3 will have totally different defaults for those settings compared to MariaDB 10.0/10.1/10.2

 

yes some settings in MariaDB 10.3 are either deprecated or set to default so not required in /etc/my.cnf