Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

CentOS 5.5 MySQL 5.5 installed via a yum repository

[ERROR] Could not use /var/log/mysqld.slow.log for logging (error 13). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.

Using a standard install of MySQL 5.5 (specifically from the webtatic repository), the slow query log cannot start actually recording due to a permissions issue. If I pre-create a copy and chown it to belong to user:mysql and group:mysql, then it works fine.

In the very same directory (/var/log), it has no problems creating and logging to mysql.log and mysql.error.log.

Obviously I have a hackish fix for it, but I'd like to be able to use logrotate on it, without additionally requiring logrotate to repeat the hackery too. (The only thing worse than hackery is having to repeat hackery.)

Does anyone know what the best practice is for fixing this?

share|improve this question
    
I like the "sysadmin's wisdom" style of the bracketed sentence :) –  the-wabbit Jun 10 '11 at 7:16

2 Answers 2

up vote 3 down vote accepted

It sounds like the mysql process (mysqld_safe, I believe) is unable to create the log file after you use logrotate to move it out of the way and send a HUP? If I'm way off here, let me know.

Assuming I'm not way off, there are a few options here:

  • Move the log to a directory owned by the same user as the mysqld_safe process. For example, create a /var/log/mysqld/ directory and save the logfiles there. If the directory is mysql:mysql 700 then new files can be created without an issue.
  • Use the copy/truncate logrotate method instead of the move/SIGHUP method. The copy/truncate method will copy the current log files (mysqld.slow.log) to a new file (mysqld.slow.log.1) then truncate the original file to zero bytes. This is useful if you don't want to interrupt the process that is writing to the log for some reason. The downside, of course, is that there is additional disk overhead with copying the original file to a new file before wiping the original file back to zero bytes. This is done by adding the copytruncate option to the logrotate stanza for that file and removing the no-longer-required postrotate section.
share|improve this answer

You can also use the create option of logrotate to create the log file after rotating out the old log file. The only thing you will need after that is a postrotate script that calls a mysqladmin flush-logs (remember -u and -p if you have a username/password that you want to use for maintenance.) This should save you the overhead of the duplication of the log file in case it gets big.

Either way should be good though: create or copytruncate. Aside from the space requirements, I don't know of any advantage of one over the other.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.