Bug #83914 | error when starting MySQL server via Workbench startup button | ||
---|---|---|---|
Submitted: | 22 Nov 2016 8:17 | Modified: | 16 Jan 2017 11:21 |
Reporter: | Robert Schneider | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 6.3.8 | OS: | MacOS (OS X 10.11.x El Capitan) |
Assigned to: | CPU Architecture: | Any | |
Tags: | WBBugReporter |
[22 Nov 2016 8:17]
Robert Schneider
[7 Dec 2016 20:42]
MySQL Verification Team
Thank you for the bug report. Which MySQL server version are you tried to connect and what kind of connection are you configured?. Thanks.
[7 Dec 2016 20:43]
MySQL Verification Team
I forgot to ask you: is the server running and you are able to connect with mysql command client?. Thanks.
[8 Dec 2016 8:06]
Robert Schneider
Re your questions: Using MySQL 5.6.23 "compiled for osx10.8" (x86_64) on a fully patched MacBook Pro Connection is a socket (i'm no longer an expert on this stuff, so hope this what you were looking for). the error occurs every time I start the server via the MySQL Workbench. Your other question is about if server running. The server is NOT running when I use the startup link in MySQL Workbench to start it up. The start up succeeds even though the error message is provided. The server seems to work ok. It's a Python system accessing the data via Django. I access it via the same machine the server is running, and sometimes from another machine on the network. The title of this bug report is "error when connecting to server". that's probably misleading. It should be "error when *starting* the server". I've changed it here.
[8 Dec 2016 9:45]
MySQL Verification Team
Thank you for the feedback. Then is duplicate of https://bugs.mysql.com/bug.php?id=83769. Work-around to stop and start the server from command line: sudo launchctl unload -F /Library/LaunchDaemons/com.oracle.oss.mysql.mysqld.plist sudo launchctl load -F /Library/LaunchDaemons/com.oracle.oss.mysql.mysqld.plist
[8 Dec 2016 9:50]
Robert Schneider
Thanks for feedback. I did not notice it a duplicate. While there is the reported error on every "start", the server does indeed start so I'm continuing to use it and not using the command prompt. But know that command prompt. Thanks!
[16 Jan 2017 11:19]
Roland Beuker
why is this bug marked: "S3 (Non-critical)" ?!? At this moment (and the last two/three months) a cannot work properly work with Workbench on Mac OSX.
[16 Jan 2017 11:21]
Robert Schneider
Feel free to elevate. For me, as described, even though error is reported, it still seems to start the MySQL Server. Maybe for others that's not the case.
[18 Jan 2017 10:55]
Roland Beuker
Starting MySql outside Workbench isn't working for me because in this situation Workbench doesn't work with the local database (it just hangs on every call).
[30 Jun 2018 23:51]
Monte Chan
I have MySQL WorkBench version 6.3 on a Mac. As another person described, the server seems to start even the error occurs. This error only occurs when I try to start the server within the Workbench interface. In addition, to my recollection, this error has been there in the previous versions of Workbench, too. In all the previous versions that I had, the server would start even though the error took place.