Bug #77531 | mysqld_safe Logging to '/var/log/mariadb/mariadb.log' | ||
---|---|---|---|
Submitted: | 29 Jun 2015 7:41 | Modified: | 30 Jun 2015 6:40 |
Reporter: | Shahriyar Rzayev | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Installing | Severity: | S1 (Critical) |
Version: | 5.7.7-rc | OS: | CentOS (7) |
Assigned to: | CPU Architecture: | Any |
[29 Jun 2015 7:41]
Shahriyar Rzayev
[29 Jun 2015 7:47]
Shahriyar Rzayev
Even with specifying --datadir it will fail: [root@centos7_vm mysql]# bin/mysqld_safe --user=mysql --datadir=/opt/mysql/datadir 150629 12:46:08 mysqld_safe Logging to '/var/log/mariadb/mariadb.log'. touch: cannot touch ‘/var/log/mariadb/mariadb.log’: No such file or directory chmod: cannot access ‘/var/log/mariadb/mariadb.log’: No such file or directory touch: cannot touch ‘/var/log/mariadb/mariadb.log’: No such file or directory chown: cannot access ‘/var/log/mariadb/mariadb.log’: No such file or directory 150629 12:46:08 mysqld_safe Starting mysqld daemon with databases from /opt/mysql/datadir bin/mysqld_safe: line 130: /var/log/mariadb/mariadb.log: No such file or directory bin/mysqld_safe: line 164: /var/log/mariadb/mariadb.log: No such file or directory touch: cannot touch ‘/var/log/mariadb/mariadb.log’: No such file or directory chown: cannot access ‘/var/log/mariadb/mariadb.log’: No such file or directory chmod: cannot access ‘/var/log/mariadb/mariadb.log’: No such file or directory 150629 12:46:08 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended bin/mysqld_safe: line 130: /var/log/mariadb/mariadb.log: No such file or directory
[29 Jun 2015 8:26]
Shahriyar Rzayev
Some more tests: # Running without any parameter: [root@centos7_vm mysql]# bin/mysqld_safe 150629 12:57:43 mysqld_safe Logging to '/var/log/mariadb/mariadb.log'. touch: cannot touch ‘/var/log/mariadb/mariadb.log’: No such file or directory chmod: cannot access ‘/var/log/mariadb/mariadb.log’: No such file or directory touch: cannot touch ‘/var/log/mariadb/mariadb.log’: No such file or directory chown: cannot access ‘/var/log/mariadb/mariadb.log’: No such file or directory 150629 12:57:43 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql bin/mysqld_safe: line 130: /var/log/mariadb/mariadb.log: No such file or directory bin/mysqld_safe: line 164: /var/log/mariadb/mariadb.log: No such file or directory touch: cannot touch ‘/var/log/mariadb/mariadb.log’: No such file or directory chown: cannot access ‘/var/log/mariadb/mariadb.log’: No such file or directory chmod: cannot access ‘/var/log/mariadb/mariadb.log’: No such file or directory 150629 12:57:43 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended bin/mysqld_safe: line 130: /var/log/mariadb/mariadb.log: No such file or directory # Running with unknown parameter: [root@centos7_vm mysql]# bin/mysqld_safe kwelewr 150629 12:57:34 mysqld_safe Logging to '/var/log/mariadb/mariadb.log'. touch: cannot touch ‘/var/log/mariadb/mariadb.log’: No such file or directory chmod: cannot access ‘/var/log/mariadb/mariadb.log’: No such file or directory touch: cannot touch ‘/var/log/mariadb/mariadb.log’: No such file or directory chown: cannot access ‘/var/log/mariadb/mariadb.log’: No such file or directory 150629 12:57:34 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql bin/mysqld_safe: line 130: /var/log/mariadb/mariadb.log: No such file or directory bin/mysqld_safe: line 164: /var/log/mariadb/mariadb.log: No such file or directory touch: cannot touch ‘/var/log/mariadb/mariadb.log’: No such file or directory chown: cannot access ‘/var/log/mariadb/mariadb.log’: No such file or directory chmod: cannot access ‘/var/log/mariadb/mariadb.log’: No such file or directory 150629 12:57:34 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended bin/mysqld_safe: line 130: /var/log/mariadb/mariadb.log: No such file or directory
[29 Jun 2015 10:14]
Shahriyar Rzayev
It seems that, there is a my.cnf file, even I have not installed any MariaDB. So the problem exists because of abandoned my.cnf file which comes as default with CentOS 7. Keeping in mind this,maybe documentation should be improved in some way, like note this problem in "installation from source section".
[30 Jun 2015 6:34]
MySQL Verification Team
Hi Shahriyar, Thank you for the report. I would mark it as a not bug, because this was intended behavior. Normally, options are read from the following files in the given order: /etc/my.cnf /etc/mysql/my.cnf /usr/local/mysql/etc/my.cnf ~/.my.cnf and with my.cnf exists from earlier rpm installation caused this issue. On my local build, I see something like below: mysql-5.7.8: bin/mysqld --help --verbose 2> /dev/null | grep -B 1 '/etc/my.cnf' Default options are read from the following files in the given order: /etc/my.cnf /etc/mysql/my.cnf /usr/local/mysql/etc/my.cnf ~/.my.cnf In such cases, you can always start with --no-defaults which can be used to prevent from unwanted option being read. Thanks, Umesh
[30 Jun 2015 6:40]
Shahriyar Rzayev
Yes really it is not a bug. There is a default my.cnf (MariaDB) with CentOS 7, even with fresh minimal installation. We need just keep this in mind.