RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

+++ 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):
mysql-5.0.95-5.el5_9

How reproducible:
always

Steps to Reproduce:
1. yum install mysql-server
2. uncomment the configuration in /etc/logrotate.d/mysqld
3. logrotate -f /etc/logrotate.d/mysqld

Actual results:
2. no file to edit
3. error: cannot stat /etc/logrotate.d/mysqld: No such file or directory

Expected results:
no error; once the server runs and writes logfile, logs get rotated after logrotate call

Additional info:

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*

Actual results:
error: cannot stat /etc/logrotate.d/mysqld: No such file or directory
1
-rw-r-----. 1 mysql mysql 25910 Aug  9 10:07 /var/log/mysqld.log

Expected results:
0
-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.

http://rhn.redhat.com/errata/RHBA-2013-1647.html