[google-cloud-sql-discuss] [cloud_sql_proxy] Running permanently on a Windows production server

We have an established app running on a Windows production server and are migrating the database to Google Cloud SQL.

I have tested cloud_sql_proxy manually and it works great, but it has to be running from a command prompt according to Google's docs. This is not ideal in production as the command prompt is quit when the terminal services session terminates.

What is the accepted method of running cloud_sql_proxy on a headless Windows production server without any manual intervention? 

--
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/a7762e80-029e-4633-9802-c9f5bbf6c72f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Need to set the global.block_encryption_mode variable to aes-256-cbc

Hello Fahad.

 

As this forum is intended for general discussion, you should post your feature request on one of our Issue Trackers so that our engineers may evaluate it. You can click here to create a feature request for Cloud SQL. Be sure to include details about your use case and why this feature request is important to you.  Once you've filed the feature request, feel free to post a link to it here so that others in the community can follow and support it.

On Tuesday, May 30, 2017 at 6:04:39 PM UTC-4, Fahad G wrote:

Currently it seems block_encryption_mode is not in the support list of flags on Cloud SQL for MySQL. 

We need to please. 128bit is not good enough.

Thanks

Fahad

--
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/f2f09198-aa48-4827-b5e2-07dec911e424%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: [cloud-sql-proxy] couldn't connect to database error, stream error: stream ID 1; PROTOCOL_ERROR

For those of us who use the cloudsql proxy docker image, the Google docs indicate to pin to a specic version. Currently 1.09 is the recommended version here (https://cloud.google.com/sql/docs/mysql/connect-docker).

When I initially setup the cloudsql proxy docker image for production that document said to pull 1.05 - and it bit us when Google decided deprecate support for older versions of their official cloudsql proxy docker images?

Is using the "latest" image bad practice here? Is Google just going to keep updating that doc and deprecating old images without any warning?

On Wednesday, May 31, 2017 at 11:13:14 AM UTC-4, Skyler Slade wrote:

This worked: we updated the version of Cloud Proxy we were using from v1.05 to v1.09 and the problem appears to have gone away. 

That worked for us as well.

It was super fun to have a ~15 minute production outage caused by that this past Monday :)

On Tuesday, May 30, 2017 at 1:25:49 PM UTC-4, Siyuan Zhang wrote:

Hi,

We are using cloud-sql-proxy together with kubernetes to deploy our app, it works fine since Nov. 2016. For the first time, today, 2 of our 5 pods reported bad connection when trying to connect to google-cloud-sql with cloud-sql-proxy. here are parts the logs:

2017/05/30 16:42:44 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:44 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:44 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:44 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 277.184µs ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 1.194005ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 1.644907ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 382.94776ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 383.939371ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 384.954228ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 385.11944ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 388.399746ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 389.191251ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 497.448221ms ago

We resolved this by deleting the pod, and after 30mins we restarted the first pod with this issue, another pod reported the same errors. and the end, we have restarted all pods. it seems gone now, but dont know if it will occur again.

--
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/f8f3ad41-6a53-479f-8f9d-e2421a9f3cbc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: [cloud-sql-proxy] couldn't connect to database error, stream error: stream ID 1; PROTOCOL_ERROR

This worked: we updated the version of Cloud Proxy we were using from v1.05 to v1.09 and the problem appears to have gone away. 

That worked for us as well.

It was super fun to have a ~15 minute production outage caused by that this past Monday :)

On Tuesday, May 30, 2017 at 1:25:49 PM UTC-4, Siyuan Zhang wrote:

Hi,

We are using cloud-sql-proxy together with kubernetes to deploy our app, it works fine since Nov. 2016. For the first time, today, 2 of our 5 pods reported bad connection when trying to connect to google-cloud-sql with cloud-sql-proxy. here are parts the logs:

2017/05/30 16:42:44 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:44 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:44 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:44 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 277.184µs ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 1.194005ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 1.644907ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 382.94776ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 383.939371ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 384.954228ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 385.11944ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 388.399746ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 389.191251ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 497.448221ms ago

We resolved this by deleting the pod, and after 30mins we restarted the first pod with this issue, another pod reported the same errors. and the end, we have restarted all pods. it seems gone now, but dont know if it will occur again.

--
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/024d1e63-40f8-4289-bece-dfacb79d7f36%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: [cloud-sql-proxy] couldn't connect to database error, stream error: stream ID 1; PROTOCOL_ERROR

Thanks Greg, you saved my day, have upgraded cloud-proxy to v1.09 8 hours ago, no more errors until now. It does solve the problem for me as well.

On Wednesday, May 31, 2017 at 6:15:29 AM UTC+8, Joey Holler wrote:

