Bug #82492 No reconnect (on timeout?) : Error Code: 2006. MySQL server has gone away
Submitted: 8 Aug 2016 12:24 Modified: 8 Aug 2016 12:44
Reporter: László Fenyvesi Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:6.3.5 OS:Windows (Microsoft Windows 10 Home)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[8 Aug 2016 12:24] László Fenyvesi
Description:
If staying idle for a while, then trying to SELECT from a table, this error occures: Error Code: 2006. MySQL server has gone away
I understand that this is fine because of connection timeout (maybe).
But then I can't reconnect, if I close the uppermost connection tab, then trying to reconnect from the home screen (where connections are displayed), then this pops up:
Cannot Connect to Database Server
Your connection attempt failed for user 'myusername' from your host to server at 127.0.0.1:3306:
Tunnel error: Remote connection to 127.0.0.1:3306 was rejected by the SSH server.
Please:
1	Check that mysql is running on server 127.0.0.1
2	Check that mysql is running on port 3306 (note: 3306 is the default, but this can be changed)
3	Check the myusername has rights to connect to 127.0.0.1 from your address (mysql rights define what clients can connect to the server and from which machines)
4	Make sure you are both providing a password if needed and using the correct password for 127.0.0.1 connecting from the host address you're connecting from

--------
If I close WB then restart it then it can connect, so my MySql server is ok.

How to repeat:
After connect and select from a table, wait some time, then try to select/reconnect.

Suggested fix:
Restart WB.
[8 Aug 2016 12:25] László Fenyvesi
Sometimes this error message occures before the #2006:
Error Code: 2013. Lost connection to MySQL server during query
[8 Aug 2016 12:44] MySQL Verification Team
Thank you for the bug report. Duplicate of http://bugs.mysql.com/bug.php?id=80225.