Bug 1281370

Summary: MySql is crashing in reload_acl_and_cache at the time of calling rotate_relay_log.
Product: Red Hat Enterprise Linux 6 Reporter: Mohit Agrawal <moagrawa>
Component: mysqlAssignee: Jakub Dorňák <jdornak>
Status: CLOSED ERRATA QA Contact: Karel Volný <kvolny>
Severity: medium Docs Contact:
Priority: urgent    
Version: 6.8CC: byte, databases-maint, fkrska, hhorak, jdornak, kfujii, moagrawa, psklenar
Target Milestone: rcKeywords: Patch, ZStream
Target Release: 6.8   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, when the rotate_relay_log() function was called, an unresolved concurrent access to a shared resource occurred. As a consequence, MySQL terminated unexpectedly with a segmentation fault. To fix this bug, a mutex lock on the resource is now used during the rotate_relay_log() call, and MySQL no longer crashes in this scenario.
 Story Points: ---
Clone Of:
: 1312274 (view as bug list) Environment:
Last Closed: 2016-05-11 01:34:17 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: 1312274    
Attachments:
Description Flags
backtrace of all mysqld threads at the time of crash none

Description Mohit Agrawal 2015-11-12 12:02:17 UTC 
Description of problem:
MySql is crashing in reload_acl_and_cache at the time of calling rotate_relay_log.

Version-Release number of selected component (if applicable):
mysql-server-5.1.73-3.el6_5.x86_64
mysql-5.1.73-3.el6_5.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
Mysql is crashing.

Expected results:
MySql should not crash.

Additional info:
Comment 2 Mohit Agrawal 2015-11-12 12:08:33 UTC 
Created attachment 1093219 [details]
backtrace of all mysqld threads at the time of crash
Comment 17 errata-xmlrpc 2016-05-11 01:34:17 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://rhn.redhat.com/errata/RHBA-2016-0979.html