Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1482122 - Test case failure: /CoreOS/mysql/Regression/bz1149143-mysql-general-log-doesn-t-work-with-FIFO-file
Test case failure: /CoreOS/mysql/Regression/bz1149143-mysql-general-log-doesn...
Status: CLOSED ERRATA
Product: Red Hat Software Collections
Classification: Red Hat
Component: mysql (Show other bugs)
rh-mysql56
Unspecified Linux
unspecified Severity unspecified
: alpha
: 2.4
Assigned To: Honza Horak
Karel Volný
:
Depends On:
Blocks: 1445537
  Show dependency treegraph
 
Reported: 2017-08-16 09:55 EDT by Karel Volný
Modified: 2017-09-21 03:42 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-09-21 03:42:41 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


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


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2787 normal SHIPPED_LIVE Important: rh-mysql56-mysql security and bug fix update 2017-09-21 07:42:12 EDT

  None (edit)
Description Karel Volný 2017-08-16 09:55:24 EDT
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 10:28 EDT
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 10:31:44 EDT
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 03:42:41 EDT
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.