Mysql is not using /etc/my.cnf

Have you looked to see if the 'user' has a separate 'my.cnf' file?

Hello Tomas,

 
[root@ ~]#mysql --help | grep "Default options" -A 1
Default options are read from the following files in the given order:
/etc/mysql/my.cnf /etc/my.cnf ~/.my.cnf
[root@ ~]#cat /etc/mysql/my.cnf
cat: /etc/mysql/my.cnf: No such file or directory
[root@ ~]# cat ~/.my.cnf
cat: /root/.my.cnf: No such file or directory
[mysql@ ~]# cat ~/.my.cnf
cat: /home/mysql/.my.cnf: No such file or directory

Select allOpen in new window

rebooted the machine, but still the same thing :( . any other suggestions??

I followed your suggestion to fix open files and it worked perfectly. Thanks

Regards,

Hi!

The command

locate my.cnf

Select allOpen in new window

(issued as root) should give you all my.cnf files on your host.
Note that if you don't find any my.cnf on the default paths then you can always create one (in the /etc/ path ) and configure the system parameters you want to differ from default. :)

Regards,
      Tomas Helgi

Hi,
I do have a my.cnf  file under /etc/ where I specified all the configuration . it's just I don't understand why root user uses the /etc/my.cnf and mysql user uses something else which I don't seem to find.!!

Thanks

Hi!

The default location for the my.cnf is usually in the /etc folder where the mysql user (user running the deamon) accesses it.


Regards,
     Tomas Helgi

Hi,
both commands return nothing

[root@~]# ps -ef | grep mysql | grep "defaults-file"
[root@~]#

Select allOpen in new window

[root@ ~]# mysql --print-defaults
mysql would have been started with the following arguments:

[root@ ~]#

Select allOpen in new window

I've requested that this question be closed as follows:

Accepted answer: 0 points for CCVOIP's comment #a41135975
Assisted answer: 250 points for TomasHelgi's comment #a41104064
Assisted answer: 250 points for TomasHelgi's comment #a41134047

for the following reason:

thank you all for your responses. but still having the same issue!!

Thanks all for your response. but I still have the same issue!!!