2nd gen flexible environment "Lost connection to MySQL server at 'reading initial communication packet'"

[Vlad Miller]

Hello,

I am unable to connect to 2nd gen google cloud sql instance from google app engine instance. When I try to connect it simply fails with 

Lost connection to MySQL server at 'reading initial communication packet'

 

The weird thing is that I have another GAE service in the same project which successfully connects to this sql instance via socket. Here is the piece of configuration 

beta_settings:
  cloud_sql_instances: xxxxx-test:us-central1:xxxxx-development

Socket is available

root@4badd097c0d5:/app# ls -lA /cloudsql/xxxxx-test\:us-central1\:xxxxxxx-development srwxrwxrwx 1 root root 0 Jun 10 11:51 /cloudsql/xxxxx-test:us-central1:xxxxxxxx-development

This is not related to my app's code because 

root@4badd097c0d5:/app# mysql --socket=/cloudsql/xxxxx-test\:us-central1\:xxxxxxx-development

ERROR 2013 (HY000): Lost connection to MySQL server at 'reading initial communication packet', system error: 0

Any advice how to proceed here?

[Adam (Cloud Platform Support)]

I'd suggest the following:

- Check the CloudSQL instance logs.

- Check that all apps in the project are authorized under Access Control -> Authorization in the Cloud Console.

- Try a re-deploy of the application.

[Vadim Berezniker]

For troubleshooting, you can also look at the Cloud SQL Proxy logs that may contain more information about the problem.

On the VM that is having the issue, run "docker ps", find the entry for the Cloud SQL Proxy and note down the Container ID.

Then run "docker logs <CONTAINER ID>" to see the logs from the proxy.

--
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-d...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/1c2b3b75-9090-40ef-9b34-aa2a62143cf9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Vlad Miller]

@Adam, there is absolutely nothing interesting in the CloudSQL logs. Also how do I check that apps have access to cloudsql? All GAE services in the same Project with CloudSQL. You mean that I can authorize individual services? 

I also tried to redeploy multiple times, no luck.

@Vadim container logs only showing my application logs, nothing from SQL Proxy.

[Vadim Berezniker]

Hmmm, interesting. Could you grep the VM logs (around boot time) for "proxy"?

Perhaps something caused the proxy not to start successfully. 

--

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-d...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/94120836-8bfb-41f5-9df8-3c782c505b2d%40googlegroups.com.

[Vlad Miller]

@Vadim which exactly logs I'm looking at? VM itself? Or Docker container? 

[Vadim Berezniker]

Yes, the logs for the VM itself. I suspect if the proxy is not running, then something might have gone wrong at startup time and if that's the case we'd love to know what happened.

--

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-d...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/f72d5309-8032-419b-90c9-36e3da5660d5%40googlegroups.com.

[Adam (Cloud Platform Support)]

The 'Authorization' section should say 'Apps in this project: All authorized' however I noticed it always says this regardless of actual permissions set, so a better place to check is under 'IAM & Admin' that the Compute Engine default service account and App Engine default service account both have at least 'Editor' role.

The VM proxy logs may be a better indication of what happened though.