Bug #72880 After upgrade of Workbench - Server will not load

• Submitted: 4 Jun 2014 17:07
• Modified: 7 Jan 2015 15:09
• Reporter: Paul Cunningham
• Status: Can't repeat
• Category: MySQL Workbench: Administration
• Severity: S5 (Performance)
• Version: 6.1.6
• OS: Windows (Microsoft build 9200, 64-bit)
• CPU Architecture: Any
• Tags: WBBugReporter

[4 Jun 2014 17:07] Paul Cunningham

Description:
----[For better reports, please attach the log file after submitting. You can find it in C:\Users\pacunningham\AppData\Roaming\MySQL\Workbench/log/wb.log]
****************************************************
***********************************************
Here is message from start server
2014-06-04 09:55:49 - Workbench will use cmd shell commands to start/stop this instance
2014-06-04 09:56:01 - Starting server...
2014-06-04 09:56:09 - Checking server status...
2014-06-04 09:56:09 - Trying to connect to MySQL...
2014-06-04 09:56:10 - Can't connect to MySQL server on '127.0.0.1' (10061) (2003)
2014-06-04 09:56:10 - Assuming server is not running
2014-06-04 09:56:10 - Server start done.
2014-06-04 09:56:10 - Checking server status...
2014-06-04 09:56:10 - Trying to connect to MySQL...
2014-06-04 09:56:11 - Can't connect to MySQL server on '127.0.0.1' (10061) (2003)
2014-06-04 09:56:11 - Assuming server is not running

How to repeat:
Opening the server

[4 Jun 2014 17:09] Paul Cunningham

Log file

Attachment: wb.log (application/octet-stream, text), 8.29 KiB.

[5 Jun 2014 11:42] MySQL Verification Team

Start failed

Attachment: 000_start.png (image/png, text), 90.56 KiB.

[5 Jun 2014 11:43] MySQL Verification Team

Thank you for the bug report.

[5 Jun 2014 11:45] MySQL Verification Team

As workaround use the Control Panel Local Service to start/stop the server.
Thanks.

[5 Jun 2014 15:27] Paul Cunningham

Responding to suggetion to start from ontrol panel

Attachment: Windows error on trying to start Local Service.JPG (image/jpeg, text), 29.31 KiB.

[5 Jun 2014 15:50] MySQL Verification Team

Please look in your err file the message error which provoked the quit. Most
probably you should find the *.err file at "C:\ProgramData\MySQL\MySQL Server 5.6\data". Print here the error message.

[27 Jun 2014 0:08] MySQL Verification Team

Service setup is OK

Attachment: 0001_start_done_on_cmd.png (image/png, text), 132.70 KiB.

[1 Sep 2014 1:28] MySQL Verification Team

http://bugs.mysql.com/bug.php?id=73778 marked as duplicate of this one.

[7 Jan 2015 15:09] Juan Rene Ramirez Monarrez

Posted by developer:
 
Have tried to reproduce this issue with the WB version against it was reported with no success.
Also tried with the lastest version and same result.

Requested the QA team to give it a try and they had no success yet.

Did some review and found that there was some updates on the logic that does this task, this could also resolve the problem on newer versions of the WB.
NOTE: External issues launching MySQL are not part of the WB, i.e. configuration issues or mysql server terminating unexpectedly.

I'm closing this bug as non reproducible, please give it a try to the newest version of the WB (6.2.4), if the problem persist, feel free to either reopen this bug or create a new one.

Thanks for reporting the issue.