| Bug #102846 | default error log file is with name of mariadb ? Any reason | ||
|---|---|---|---|
| Submitted: | 7 Mar 12:44 | Modified: | 11 Apr 7:06 |
| Reporter: | Ankit Kapoor | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Server: Installing | Severity: | S6 (Debug Builds) |
| Version: | 8.0.23 | OS: | Linux |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | MariaDB, MySQL | ||
[7 Mar 12:44]
Ankit Kapoor
[7 Mar 14:48]
Terje Røsten
The tarball don't ship any my.cnf file and don't ship any files outside the normal unpacked directory mysql-... If you have /etc/my.cnf or other mysql files around there origin are from other sources. (However, mysql might use /etc/my.cnf if present, it's up to DBA to control the origin and contents of the file.)
[7 Mar 14:50]
Terje Røsten
If you don't want MySQL to read /etc/my.cnf look a the --no-defaults and --defaults-file options: https://dev.mysql.com/doc/refman/8.0/en/option-file-options.html
[7 Mar 15:02]
Ankit Kapoor
Thanks. "/etc/my.cnf" file got created post running mysqld and my.cnf file got created on its own. Please note I installed mysqld completely on new server and there is no chance to have my.cnf file from other sources. Have you tried reproducing it ?
[7 Mar 15:03]
Ankit Kapoor
my concern is even if mysqld is creating /etc/my.cnf file then how come log error and pid file is of "mariadb"
[7 Mar 17:38]
Terje Røsten
Can you please describe in detail how you come this to your conclusion? I can't reproduce: [root@host]# wget -q https://dev.mysql.com/get/Downloads/MySQL-8.0/mysql-8.0.23-linux-glibc2.12-x86_64.tar.xz [root@host]# md5sum mysql-8.0.23-linux-glibc2.12-x86_64.tar.xz b7228a20ab3f43d830f0f791cb52c229 mysql-8.0.23-linux-glibc2.12-x86_64.tar.xz [root@host]# tar xf mysql-8.0.23-linux-glibc2.12-x86_64.tar.xz [root@host]# cd mysql-8.0.23-linux-glibc2.12-x86_64 [root@host mysql-8.0.23-linux-glibc2.12-x86_64]# ls LICENSE README bin docs include lib man share support-files [root@host mysql-8.0.23-linux-glibc2.12-x86_64]# ls -l /etc/my.cnf ls: cannot access '/etc/my.cnf': No such file or directory [root@host mysql-8.0.23-linux-glibc2.12-x86_64]# bin/mysqld --user=mysql --initialize --datadir=/tmp/my 2021-03-07T17:31:43.794953Z 0 [System] [MY-013169] [Server] /tmp/mysql-8.0.23-linux-glibc2.12-x86_64/bin/mysqld (mysqld 8.0.23) initializing of server in progress as process 119268 2021-03-07T17:31:43.799977Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started. 2021-03-07T17:31:43.955191Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended. 2021-03-07T17:31:44.784735Z 6 [Note] [MY-010454] [Server] A temporary password is generated for root@localhost: +ls(J+a4rohi [root@host mysql-8.0.23-linux-glibc2.12-x86_64]# ls -l /etc/my.cnf ls: cannot access '/etc/my.cnf': No such file or directory There is no /etc/my.cnf present nor before or after initialize.
[9 Mar 10:24]
Terje Røsten
Hi again, any other trick you can use is the seen which files MySQL uses to set options. Try for example this query: mysql> select * from performance_schema.variables_info where VARIABLE_PATH like '/etc%'; Giving something like: +---------------+-----------------+---------------+-----------+-----------+----------+----------+----------+ | VARIABLE_NAME | VARIABLE_SOURCE | VARIABLE_PATH | MIN_VALUE | MAX_VALUE | SET_TIME | SET_USER | SET_HOST | +---------------+-----------------+---------------+-----------+-----------+----------+----------+----------+ | datadir | GLOBAL | /etc/my.cnf | 0 | 0 | NULL | NULL | NULL | | log_error | GLOBAL | /etc/my.cnf | 0 | 0 | NULL | NULL | NULL | | pid_file | GLOBAL | /etc/my.cnf | 0 | 0 | NULL | NULL | NULL | | socket | GLOBAL | /etc/my.cnf | 0 | 0 | NULL | NULL | NULL | +---------------+-----------------+---------------+-----------+-----------+----------+----------+----------+ And mysql> select * from performance_schema.variables_info where VARIABLE_NAME like 'pid_file'; +---------------+-----------------+---------------+-----------+-----------+----------+----------+----------+ | VARIABLE_NAME | VARIABLE_SOURCE | VARIABLE_PATH | MIN_VALUE | MAX_VALUE | SET_TIME | SET_USER | SET_HOST | +---------------+-----------------+---------------+-----------+-----------+----------+----------+----------+ | pid_file | GLOBAL | /etc/my.cnf | 0 | 0 | NULL | NULL | NULL | +---------------+-----------------+---------------+-----------+-----------+----------+----------+----------+ When problematic file is found you can use package manager tool for system. RPM on RHEL/OracleLinux/CentOS: $ rpm -qf /path/to/my.cnf dpkg on Debian and Ubuntu systems: $ dpkg -S /path/to/my.cnf To get package which is problematic.
[9 Mar 13:28]
Ankit Kapoor
Hello, Sorry for coming late on this and thanks for your follow up and providing the above information. I tried re producing this and again got this error. But this time I finally realised that error is not with mysql binary files. It is with the VM I am buying from one of the cloud vendor. So issue is whenever I create a VM my.cnf file comes there automatically. Since I never expected this I never thought to check from that angle. See below : [root@xyz ~]# ps -ef|grep mysql root 8266 8226 0 21:25 pts/0 00:00:00 grep --color=auto mysql [root@xyz ~]# ls -lrth /etc/my.cnf -rw-r--r--. 1 root root 570 Oct 19 16:29 /etc/my.cnf [root@xyz ~]#
[10 Mar 7:35]
Terje Røsten
Hi again! For future reference what is the output from: $ rpm -qf /etc/my.cnf on that system?
[12 Apr 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
