MySQL Bugs: #55668: Workbench freezes when starting server

Bug #55668	Workbench freezes when starting server
Submitted:	1 Aug 2010 0:21	Modified:	17 Sep 2010 15:24
Reporter:	Abhijit Sarkar	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S3 (Non-critical)
Version:	mysql-workbench-5.2.25-win32-noinstall, 5.2.26	OS:	Windows (Vista Business SP 2 64-bit OS)
Assigned to:		CPU Architecture:	Any

Description:
Using mysql-noinstall-5.1.49-winx64 with mysql-workbench-gpl-5.2.25-win32-noinstall.
Workbench freezes when attempting to start server. Same command from the server_install\bin directory works. Server shutdown works from workbench.
---------------------------------------------------------------------------
Command Line
---------------------------------------------------------------------------
C:\Program Files\mysql-5.1.49\bin>mysqld --user=appadmin --console=true
100731 20:11:31 [Note] Plugin 'FEDERATED' is disabled.
100731 20:11:32  InnoDB: Started; log sequence number 0 44233
100731 20:11:32 [Note] Event Scheduler: Loaded 0 events
100731 20:11:32 [Note] mysqld: ready for connections.
Version: '5.1.49-community'  socket: ''  port: 3306  MySQL Community Server (GPL)

---------------------------------------------------------------------------
Workbench
---------------------------------------------------------------------------
"C:\Program Files\mysql-5.1.49\bin\mysqld" --user=appadmin --console=true
Freezes indefinitely.

"C:\Program Files\mysql-5.1.49\bin\mysqladmin" --user=appadmin --password=xxx shutdown
Works.

How to repeat:
1. Double click "MySQLWorkbench.exe".
2. Double click a Server instance. "mysqld@localhost" in my case.
3. Click on "Continue Anyway" when prompted for.
4. Click on "Start Server".
5. Hope (in vain) that the workbench would be responsive and does not freeze.

Suggested fix:
Nothing that I am aware of.

Are there more then one server running?

No, only one server instance is running. As I mentioned in the bug report, startup works from the command line.

I couldn't repeat on Vista X86_64.

When you created the instance in Workbench ... what did you fill as startup command?

Did you fill mysqld for startup and mysqladmin shutdown for stopping the daemon?

Susanne Ebrecht wrote:
> Did you fill mysqld for startup and mysqladmin shutdown for stopping
> the daemon?

Yes I did. If you look at my bug report, I have already put those commands in it. I am repeating them for your convenience:
"C:\Program Files\mysql-5.1.49\bin\mysqld" --user=appadmin --console=true
"C:\Program Files\mysql-5.1.49\bin\mysqladmin" --user=appadmin --password=xxx shutdown

Thank you for the feedback.

Verified as described on 32-bit Vista Business.

Hm... In my case froze was because hidden under open WB window UAC dialog. Do you have UAC turned on? Please check if you experience this issue because such dialog too.

@Sveta:
"Verified as described on 32-bit Vista Business."
Correction, mine is 64-bit Vista Business.

"Do you have UAC turned on"?
I think I do. I have tried running it with "always run as administrator" option without any luck. I get the popup, accept it and guess what? Nothing happens.

Hi

You are not supposed to make WB call mysqld.exe directly, it should be started/stopped using the Windows services interface. Calling mysqld directly will not only make it hang (as you've noticed), but it will probably also kill the server when WB exits. Please either use the Windows services interface instance that was created by the MySQL server installation or create one. Usually, the commands used to start/stop MySQL from WB is something like: "sc start mysql" and "sc stop mysql"

Alfredo,
Do you think that MySQL should be installed as a Windows service? Or are you only asking me to use the Windows service interface?
Personally I am avert to installing anything as a Windows service.

Workbench is designed to use service on Windows. Adding some way to start server without adding service is a new feature request.

The fact that there exists a choice to install (or not install) the WB as a Windows service suggests that it should work both ways. I am not convinced that there exists options but only one of them works and making the other work is a feature request. I think we should agree that this is a bug and put this in the list of known issues. Whether or not it will be fixed now is a question to the MySQL team.

Workbench requires the server to have a service set up for it. If a user installs the server from a zip, it is expected that they create the service manually, otherwise the MSI server package should be used. Server installation is not in the scope of Workbench.

> [17 Sep 17:18] Alfredo Kojima
"Server installation is not in the scope of Workbench.".
There seems to be a misinterpretation. I am saying that the WB should not be necessarily installed as a Windows service. Even if not installed as a Windows service, it should be able to start and stop an existing installation of the server.