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:
None 
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
Description:
----[For better reports, please attach the log file after submitting. You can find it in /Users/rmschne/Library/Application Support/MySQL/Workbench/log/wb.log]

Unhandled exception: Wrong number or type of arguments for overloaded function 'TextBox_append_text_with_encoding'.
  Possible C/C++ prototypes are:
    mforms::TextBox::append_text_with_encoding(std::string const &,std::string const &,bool)
    mforms::TextBox::append_text_with_encoding(std::string const &,std::string const &)

===

08:14:35 [INF][      Workbench]: Starting up Workbench
08:14:35 [INF][      WBContext]: Parsing application arguments.
08:14:35 [INF][      WBContext]:     /Applications/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench
08:14:35 [INF][   WBContext UI]: Initializing workbench context UI with these values:
	base dir: /Applications/MySQLWorkbench.app/Contents/Resources
	plugin path: /Applications/MySQLWorkbench.app/Contents/PlugIns
	struct path: /Applications/MySQLWorkbench.app/Contents/Resources/grt
	module path: /Applications/MySQLWorkbench.app/Contents/PlugIns:/Applications/MySQLWorkbench.app/Contents/Resources/plugins
	library path: /Applications/MySQLWorkbench.app/Contents/Resources/libraries
	user data dir: /Users/rmschne/Library/Application Support/MySQL/Workbench
	open at start: 
	open type: 
	run at startup: 
	run type: 
	Force SW rendering: No
	Force OpenGL: No
	quit when done: No
08:14:35 [INF][      WBContext]: WbContext::init
08:14:36 [INF][            WBA]: Looking for extension modules for WBA...
08:14:36 [INF][            WBA]: 0 extension modules found
08:14:36 [WRN][            grt]: /Applications/MySQLWorkbench.app/Contents/Resources/data/table_templates.xml:21: link 'com.mysql.rdbms.mysql.datatype.timestamp' <object db.SimpleDatatype> key=simpleType could not be resolved
08:14:36 [WRN][            grt]: /Applications/MySQLWorkbench.app/Contents/Resources/data/table_templates.xml:106: link 'com.mysql.rdbms.mysql.datatype.varchar' <object db.SimpleDatatype> key=simpleType could not be resolved
08:14:36 [WRN][            grt]: /Applications/MySQLWorkbench.app/Contents/Resources/data/table_templates.xml:229: link 'com.mysql.rdbms.mysql.datatype.int' <object db.SimpleDatatype> key=simpleType could not be resolved
08:14:36 [WRN][            grt]: /Users/rmschne/Library/Application Support/MySQL/Workbench/connections.xml:27: link '40F5C16F-9CC7-4E59-A8F5-1720B15B4549' <object GrtObject> key=owner could not be resolved
08:14:36 [INF][      WBContext]: System info:
 	MySQL Workbench Community (GPL) for Mac OS X version 6.3.8 CE build 1228 (64 bit)
	Configuration Directory: /Users/rmschne/Library/Application Support/MySQL/Workbench
	Data Directory: /Applications/MySQLWorkbench.app/Contents/Resources
	Cairo Version: 1.10.2
	OS: OS X 10.11.x El Capitan
	CPU: 8x Intel(R) Core(TM) i7-3820QM CPU @ 2.70GHz - 16.00GiB RAM

08:14:43 [ERR][      SqlEditor]: SqlEditorForm: exception in do_connect method: Exception: Can't connect to MySQL server on '127.0.0.1' (61)
08:14:43 [INF][      SqlEditor]: Error 2003 connecting to server, assuming server is down and opening editor with no connection
08:14:43 [INF][      SqlEditor]: Error 2003 connecting to server, assuming server is down and opening editor with no connection
08:14:44 [ERR][wb_admin_control.py:init:314]: Error connecting to MySQL: Can't connect to MySQL server on '127.0.0.1' (61) (code 2003)
08:14:44 [ERR][wb_admin_control.py:server_polling_thread:559]: Error creating SQL connection for monitoring: MySQLError("Can't connect to MySQL server on '127.0.0.1' (61) (code 2003)",)
08:14:44 [INF][wb_admin_control.py:query_server_installation_info:857]: Currently connected to MySQL server version 'unknown', conn status = None, active plugins = []
08:14:44 [INF][wb_admin_control.py:acquire_admin_access:288]: Target OS detection returned: os_type=darwin, os_name=Mac OS X, os_variant=Mac OS X, os_version=10.11.6
08:14:45 [INF][wb_admin_control.py:exec_query:626]: sql connection is down
08:14:48 [INF][wb_log_reader.py:__init__:351]: Will use sudo and dd to get contents of log file /usr/local/mysql/data/MacBookPro.local.err
08:14:50 [INF][wb_admin_control.py:exec_query:626]: sql connection is down
08:14:50 [INF][wb_admin_control.py:exec_query:626]: sql connection is down
08:14:50 [INF][wb_admin_main.py:handle_server_state_changed:235]: received notification that server state changed to 1
08:14:50 [ERR][       pymforms]: Unhandled exception in Python code: Wrong number or type of arguments for overloaded function 'TextBox_append_text_with_encoding'.
  Possible C/C++ prototypes are:
    mforms::TextBox::append_text_with_encoding(std::string const &,std::string const &,bool)
    mforms::TextBox::append_text_with_encoding(std::string const &,std::string const &)

<traceback object at 0x11ab34e18>
08:14:50 [INF][      SqlEditor]: Opened connection 'Local' to MySQL Community Server (GPL) version 5.6.23

How to repeat:
connect to server

Suggested fix:
not known to me.
[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.