"connection timed out" errors about cloud-sql-proxy

[ega-forever]

have the same problem right now. But in my case, I have one region (europe-west1-b), and timeout happens in a random manner (so it can work for instance, for 2-3 hours, then disconnect by timeout). I even can't find out the reason.

[Carrotman42]

Sorry for the delay. This is very interesting!

Are both GCE VMs running the exact same code? Is the Cloud SQL Database in the same zone as either of those VMs, or is it in yet a third?

[cuu508]

The VMs are in us-east1-c and us-east1-d. Not sure which zone the database is in, it just says "Location: us-east1". Both VMs are set up with the same provisioning script around the same time, so should be very similar.

In my Django app I had CONN_MAX_AGE set to 60, meaning that every database connection is used for up to one minute and then is closed and reopened. I had a hunch that these errors happen when closing and re-opening the database connection (maybe cloud_sql_proxy needs to refresh its credentials and that part times out?). I changed CONN_MAX_AGE to None for unlimited persistent connections. I haven't seen these "connection timed out" errors since then (2+ weeks now, and about the same amount of traffic).

[Carrotman42]

Yes, if your app is closing connections after 60 seconds that can definitely cause the sort of messages from the Proxy that you posted in the original issue, but it is still a little weird that the django app was also seeing errors related to that closing.

Since the issue has gone away I will close this issue since it seems you've found a workable workaround. If that ceases to be stable please feel free to reopen the issue!