MySQL Bugs: #54256: Incorrect detection of the mysql startup script on Ubuntu

Bug #54256	Incorrect detection of the mysql startup script on Ubuntu
Submitted:	5 Jun 2010 16:20	Modified:	10 Jun 2010 0:22
Reporter:	David Glasser	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S3 (Non-critical)
Version:	5.2.22RC	OS:	Linux (Ubuntu 10.04 (Server))
Assigned to:		CPU Architecture:	Any

Description:
New server instance wizard can't find correct start-up script for the MySQL instance on Ubuntu 10.04 Server Edition. This is similar to bug 51802.

How to repeat:
1. Go to New server instance
2. Click next (will create instance for localhost)
3. Provide user name and password
4. Click next
5. Set MySQL installation type Ubuntu Linux (Vendor Package)
6. Click next
7. Receive error: Operation failed: /etc/init.d/mysql start is invalid

Thank you for the bug report. Which server version are you using?. I couldn't repeat on Ubuntu 10.04 X86_64 and server 5.1.41 (installed with apt-get). Thanks in advance.

mysql> SELECT VERSION();
+--------------------+
| VERSION()          |
+--------------------+
| 5.1.41-3ubuntu12.1 |
+--------------------+
1 row in set (0.00 sec)

lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 10.04 LTS
Release:	10.04
Codename:	lucid

I'm wondering if this is a problem with how I'm connecting. I've basically set up an ssh tunnel from my box to the mysql server. In the connection profile I've selected Standard TCP/IP with the root username and password of the mysql server. I then connect to the localhost (because I have the port forwarded). Using this connection profile I can make queries just fine. 

I'm wondering what exactly MySQL Workbench is doing in the "Server Administration" section. Do I need to have MySQL Workbench ssh to the server with the root password of the ubuntu box for this to work? I've disabled root access as this seems like a security risk.

...
5. Set MySQL installation type Ubuntu Linux (Vendor Package)
6. Click next
7. Receive error: Operation failed: /etc/init.d/mysql start is invalid

When you click next here you will get the window where you can configure your start script.

If your start script is different from /etc/init.d/mysql then it is totally ok that the first check will fail.

After you configured the right start script that you are using all will work fine.

I believe this is just a file permission issue because I'm not connecting to the server as root.