Cause: Logrotate script was missing in mysql-server
Consequence: Logs rotation had to be configured manually
Fix: mysql-server provides logrotate script now
Result: users can use logrotate to log their mysqld.log file after un-commenting lines in the logrotate script
+++ This bug was initially created as a clone of Bug #904059 +++
Description of problem:
Mysql packages do not provide logrotate configuration file.
Looking at bug #647223 comment #16 I understand that as it should be included after the problem with rotating logs gets fixed. The problem got fixed already but we still do not provide /etc/logrotate.d/mysqld
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. yum install mysql-server
2. uncomment the configuration in /etc/logrotate.d/mysqld
3. logrotate -f /etc/logrotate.d/mysqld
2. no file to edit
3. error: cannot stat /etc/logrotate.d/mysqld: No such file or directory
no error; once the server runs and writes logfile, logs get rotated after logrotate call
It looks like we fixed this in Fedora and RHEL5, but the fix never made it into the RHEL6 branch ... which makes this a regression from RHEL5 to RHEL6. Oops.
How to reproduce:
1) (uncomment related lines in /etc/logrotate.d/mysqld)
2) # logrotate /etc/logrotate.d/mysqld -f
3) # echo $?
4) # ls -l /var/log/mysqld.log*
error: cannot stat /etc/logrotate.d/mysqld: No such file or directory
-rw-r-----. 1 mysql mysql 25910 Aug 9 10:07 /var/log/mysqld.log
-rw-r-----. 1 mysql mysql 0 Aug 9 10:14 /var/log/mysqld.log
-rw-r-----. 1 mysql mysql 2546 Aug 9 10:14 /var/log/mysqld.log.1.gz
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.