Bug 750107 - Packaging: mysql-server logfile is marked as a "configuration file"
Summary: Packaging: mysql-server logfile is marked as a "configuration file"
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: mysql
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Michal Schorm
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 947775 1070830 1159820
TreeView+ depends on / blocked
 
Reported: 2011-10-31 01:55 UTC by David Tonhofer
Modified: 2017-04-12 10:19 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-07 19:18:04 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description David Tonhofer 2011-10-31 01:55:30 UTC
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 2 RHEL 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.

Comment 3 Tom Lane 2011-10-31 03:07:28 UTC
It's not apparent to me exactly what you think the problem is?  mysqld.log is supposed to be marked that way, per advice going back to bug #102190.

Comment 4 David Tonhofer 2011-10-31 07:40:39 UTC
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

Comment 5 Tom Lane 2011-10-31 14:06:52 UTC
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.

Comment 7 Jon Dufresne 2014-08-19 14:12:00 UTC
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.)

Comment 8 Honza Horak 2014-08-19 15:06:02 UTC
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


Note You need to log in before you can comment on or make changes to this bug.