| Bug #79897 | Incomplete setup of Workbench causes performance schema misrecognition | ||
|---|---|---|---|
| Submitted: | 8 Jan 2016 17:22 | Modified: | 11 Sep 2016 0:50 |
| Reporter: | Tony Holmes | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
| Version: | 6.3.5 | OS: | MacOS (10.11.2) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | performance schema, workbench | ||
[11 Aug 2016 0:50]
MySQL Verification Team
Please try version 6.3.7. Thanks.
[11 Sep 2016 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
Description: There seems to be a bug where an incomplete setup of performance tools causes an issue where workbench is unable to make a clean connection for the purposes of "performance reports" and "performance schema setup" windows. The wb.log shows an error 2006, thus 11:56:09 [ERR][wb_admin_perfschema.py:ps_usable:275]: MySQL error retrieving the performance_schema variable: ('MySQL server has gone away', 2006) How to repeat: An incomplete variable in connections.xml seemed to cause this. Removing <value type="string" key="schema"></value> from the connection and restarting workbench seems to resolve this problem. Suggested fix: Error caused by empty "schema" variable in connections.xml; Perhaps a sanity check on connections.xml at startup may solve this, or allow the exception to be handled.