Bug #92414 mysql 5.7 does not start on [re]boot of genuine RHEL7.5
Submitted: 13 Sep 2018 21:23 Modified: 14 Sep 2018 4:39
Reporter: Steven Jones Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Installing Severity:S1 (Critical)
Version:5.7.23-1.el7.x86_64 OS:Red Hat (7.5)
Assigned to: CPU Architecture:x86

[13 Sep 2018 21:23] Steven Jones 
Description:
mysql 5.7 does not start on [re-]boot as the sub-directory /var/run/mysql does not get created and hence the pid file cannot be written into it. The mysqld then shuts down. 

How to repeat:
I have this occurring on 3 brand new RHEL7.5 servers.

Turned off selinux no difference.

Contacted Redhat support they refuse to help stating its a mysql problem.

Suggested fix:
None known
[13 Sep 2018 21:25] Steven Jones 
Also cannot do a systemctl start mysqld either.  The Q is why isnt the mysql start script creating this directory?
[14 Sep 2018 4:39] MySQL Verification Team 
Hello Steven,

Please do not submit the same bug more than once. An existing bug report Bug #92016 already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

regards,
Umesh