MySQL Bugs: #111104: Could not connect, server may not be running.: Lost connection to MySQL server

Bug #111104	Could not connect, server may not be running.: Lost connection to MySQL server
Submitted:	22 May 2023 13:48	Modified:	24 Jun 2023 12:30
Reporter:	Rodrigo Teixeira	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	8.0.28	OS:	MacOS (Could not connect, server may not be running.: Lost connection to MySQL server at 'waiting for initi)
Assigned to:	MySQL Verification Team	CPU Architecture:	Any
Tags:	WBBugReporter

Description:
----[For better reports, please attach the log file after submitting. You can find it in /Users/rodrigoteixeira/Library/Application Support/MySQL/Workbench/log/wb.log]

This is the error I keep getting on connecting to Google Cloud Platfor. Since last Friday (without changing anything), I am unable to connect to GCP. I always get this error: 

Could not connect, server may not be running.: Lost connection to MySQL server at 'waiting for initial communication packet', system error: 60

How to repeat:
Just logging in from the MySQL Workbench app in MAcOs I cannot access the database.

Hello Rodrigo,

Thank you for the bug report.
To investigate further this issue at our end, may I kindly request you to launch workbench under debug mode (--log-level=debug3) and provide unaltered workbench log file(more details about log are explained here - https://dev.mysql.com/doc/workbench/en/workbench-reporting-bugs.html)? Thank you.

Regards,
Ashwini Patil

wb.log

Attachment: wb.log (application/octet-stream, text), 7.85 KiB.

wb.1.log

Attachment: wb.1.log (application/octet-stream, text), 5.66 KiB.

wb.2.log

Attachment: wb.2.log (application/octet-stream, text), 4.24 KiB.

wb.3.log

Attachment: wb.3.log (application/octet-stream, text), 4.16 KiB.

wb.4.log

Attachment: wb.4.log (application/octet-stream, text), 6.12 KiB.

wb.5.log

Attachment: wb.5.log (application/octet-stream, text), 6.12 KiB.

wb.6.log

Attachment: wb.6.log (application/octet-stream, text), 4.24 KiB.

wb.7.log

Attachment: wb.7.log (application/octet-stream, text), 10.90 KiB.

wb.8.log

Attachment: wb.8.log (application/octet-stream, text), 6.06 KiB.

wb.9.log

Attachment: wb.9.log (application/octet-stream, text), 9.08 KiB.

Hi, 

please find attached the logs.

Regards, 

Rodrigo

wb Log from Windows machine.

Attachment: wb_LOGS.txt (text/plain), 7.40 KiB.

Hi, 

I have added a new log this time from a Windows machine regarding the same issue. 

Hope this helps. 

Regards, 

Rodrigo

Hello Rodrigo,

Thank you for the details.
Please try as suggested in the error log :

Please:
1 Check that MySQL is running on address 173.194.233.158
2 Check that MySQL is reachable on port 3306 (note: 3306 is the default, but this can be changed)
3 Check the user aymesbi has rights to connect to 173.194.233.158 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 173.194.233.158 connecting from the host address you're connecting from

Are you able to connect to MySQL Server using command line(with the same user credentials, host details as in MySQL Workbench)? 

Regards,
Ashwini Patil

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".