Bug #86284 There was a problem opening the Client Connections
Submitted: 11 May 2017 16:13 Modified: 12 May 2017 12:10
Reporter: Leirbag Gabriel Email Updates:
Status: Unsupported Impact on me:
None 
Category:MySQL Workbench: Administration Severity:S2 (Serious)
Version:6.3.9 OS:Microsoft Windows (Microsoft Windows 10 Pro)
Assigned to: CPU Architecture:Any
Tags: client, Client Connections, Connections, log, workbench

[11 May 2017 16:13] Leirbag Gabriel
Description:
Hi there!

When I try to use the Client Connections menu option, I get the next error:

"There was a problem opening the Client Connections. Please check the error log for more details."

So I read the log file and I get the next errors:

13:03:49 [WRN][wb_admin_control.py:exec_query:624]: Error executing query SELECT COUNT(*) FROM performance_schema.threads: Error executing 'SELECT COUNT(*) FROM performance_schema.threads'
Table 'performance_schema.threads' doesn't exist.
SQL Error: 1146
13:03:49 [ERR][wb_admin_connections.py:page_activated:812]: QueryError in Admin for Client Connections:
Error executing 'SELECT COUNT(*) FROM performance_schema.threads'
Table 'performance_schema.threads' doesn't exist.
SQL Error: 1146

Traceback (most recent call last):
  File "C:\Program Files\MySQL\MySQL Workbench 6.3 CE\modules\wb_admin_connections.py", line 809, in page_activated
    self.ctrl_be.exec_query("SELECT COUNT(*) FROM performance_schema.threads")
  File "C:\Program Files\MySQL\MySQL Workbench 6.3 CE\modules\wb_admin_control.py", line 629, in exec_query
    raise e
QueryError: Error executing 'SELECT COUNT(*) FROM performance_schema.threads'
Table 'performance_schema.threads' doesn't exist.
SQL Error: 1146

13:03:49 [WRN][wb_admin_control.py:exec_query:624]: Error executing query SELECT COUNT(*) FROM performance_schema.threads: Error executing 'SELECT COUNT(*) FROM performance_schema.threads'
Table 'performance_schema.threads' doesn't exist.
SQL Error: 1146
13:03:49 [ERR][wb_admin_connections.py:page_activated:812]: QueryError in Admin for Client Connections:
Error executing 'SELECT COUNT(*) FROM performance_schema.threads'
Table 'performance_schema.threads' doesn't exist.
SQL Error: 1146

Traceback (most recent call last):
  File "C:\Program Files\MySQL\MySQL Workbench 6.3 CE\modules\wb_admin_connections.py", line 809, in page_activated
    self.ctrl_be.exec_query("SELECT COUNT(*) FROM performance_schema.threads")
  File "C:\Program Files\MySQL\MySQL Workbench 6.3 CE\modules\wb_admin_control.py", line 629, in exec_query
    raise e
QueryError: Error executing 'SELECT COUNT(*) FROM performance_schema.threads'
Table 'performance_schema.threads' doesn't exist.
SQL Error: 1146

I really need to use this tool, if you can help me solve this problem, I would really appreciate it.

cheers guys!

How to repeat:
It repeats all the time
[11 May 2017 17:06] MySQL Verification Team
Thank you for the bug report. Which is the server version are you connected with?. Thanks.
[11 May 2017 17:41] Leirbag Gabriel
Hi there! I'm using a MySQL version 5.1.35
[11 May 2017 22:41] MySQL Verification Team
Thank you for the feedback. WorkBench use the performance_schema to get some data like: Threads Connected, Threads Running, etc. Quoting 5.5 Manual:

https://dev.mysql.com/doc/refman/5.5/en/performance-schema.html

"The MySQL Performance Schema is a feature for monitoring MySQL Server execution at a low level. The Performance Schema is available as of MySQL 5.5.3 and has these characteristics:.."

I suggest you to update your server version.
[12 May 2017 12:10] Leirbag Gabriel
Thanks for your help Miguel. How can I close this bug report?
[18 May 2017 17:06] Georald Camposano
Was this a change that was made recently to Workbench? We also use a really old version of mysql (5.1.73) but the Client Connections tab used to work for me a few months ago, a few Mysql Workbench versions back (can't remember when it stopped working though).
[31 May 2017 13:33] Martin H├Ącker
We also have this problem, and since our servers run on CentOS 6 (and will be for some time) updating the MySQL Server version is not an option.

As far as I understand, the App checks that it is communicating with a supported version on establishing the connection - is that not so?

If so, do you plan on changing the supported versions or do you plan on making that code robust against missing performance schemas?
[10 Jul 2017 15:17] Scott Genevish
Yes, this seems to have broken in the recent update.  The 6.2 client can still access the process list on older MySQL servers (we're using Enterprise RedHat 6.9, which has MySQL version 5.1.73
[27 Mar 2018 4:35] Shawn Heisey
This is a big problem.

MySQL Workbench used to be able to look at the connections on all our MySQL servers.  Most of them are still running 5.1.

At some point, not sure exactly when, that capability disappeared, with exactly the same error message in the log that's noted here.

I fully understand that you don't want to support old versions forever.  And I have found information stating that the 5.1 version is now in the "Sustaining Support" category.

We're not asking for new capability, or even any changes to MySQL 5.1, which the Sustaining Support category says *will not* happen.

Is it actually a development burden to keep support for obtaining the connection/process list on older versions in Workbench?

I did some quick searching in the 6.3.x release notes and couldn't find anything mentioning that the way connections were retrieved from the system had changed.  Maybe I just don't know what to search for.
[11 Sep 2018 14:24] NOT_FOUND France
Same problem here. Has anyone worked out which version of MySQLWorkbench is the last working version for older servers?

Not urgent as can just use the command line.
[11 Sep 2018 15:01] NOT_FOUND France
6.3.8 works with mysql 5.1