Hello Thomas,
Please note that aborted connection error is caused mainly by the following events:
- A client attempts to access a database but has no privileges for it.
- A client uses an incorrect password.
- A connection packet does not contain the right information.
- It takes more than connect_timeout seconds to obtain a connect packet."
- The client slept for longer than the defined wait_timeout or interactive_timeout seconds
I suggest you review this document that contains a list of the most frequent issues you might run into when working with Google Cloud SQL instances as well as steps you can take to address them. I would also recommend to read this third party document to identify the possible reasons for MySQL "Got an error reading communication packet" errors, and how to address them.
If you still are seeing this error after reviewing the above information, and you believe the issue is on our end, please open a private Issue Tracker and provide the following information:
- Project ID and Cloud SQL instance ID
- Timestamp of the last occurence
- Have you performed any change to the code accessing the Mysql since the "timeouts" or the "error reading" was not happening?
- Do you close the connections properly during the normal behaviour?
- Do you keep many connections idle and open for a long time?
- Screenshot of the error encountered on your end
Please make sure to open it using the provided link as it will be a private Issue Tracker where you will be able to share your project ID.
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/3c9b43f6-3b8d-4670-ab2d-f58adfd5c0de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment