Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1058719 - MySQL server does not restart after unclean reboot
MySQL server does not restart after unclean reboot
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: mysql (Show other bugs)
6.5
Unspecified Unspecified
urgent Severity urgent
: rc
: ---
Assigned To: Honza Horak
qe-baseos-daemons
: Patch, Regression, ZStream
Depends On: 1037650 1064862
Blocks:
  Show dependency treegraph
 
Reported: 2014-01-28 07:24 EST by Libor Miksik
Modified: 2016-04-26 09:59 EDT (History)
18 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: MySQL socket was checked for existence, but it was not checked if any process uses it. Consequence: If a server crashed, it couldn't be started again. Fix: Existence of MySQL socket is ignored in case no process uses it. Result: Server can be restarted after crash.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-02-12 13:24:48 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2014:0164 normal SHIPPED_LIVE Moderate: mysql security and bug fix update 2014-02-12 18:22:48 EST

  None (edit)
Description Libor Miksik 2014-01-28 07:24:26 EST
This bug has been copied from bug #1037650 and has been proposed
to be backported to 6.5 z-stream (EUS).
Comment 5 Honza Horak 2014-01-28 11:59:11 EST
How to test:
1. service mysqld start
2. killall -9 mysqld_safe mysqld
3. service mysqld start
4. echo $?

Actual results:
1
Service doesn't start

Expected results:
0
Service starts
Comment 9 errata-xmlrpc 2014-02-12 13:24:48 EST
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.

http://rhn.redhat.com/errata/RHSA-2014-0164.html

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