Bug #75743 Workbench unable to show processlist
Submitted: 3 Feb 2015 10:39 Modified: 3 Mar 2015 15:48
Reporter: Miguel Espinoza Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:6.2.4.12437 OS:MacOS
Assigned to: CPU Architecture:Any

[3 Feb 2015 10:39] Miguel Espinoza
Description:
Clicking "Client Connections" shows this alert and does not show the list of connections

Unhandled exception: Error executing 'SELECT t.PROCESSLIST_ID,IF (NAME = 'thread/sql/event_scheduler','event_scheduler',t.PROCESSLIST_USER) PROCESSLIST_USER,t.PROCESSLIST_HOST,t.PROCESSLIST_DB,t.PROCESSLIST_COMMAND,t.PROCESSLIST_TIME,t.PROCESSLIST_STATE,t.THREAD_ID,t.TYPE,t.NAME,t.PARENT_THREAD_ID,t.INSTRUMENTED,t.PROCESSLIST_INFO,a.ATTR_VALUE FROM performance_schema.threads t  LEFT OUTER JOIN performance_schema.session_connect_attrs a ON t.processlist_id = a.processlist_id AND (a.attr_name IS NULL OR a.attr_name = 'program_name') WHERE t.TYPE <> 'BACKGROUND''
Table 'performance_schema.session_connect_attrs' doesn't exist.
SQL Error: 1146

How to repeat:
Have a MySQL 5.6 DB and MySQL Workbench 6.2.4, connect to the database and click "Client Connections"
[3 Feb 2015 10:40] Miguel Espinoza
Changed the OS to Mac OS X
[3 Feb 2015 10:55] MySQL Verification Team
client connection  screen

Attachment: client_connections.png (image/png, text), 320.56 KiB.

[3 Feb 2015 11:34] MySQL Verification Team
Thank you for the report.
Could you please confirm whether the table exists performance_schema.session_connect_attrs?

from mysql> 

desc performance_schema.session_connect_attrs;

Also, could you pls show the privileges of user which is being used(you may want to make the note private)? Also, provide complete error log for further investigation.

Thanks,
Umesh
[3 Feb 2015 15:06] Peter Laursen
If the P_S table does not exist it could very well be because 'msyql_upgrade' needs to be run after a server upgrade. 

-- Peter
-- not an Oracle/mySQL person
[4 Mar 2015 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".