Bug #35098 mysql start with MySQL/etc/init.d/mysql: line 159: kill
Submitted: 6 Mar 2008 9:31 Modified: 6 Mar 2008 19:18
Reporter: Steven Foo Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Server Severity:S2 (Serious)
Version:Redhat EL4 OS:Linux
Assigned to: CPU Architecture:Any
Tags: MySQL/etc/init.d/mysql: line 159: kill

[6 Mar 2008 9:31] Steven Foo
I am having the same issue as well.

Starting MySQL/etc/init.d/mysql: line 159: kill: (24684) - No such process

I am using the below:

Linux server1 2.6.9-42.ELsmp #1 SMP Wed Jul 12 23:27:17 EDT 2006 i686 i686 i386 GNU/Linux


I can start with mysqld_safe. However it is using the file my.conf.

mysqld is reading my.cnf.

Any ideas how to resolved the error MySQL/etc/init.d/mysql: line 159: kill?

I read so many search result from google and etc. but found no solution.


How to repeat:
The issue happen when start the mysql server.

/etc/init.d/mysql start
service mysql start
[6 Mar 2008 10:36] Steven Foo
I have disable the SELinux and able to start with mysql start.

However it is with /etc/my.conf only.
If I change it to my.cnf, it will failed. The file /etc/my.cnf must not exist.

I then tried to use the MySQL Administrator GUI to see the startup parameter.
Some of the parameter is still grey off.
All basedir, datadir, tempdir, default storage engine and etc is specify in the my.conf however they are grey off. Other parameters are able to modify.

I wonder why mysql start my.cnf with error whereis my.conf is fine.
Also some my.conf parameter is grey off in MySQL Administrator GUI no doubt the value is specify in the my.conf file.

Kindly advice.
[6 Mar 2008 19:18] Sveta Smirnova
Please do not submit the same bug more than once. An existing bug report 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.

Duplicate of bug #29595