Bug #74111 When the socket option is relative, mysqld startup script fails on CentOS 6.
Submitted: 26 Sep 2014 16:01 Modified: 28 Oct 2014 22:14
Reporter: Jean-François Gagné Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Errors Severity:S3 (Non-critical)
Version:5.7.5/5.6 OS:Linux (CentOS 6.5)
Assigned to: CPU Architecture:Any

[26 Sep 2014 16:01] Jean-François Gagné 
Description:
When the socket option is relative in my.cnf, the CentOS startup script print the following message:

Timeout error occurred trying to start MySQL Daemon.

But MySQL is started.

How to repeat:
Set the socket option in my.cnf to a relative path, and do "service mysqld start".
[7 Oct 2014 20:34] MySQL Verification Team 
[root@tikal miguel]# service mysqld start
Timeout error occurred trying to start MySQL Daemon.
Starting mysqld:                                           [FAILED]
[root@tikal miguel]#
[7 Oct 2014 20:59] MySQL Verification Team 
Thank you for the bug report.
[28 Oct 2014 22:14] Paul DuBois 
Noted in 5.5.41, 5.6.22, 5.7.6 changelogs.

On CentOS 6, specifying a relative path name for the --socket option
caused MySQL startup script failure.
[3 Dec 2014 15:20] Laurynas Biveinis 
$ bzr log -r 4729
------------------------------------------------------------
revno: 4729
committer: Balasubramanian Kandasamy <balasubramanian.kandasamy@oracle.com>
branch nick: mysql-5.5
timestamp: Tue 2014-10-21 14:48:58 +0200
message:
  Bug#19775856: When the socket option is relative, mysqld startup script fails on CentOS 6