Red Hat Bugzilla – Bug 435494
Timeout error starting MySQL when using non-default socket file value (fix provided)
Last modified: 2015-02-20 10:03:25 EST
Description of problem:
If a new socket file that is not the default value is specified in /etc/my.cnf,
the MySQL service will give the following error on start, even though it has
Starting MySQL: [FAILED]
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. change the socketfile to a nondefault value in /my.cnf
2. run "service mysqld start"
the daemon starts but the "service" command fails with a timeout because the
pinging is incorrectly done.
ping should be done correctly, and "service" should return succesfully
This is an easy fix, replace the following line:
RESPONSE=`/usr/bin/mysqladmin -uUNKNOWN_MYSQL_USER ping 2>&1` && break
RESPONSE=`/usr/bin/mysqladmin -S$socketfile -uUNKNOWN_MYSQL_USER ping 2>&1` &&
I forgot to mention that the last fix has to be applied to the startup script: /
I've applied this fix in Fedora devel (so it'll be in F9, and probably also in the next F8 or F7 spins). I can't
promise much about when it'll get into RHEL5 though.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.