Bug 1482122 - Test case failure: /CoreOS/mysql/Regression/bz1149143-mysql-general-log-doesn-t-work-with-FIFO-file
Summary: Test case failure: /CoreOS/mysql/Regression/bz1149143-mysql-general-log-doesn...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Software Collections
Classification: Red Hat
Component: mysql
Version: rh-mysql56
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: alpha
: 2.4
Assignee: Honza Horak
QA Contact: Karel Volný
URL:
Whiteboard:
Depends On:
Blocks: 1445537
TreeView+ depends on / blocked
 
Reported: 2017-08-16 13:55 UTC by Karel Volný
Modified: 2017-09-21 07:42 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-09-21 07:42:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
proposed patch (860 bytes, patch)
2017-08-16 14:28 UTC, Honza Horak
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2787 0 normal SHIPPED_LIVE Important: rh-mysql56-mysql security and bug fix update 2017-09-21 11:42:12 UTC

Description Karel Volný 2017-08-16 13:55:24 UTC
the file /etc/opt/rh/rh-mysql56/my.cnf.d/mysql-server.cnf specifies
log-error=/var/opt/rh/rh-mysql56/log/mysql/mysqld.log

this is not a problem in default configuration, as the file gets created on service startup

however, if you change log path to something else, e.g. like

[mysqld]
general_log=1
general_log_file=/var/opt/rh/rh-mysql56/log/mysql/mysqld.fifo

and delete the file 'mysqld.log', then service startup then fails as the general_log_file path is checked/gets created if needed and not the error-log path

this is regression from previous version, as both files were touched before running mysqld_safe, and this was dropped from scripts, leaving it upon mysqld_safe

Comment 1 Honza Horak 2017-08-16 14:28:53 UTC
Created attachment 1314225 [details]
proposed patch

There is one line in mysqld_safe that was not converted into SCL-ized path, which seems like causing these troubles.

Comment 5 Karel Volný 2017-08-23 14:31:44 UTC
ahem, this is in RHSA-2017:28374 which is 2.4.z but has target 3.0 ... trying to correct

note that also 3.0 branches commits are referred but it got fixed in the new 2.4 build

Comment 9 errata-xmlrpc 2017-09-21 07:42:41 UTC
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.

https://access.redhat.com/errata/RHSA-2017:2787


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