MySQL Bugs: #48019: init.d fails to start MySQL directly

Bug #48019	init.d fails to start MySQL directly
Submitted:	13 Oct 2009 9:48	Modified:	13 Nov 2009 17:03
Reporter:	Abhishek Kumar	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: General	Severity:	S3 (Non-critical)
Version:	5.1.37	OS:	Linux (Fedora Core 8)
Assigned to:		CPU Architecture:	Any
Tags:	init.d startup

Description:
MySQL does not start automatically. The init script fails with error "Manager of pid-file quit without updating file.". 

Upon further investigation, it was found that mysqld_safe script starts mysqld but it exits almost instantaneously. The error logs contains the following:-

091008 19:38:26 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
091008 19:38:28 mysqld_safe mysqld from pid file /var/lib/mysql/arthur.pid ended

A workaround is to start the init script from sh, i.e. execute "sh /etc/init.d/mysql start". 

How to repeat:
Install mysql on Fedora Core 8 and restart.

Please see bug: http://bugs.mysql.com/bug.php?id=44492 if your same case. Thanks in advance.

This problem is different from http://bugs.mysql.com/bug.php?id=44492. Even after removing the pid file and the lock file (/var/lock/subsys/mysql) the problem remains the same. I am unable to get any more verbose error information than what I have provided in the description. Let me know if any command line options to mysqld_safe / mysqld can be used to get more verbose error information.

Please, try to repeat with a newer version, 5.1.39, and inform about the results.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".