Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Cause:
Packaging issue, wrongly expanded macro containing patch to the MySQL server log file in the log-rotate file.
Consequence:
The file-path to the default location of the MySQL server log file is set wrong.
The log-rotation of the MySQL server does not wok out-of-the-box.
Fix:
Use a correct (different) source file from which the log-rotate configuration file is generated.
Result:
The log-rotate file now contains the correct file-path to the default location of the MySQL server log file.
! HOWEVER !
The whole configuration file is now commented out. That is a default state of the log-rotate configuration file intended by upstream
That means (both before and after this fix) the user action is required in order for the log-rotate to be working.
Description of problem:
Default target of logrotate script does not match log location in default configuration. This means logrotate does not work out of the box.
Version-Release number of selected component (if applicable):
mysql-server-8.0.28-1.el9.x86_64
How reproducible:
always
Steps to Reproduce:
1. cat /etc/logrotate.d/mysqld
2. cat /etc/my.cnf.d/mysql-server.cnf
3.
Actual results:
<snip logrotate>
/var/lib/mysql/mysqld.log {
</snip>
<snip mysql-server.cnf>
log-error=/var/log/mysql/mysqld.log
</snip>
Expected results:
Files match.
Additional info:
PR for Fedora:
https://src.fedoraproject.org/rpms/community-mysql/pull-request/10
However, I'm not sure the fix shouldn't be about using a different file instead -- I see we have two:
* mysql-8.0.28/support-files/mysql-log-rotate.in (this one is used)
* mysql-8.0.28/packaging/rpm-common/mysql.logrotate.in (this one looks like relevant for the RPM)
Description of problem: Default target of logrotate script does not match log location in default configuration. This means logrotate does not work out of the box. Version-Release number of selected component (if applicable): mysql-server-8.0.28-1.el9.x86_64 How reproducible: always Steps to Reproduce: 1. cat /etc/logrotate.d/mysqld 2. cat /etc/my.cnf.d/mysql-server.cnf 3. Actual results: <snip logrotate> /var/lib/mysql/mysqld.log { </snip> <snip mysql-server.cnf> log-error=/var/log/mysql/mysqld.log </snip> Expected results: Files match. Additional info: