Bug 1482122

Summary: Test case failure: /CoreOS/mysql/Regression/bz1149143-mysql-general-log-doesn-t-work-with-FIFO-file
Product: Red Hat Software Collections Reporter: Karel Volný <kvolny>
Component: mysqlAssignee: Honza Horak <hhorak>
Status: CLOSED ERRATA QA Contact: Karel Volný <kvolny>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rh-mysql56CC: databases-maint, hhorak, mmuzila
Target Milestone: alpha   
Target Release: 2.4   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
undefined
 Story Points: ---
Clone Of: Environment:
Last Closed: 2017-09-21 07:42:41 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:    
Bug Blocks: 1445537    
Attachments:
Description Flags
proposed patch none

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