 |
I have identified the problem. Basically /etc/my.cnf must be owned by mysql user. Nevertheless, this shouldn't be silently ignored. |
|
|
Same problem here. Files in /etc/my.cnf.d have correct permissions, but different SElinux context from /etc/my.cnf (etc_t vs. mysqld_etc_t). Still they would be read, if not for the include statement being in /etc/my.cnf which can't be accessed. Minimal force solution/workaround: chown :mysql /etc/my.cnf chmod g+r /etc/my.cnf |
|
|
Just ran into this issue as well. Permissions and/or owner of the file /etc/my.cnf need to be fixed. I would suggest to fix the permissions of the file to be readable by user "mysql". Is this the case the provided include paths would be read by mariadb – the default files in "/etc/my.cnf.d/" are world readable. |
|
|
i am having the same problem. changing anything in /etc/my.cnf has no effect. i even changed the permissions on the configuration files and it makes no difference. i was running in a multi configuration and now the daemon only starts in default single instance configuration. selinux is disabled |
 |
The correct permissions are as follows: -rw-r--r--. 1 root root 901 Jun 14 12:29 /etc/my.cnf and selinux context -rw-r--r--. root root system_u:object_r:mysqld_etc_t:s0 /etc/my.cnf The file should definitely NOT be owned by mysql as that would give the daemon the ability to change it, thus if someone can find a vulnerability in mariadb they could then proceed to alter the config file. See https://access.redhat.com/security/cve/cve-2016-6662 for a reason why. |
|
|
i have tried everything and mariadb does NOT read any updates made to /etc/my.cnf. [root@ns1 ~]# /usr/libexec/mysqld --verbose --help | grep -A 1 "Default options" 170614 13:16:23 [Note] Plugin 'FEEDBACK' is disabled. Default options are read from the following files in the given order: /etc/mysql/my.cnf /etc/my.cnf ~/.my.cnf there is no file /etc/mysql/my.cnf. the user mysql home directory is /var/lib/mysql and there is no file my.cnf in there i run SHOW VARIABLES; in mysql CLI and the variables show no change. i restart mariadb between changes using systemctl stop mariadb systemctl start mariadb |
|
|
What version? # rpm -qa mariadb\* mariadb-5.5.52-1.el7.x86_64 mariadb-libs-5.5.52-1.el7.x86_64 mariadb-server-5.5.52-1.el7.x86_64 |
|
|
FYI system info mariadb-server-5.5.52-1.el7.x86_64 centos-release-7-3.1611.el7.centos.x86_64 |
|
|
Yes exactly the same [root@ns1 etc]# rpm -qa mariadb\* mariadb-server-5.5.52-1.el7.x86_64 mariadb-libs-5.5.52-1.el7.x86_64 mariadb-5.5.52-1.el7.x86_64 |
|
|
Show the output from ls -la /etc/mysql/my.cnf /etc/my.cnf ls -laZ /etc/mysql/my.cnf /etc/my.cnf |
|
|
[root@ns1 etc]# ls -la /etc/mysql/my.cnf /etc/my.cnf ls: cannot access /etc/mysql/my.cnf: No such file or directory -rw-r--r-- 1 root root 943 Jun 14 11:29 /etc/my.cnf [root@ns1 etc]# ls -laZ /etc/mysql/my.cnf /etc/my.cnf ls: cannot access /etc/mysql/my.cnf: No such file or directory -rw-r--r-- root root ? /etc/my.cnf |
|
|
Then sorry, no idea, I tested here and it works for me. |
|
|
this is the server.cnf file i was using. it worked perfectly before but now any changes i make are completely ignored. maybe you spot something that i am missing that may have changed during the last update? it is supposed to be loaded from /etc/my.cnf. my.cnf only contains [client-server] !includedir /etc/my.cnf.d/multi |
|
|
will i need to take it to mariadb support? seems strange that it has been working perfectly and then after a recent restart it isn't working any more |
|
|
Yes, it looks that way to me. I'm not aware that it respects what you've done in your server.cnf file - I run parallel instances of mysqld on a box and they have separate cnf files and both have a [mysqld] section. I have no idea if [mysqld1] is a supported way of working. For that you need a mysql/mariadb person. |
|
|
yes i was thinking i might have to change to that method. these are some of the references i have been looking at; this one explains using mysql multi: https://unix.stackexchange.com/questions/256285/run-multiple-instances-of-mysql-centos7 this is for multiple mysql instances: http://sharadchhetri.com/2013/12/02/create-multiple-mysql-instance-centos-6-4-red-hat-6-4/ maybe an update of mariadb has overwritten my configuration in /usr/lib/systemd/system/mariadb.service and caused the problem? |
|
|
Very possible. If you want to change the supplied unit files, do not edit them in place as they are not defined as config files so will be overwritten on package update. You need to copy them to /etc/systemd/system and modify them there. |
|
|
thanks. i am reading this now as mentioned in the top of the unit file. http://fedoraproject.org/wiki/Systemd#How_do_I_customize_a_unit_file.2F_add_a_custom_unit_file.3F and also this for configuring systemd with multi https://forums.mysql.com/read.php?10,627016,627016 i will let you know if it doesn't solve the problem |
|
|
I think this is due to the default path of my.cnf for MariaDB having changed, see https://mariadb.com/kb/en/mariadb/configuring-mariadb-with-mycnf/ I've tried working around this by adding a custom unit file (described in this thread) to set the MYSQLD_OPTS variable, which runs into this: https://bugs.mysql.com/bug.php?id=30994 What I've done is replace the ExecStart entry in my custom unit file to move MYSQLD_OPTS to the first argument: ExecStart=/usr/libexec/mysqld $MYSQLD_OPTS --basedir=/usr $_WSREP_NEW_CLUSTER |
|
|
I installed: MariaDB-client-10.1.45-1.el7.centos.x86_64 MariaDB-common-10.1.45-1.el7.centos.x86_64 MariaDB-server-10.1.45-1.el7.centos.x86_64 MariaDB-shared-10.1.45-1.el7.centos.x86_64 on CentOS Linux release 7.6.1810 (Core) and this is the output : | character_set_client | utf8 | | character_set_connection | utf8 | | character_set_database | utf8 | | character_set_filesystem | binary | | character_set_results | utf8 | | character_set_server | utf8 | | character_set_system | utf8 | | character_sets_dir | /usr/share/mysql/charsets/ | | collation_connection | utf8_general_ci | | collation_database | utf8_general_ci | | collation_server | utf8_general_ci | Maybe should be close this "bug" |
|
|
a) 7.6.1810 is 2 whole point releases out of date and you have 18+ months of security vulnerabilities on that machine b) we don't ship MariaDB* packages at all on CentOS 7 and certainly not 10.1.45 versions of it. CentOS 7 packages are e.g. mariadb-server-5.5.65-1.el7.x86_64 - i.e package name is all lower case and the version number is 5.5.65. |
- Anonymous
