MySQL Bugs: #20117: YaST2's run level editor can't detect status of mysql

Bug #20117	YaST2's run level editor can't detect status of mysql
Submitted:	29 May 2006 7:54	Modified:	31 May 2006 20:54
Reporter:	Miles Barry	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Command-line Clients	Severity:	S4 (Feature request)
Version:	5.0.21-1	OS:	Linux (SLES9)
Assigned to:		CPU Architecture:	Any

Description:
We are using 5.0.21-1 SLES9 x86-64 RPM packages by Lenz Grimmer, downloaded directly off the mysql download section.

puigmal:/var/lib/mysql # /etc/init.d/mysql status
Usage: /etc/init.d/mysql start|stop|restart|reload
puigmal:/var/lib/mysql #

As the init script does not contain a status function, when in YaST2 Run Level Editor, which scans all the daemons and reports the status, it can't display the status of the MySQL server daemon.

It would be very nice to see this fixed within the package.

Kind regards

Miles

How to repeat:
Enter YaST2

System -> Runlevel Editor -> Expert Mode -> mysql -> Refresh Status

You will see:

/etc/init.d/mysql status returned 1 (program is dead and /var/run pid file exists):

Usage: /etc/init.d/mysql start|stop|restart|reload

Note that that is when I have mysql server running also...

Suggested fix:
Add the status function to the /etc/init.d/mysql

Which method of user/password authentification do you use? NIS, LDAP or something else? I suspect this is a problem in the order in which processes are started at bootup. It almost looks as if some required service is not available at the time MySQL is started.

What command do you use to start the server from the shell afterwards?

Please disregard the previous comment - wrong bug :)

LDAP is the auth backend.

I use /etc/init.d/mysql to start the service manually or rcmysql.

Now you come to mention it, I'm going to look at the boot log and see if LDAP was down, but the mysql user and group are system, and not in the ldap tree.

...

MySQL starts after ldap, directly after it.

Regards

Miles

Looks like a reasonable feature request for me. /etc/init.d/mysql script should recognize and properly process "status" parameter.