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.
Description of problem:
=======================
# rpm --query --verify mysql-server
missing c /var/log/mysqld.log <--- Should not care about this
Version-Release number
======================
mysql-server-5.1.52-1.el6_0.1.x86_64
Comment 2RHEL Program Management
2011-10-31 02:28:28 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Unfortunately,
"You are not authorized to access bug #102190"
The problem is that you get a package verification warning when the log file is missing - which happens because MySQL may have been configured to log some other file, this is the case on our installations for example. After all, it's just a logfile.
Compare with httpd or syslog - No complains on "missing logfiles" here.
Best regards,
-- David
Well, the file is created by installing the RPM, so the only way you'd get such a message is if you manually removed the file ... and I see nothing particularly wrong with that.
Is this why I sometimes have a file "/var/log/mysqld.log.rpmnew" after a yum update? This file is always empty. Other log files do not do this. The existence of the rpmnew file creates maintenance overhead for me as I need to analyze if any change in a _config_ is required. (In this case it should simply be deleted.)
There is quite good summary of the log files issue at:
http://fedoraproject.org/wiki/PackagingDrafts/Logfiles
And since the mysqld log file should be owned by mysql user, the following seems like a best we can do (now used in Fedora):
%attr(0640,mysql,mysql) %config %ghost %verify(not md5 size mtime) /var/log/mysqld.log