Thanks Greg, this solves the issue for me as well.

On Tuesday, May 30, 2017 at 5:13:42 PM UTC-5, Greg Hecht wrote:

Same issue appeared for us today. 

This worked: we updated the version of Cloud Proxy we were using from v1.05 to v1.09 and the problem appears to have gone away. 

Give that a shot?

On Tuesday, May 30, 2017 at 1:06:31 PM UTC-7, Jonathan Sick wrote:

I'm having the same issue with cloud_sql_proxy this morning. Restarting pods in GKE hasn't solved the problem. I also restored my DB to a brand new Cloud SQL instance in us-east (we were in us-central1) and that hasn't resolved the issue either.

On Tuesday, May 30, 2017 at 12:51:03 PM UTC-7, Joey Holler wrote:

I have 2 Compute Engine instances that both suffered the same issue today, one at a time.  They have both been using the cloud_sql_proxy for months without any issue, but suddenly today the proxies on both instances intermittently starting to show similar errors:

2017/05/30 13:28:07 New connection for "project-id-1234:us-central1:sql_instance"
2017/05/30 13:28:07 couldn't connect to "project-id-1234:us-central1:sql_instance": Post https://www.googleapis.com/sql/v1beta4/projects/project-id-1234/instances/sql_instance/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR
2017/05/30 13:28:41 New connection for "project-id-1234:us-central1:sql_instance"
2017/05/30 13:28:41 Thottling refreshCfg(project-id-1234:us-central1:sql_instance): it was only called 33.490705951s ago
2017/05/30 13:28:41 couldn't connect to "project-id-1234:us-central1:sql_instance": Post https://www.googleapis.com/sql/v1beta4/projects/project-id-1234/instances/sql_instance/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

I tried restarting both SQL and CE instances, but it did not resolve the issue with using the proxy, and I had to resort to adding the Authorized Networks and using the public IP of my SQL instance in order to get my production sites back up.  For me the issue still persists when trying to use the proxy.

On Tuesday, May 30, 2017 at 12:25:49 PM UTC-5, Siyuan Zhang wrote:

Hi,

We are using cloud-sql-proxy together with kubernetes to deploy our app, it works fine since Nov. 2016. For the first time, today, 2 of our 5 pods reported bad connection when trying to connect to google-cloud-sql with cloud-sql-proxy. here are parts the logs:

2017/05/30 16:42:44 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:44 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:44 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:44 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 277.184µs ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 1.194005ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 1.644907ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 382.94776ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 383.939371ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 384.954228ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 385.11944ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 388.399746ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 389.191251ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 497.448221ms ago

We resolved this by deleting the pod, and after 30mins we restarted the first pod with this issue, another pod reported the same errors. and the end, we have restarted all pods. it seems gone now, but dont know if it will occur again.

--
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/12ba5522-49d5-4cbc-8ad6-4695b0d84528%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: [cloud-sql-proxy] couldn't connect to database error, stream error: stream ID 1; PROTOCOL_ERROR

Thanks Greg, this solves the issue for me as well.

On Tuesday, May 30, 2017 at 5:13:42 PM UTC-5, Greg Hecht wrote:

Same issue appeared for us today. 

This worked: we updated the version of Cloud Proxy we were using from v1.05 to v1.09 and the problem appears to have gone away. 

Give that a shot?

On Tuesday, May 30, 2017 at 1:06:31 PM UTC-7, Jonathan Sick wrote:

I'm having the same issue with cloud_sql_proxy this morning. Restarting pods in GKE hasn't solved the problem. I also restored my DB to a brand new Cloud SQL instance in us-east (we were in us-central1) and that hasn't resolved the issue either.

On Tuesday, May 30, 2017 at 12:51:03 PM UTC-7, Joey Holler wrote:

I have 2 Compute Engine instances that both suffered the same issue today, one at a time.  They have both been using the cloud_sql_proxy for months without any issue, but suddenly today the proxies on both instances intermittently starting to show similar errors:

2017/05/30 13:28:07 New connection for "project-id-1234:us-central1:sql_instance"
2017/05/30 13:28:07 couldn't connect to "project-id-1234:us-central1:sql_instance": Post https://www.googleapis.com/sql/v1beta4/projects/project-id-1234/instances/sql_instance/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR
2017/05/30 13:28:41 New connection for "project-id-1234:us-central1:sql_instance"
2017/05/30 13:28:41 Thottling refreshCfg(project-id-1234:us-central1:sql_instance): it was only called 33.490705951s ago
2017/05/30 13:28:41 couldn't connect to "project-id-1234:us-central1:sql_instance": Post https://www.googleapis.com/sql/v1beta4/projects/project-id-1234/instances/sql_instance/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

