Bug 1327714

Summary: mysql cartridge removes logs on start
Product: OKD Reporter: Andy Grimm <agrimm>
Component: ImageAssignee: Vu Dinh <vdinh>
Status: CLOSED WONTFIX QA Contact: XiuJuan Wang <xiuwang>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.xCC: aos-bugs, jgoulding, mmccomas, wzheng
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: After the MySQL cartridge is successfully started, the log is automatically removed as a part of control script. Consequence: The log file is gone and no way to recover it. If there are errors occurred before the cartridge is started, the error log will be lost. This issue makes the debugging process difficult. Fix: The code that is responsible for log file removal is removed from the control script. Result: The log file will persist after the cartridge is started.
Story Points: ---
Clone Of:
: 1361307 (view as bug list) Environment:
Last Closed: 2017-05-31 18:22:11 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:
Bug Depends On:    
Bug Blocks: 1277547, 1361307    

Description Andy Grimm 2016-04-15 17:32:53 UTC
Currently the "start" function in the control script of the mysql cartridge removes the mysql.log, which often makes it impossible for users to find the root cause of an outage.

Comment 1 openshift-github-bot 2016-04-15 21:26:40 UTC
Commit pushed to master at https://github.com/openshift/origin-server

https://github.com/openshift/origin-server/commit/05b750de48ade4717faa86ed01d1c3ee79512c7e
Bug 1327714: MySQL cartridge removes logs on start

The "start" function of start script of the MySQL cartridge removes the
mysql.log which is supposed to save some disk space. However, since the
log file is removed, it's very difficult, if not impossible, for users
to debug any issues with MySQL database.

Since the log file removal is unnecessary, the code that is responsible
for that is now removed. As a result, the mysql.log file will remain
after the "start" function in control script is called. Also, replace
an error-log dump with a static message to instruct users to check
mysql.log for errors.

Bug: 1327714
Link: <https://bugzilla.redhat.com/show_bug.cgi?id=1327714>

Signed-off-by: Vu Dinh <vdinh>

Comment 2 XiuJuan Wang 2016-04-25 10:14:28 UTC
Verified in devenv_5785

Feature works in mysql-5.1 and mysql-5.5, could save the mysql.log under $OPENSHIFT_LOG_DIR

Comment 4 Eric Paris 2017-05-31 18:22:11 UTC
We apologize, however, we do not plan to address this report at this time. The majority of our active development is for the v3 version of OpenShift. If you would like for Red Hat to reconsider this decision, please reach out to your support representative. We are very sorry for any inconvenience this may cause.