Bug 904061
Summary: | missing logrotate script | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Karel Volný <kvolny> |
Component: | mysql | Assignee: | Honza Horak <hhorak> |
Status: | CLOSED ERRATA | QA Contact: | qe-baseos-daemons |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 6.4 | CC: | azelinka, byte, hhorak, lnovich, ovasik, prabhakar_pujeri, praiskup, thomas_chenault |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | mysql-5.1.71-1.el6 | Doc Type: | Bug Fix |
Doc Text: |
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
|
Story Points: | --- |
Clone Of: | 904059 | Environment: | |
Last Closed: | 2013-11-21 20:41:09 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 904059 | ||
Bug Blocks: | 960054 |
Description
Karel Volný
2013-01-25 11:56:00 UTC
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 |