I tried restarting both SQL and CE instances, but it did not resolve the issue with using the proxy, and I had to resort to adding the Authorized Networks and using the public IP of my SQL instance in order to get my production sites back up.  For me the issue still persists when trying to use the proxy.

On Tuesday, May 30, 2017 at 12:25:49 PM UTC-5, Siyuan Zhang wrote:

Hi,

We are using cloud-sql-proxy together with kubernetes to deploy our app, it works fine since Nov. 2016. For the first time, today, 2 of our 5 pods reported bad connection when trying to connect to google-cloud-sql with cloud-sql-proxy. here are parts the logs:

2017/05/30 16:42:44 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:44 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:44 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:44 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 277.184µs ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 1.194005ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 1.644907ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 382.94776ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 383.939371ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 384.954228ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 385.11944ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 388.399746ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 389.191251ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 497.448221ms ago

We resolved this by deleting the pod, and after 30mins we restarted the first pod with this issue, another pod reported the same errors. and the end, we have restarted all pods. it seems gone now, but dont know if it will occur again.

--
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/32dac8ba-3e30-4651-8554-ef450063f623%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: [cloud-sql-proxy] couldn't connect to database error, stream error: stream ID 1; PROTOCOL_ERROR

Same issue appeared for us today. 

This worked: we updated the version of Cloud Proxy we were using from v1.05 to v1.09 and the problem appears to have gone away. 

Give that a shot?

On Tuesday, May 30, 2017 at 1:06:31 PM UTC-7, Jonathan Sick wrote:

I'm having the same issue with cloud_sql_proxy this morning. Restarting pods in GKE hasn't solved the problem. I also restored my DB to a brand new Cloud SQL instance in us-east (we were in us-central1) and that hasn't resolved the issue either.

On Tuesday, May 30, 2017 at 12:51:03 PM UTC-7, Joey Holler wrote:

I have 2 Compute Engine instances that both suffered the same issue today, one at a time.  They have both been using the cloud_sql_proxy for months without any issue, but suddenly today the proxies on both instances intermittently starting to show similar errors:

2017/05/30 13:28:07 New connection for "project-id-1234:us-central1:sql_instance"
2017/05/30 13:28:07 couldn't connect to "project-id-1234:us-central1:sql_instance": Post https://www.googleapis.com/sql/v1beta4/projects/project-id-1234/instances/sql_instance/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR
2017/05/30 13:28:41 New connection for "project-id-1234:us-central1:sql_instance"
2017/05/30 13:28:41 Thottling refreshCfg(project-id-1234:us-central1:sql_instance): it was only called 33.490705951s ago
2017/05/30 13:28:41 couldn't connect to "project-id-1234:us-central1:sql_instance": Post https://www.googleapis.com/sql/v1beta4/projects/project-id-1234/instances/sql_instance/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

I tried restarting both SQL and CE instances, but it did not resolve the issue with using the proxy, and I had to resort to adding the Authorized Networks and using the public IP of my SQL instance in order to get my production sites back up.  For me the issue still persists when trying to use the proxy.

On Tuesday, May 30, 2017 at 12:25:49 PM UTC-5, Siyuan Zhang wrote:

Hi,

We are using cloud-sql-proxy together with kubernetes to deploy our app, it works fine since Nov. 2016. For the first time, today, 2 of our 5 pods reported bad connection when trying to connect to google-cloud-sql with cloud-sql-proxy. here are parts the logs:

2017/05/30 16:42:44 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:44 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:44 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:44 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:45 Client closed local connection on 127.0.0.1:3306

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 277.184µs ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 1.194005ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 1.644907ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 382.94776ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 383.939371ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 384.954228ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 385.11944ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 388.399746ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 389.191251ms ago

2017/05/30 16:42:46 couldn't connect to "teak-clarity-132123:us-central1:diningzoodatabase": Post https://www.googleapis.com/sql/v1beta4/projects/teak-clarity-132123/instances/diningzoodatabase/createEphemeral?alt=json: stream error: stream ID 1; PROTOCOL_ERROR

2017/05/30 16:42:46 New connection for "teak-clarity-132123:us-central1:diningzoodatabase"

2017/05/30 16:42:46 Thottling refreshCfg(teak-clarity-132123:us-central1:diningzoodatabase): it was only called 497.448221ms ago

We resolved this by deleting the pod, and after 30mins we restarted the first pod with this issue, another pod reported the same errors. and the end, we have restarted all pods. it seems gone now, but dont know if it will occur again.

--
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/449273e9-d688-438a-b419-7d2f76ce6f5f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.