[google-cloud-sql-discuss] Can't Connect to Cloud SQL from Compute Engine

I recently set up a Google Cloud SQL as well as a Compute Engine, however, I am having issues connecting to it. I have included my IP address in the authorized network tab but I am still unable to get through. The only error that PDO returns is this:

SQLSTATE[HY000] [2002] Connection timed out

Any help would be greatly appreciated! Thank you.

--
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/496e60e1-b5c5-4152-9045-03b7445a03d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Can't Connect to SQL from Compute Instance

Hello, I recently got a Cloud SQL instance set up but I am unable to access it using my Compute Engine instance. I have included the external IP in authorized networks list and I am still unable to connect. The only error that it is giving me is this:

SQLSTATE[HY000] [2002] Connection timed out

Any help would be greatly appreciated. Thank you.

--
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/e32ac569-afff-48d2-b693-8f7b8122fdb4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: sql instance restart automatically.

Thank you.

I have seen below thread.

This thread is my mistake.

delete plz.

2018년 5월 1일 화요일 오전 5시 19분 32초 UTC+9, Karthick (Cloud Platform Support) 님의 말:

Hello,

I noticed that this concern is already addressed in this thread. Future discussion regarding this will be held there. 

p.s. Please note that I have concealed your project details from the previous message as this is considered to be a sensitive information.

--
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/fb6bef7e-e0c8-4983-9622-0b1e3008629e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Failed to create clone with point-in-time

I got the binary log file name from SHOW BINARY LOGS command, and 1 tried with position 1, failed, then i clone another with some of the position from SHOW BIN LOG EVENTS command, it failed too.

There is no error reports, the cloning started, a new instance created, and it runs from couple of minutes, then the instance ended up with a red exclamation mark which shows Failed to create.

On Tuesday, 1 May 2018 07:56:37 UTC+8, Digil (Google Cloud Platform Support) wrote:

While performing the 'Cloning' on Cloud SQL instance, have you properly mentioned the 'binary log file name' and 'recovery position'?. You can find information about these details in this help center article. Also, have you received any error reports while generating the clone?. Furthermore, you might also need to check the document on diagnosing the issue with Cloud SQL instances as well.

--
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/446f3fbb-c11a-46df-bcf3-8d26f08d1140%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Failed to create clone with point-in-time

While performing the 'Cloning' on Cloud SQL instance, have you properly mentioned the 'binary log file name' and 'recovery position'?. You can find information about these details in this help center article. Also, have you received any error reports while generating the clone?. Furthermore, you might also need to check the document on diagnosing the issue with Cloud SQL instances as well.

--
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/c46a929a-41a2-466d-b373-de171b2c421f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Can I drop the failover CloudSQL instance and re-create it?

Hello Roshan,

According to this document " To minimize performance impact on the master, while ensuring that changes are never lost, the replica logs the update events, and then performs the updates in order."  Therefore, I highly doubt that there is specific task that runs every 4- 5 minutes to keep both instances synced, but rather in seconds per order of each operation . You may verify that by checking the replication lag metrics (seconds behind master).  

As for stopping/pausing the failover replica, it is not currently possible. As you mentioned, you would have to delete it, and this would render your master not to be configured with high availability. If you choose to recreate the replica, you may check this guide for quick configurations. I hope this helps

--
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/4619340a-7d47-4a12-9e78-062e4e24282a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: sql instance restart automatically.

Hello,

I noticed that this concern is already addressed in this thread. Future discussion regarding this will be held there. 

p.s. Please note that I have concealed your project details from the previous message as this is considered to be a sensitive information.

--
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/388008af-0bbe-42ca-a2e9-050f914b73ad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Sql instance restart automatically

After inspecting your Project, this instance restart was the part of the routine maintenance of Cloud SQL instances, where updates and upgrades are applied to the instances, so that there was a downtime which is expected, as explained in the documentation. You can also check this SLA page for Cloud SQL, instances can also present some time of monthly downtime period; however, in any case, the scheduled maintenance is not counted in the downtime period.

Also, I see that you have not set a maintenance window, and therefore you allow for any disruptive maintenance update to happen at any time. If you wish, you can specify a specific day and hour for the maintenance schedule by editing your instance through the Console, in such a way that you can make sure that maintenance updates happen during a time frame that affects your services minimally.

p.s. Please note that I have concealed your project details from the previous message as this is considered to be a sensitive information.

--
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/37e98994-39f4-46da-86fd-1fecfb0ff275%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Failed to create clone with point-in-time

I tried to create a clone with point-in-time with different binary log and position, but after loading for a long while, will ended with a Failed to create error.

Is there anyway i can find out why it failed? 

--
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/10f64c87-e22c-410b-ac3a-412cd71a27c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Sql instance restart automatically

Hi there!

My sql instance restart automatically a few hour ago.  restarted at 2018-04-30T04:22:00(UTC).

i didn't do anything. 

i looked at logs. but i haven't found a problem  yet.

Is that my mistake?

help me plz.

Thank you.

project number is 943233972526.

sql instance name is mad8db.

--
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/ef7d0d27-a86f-4f00-8e8b-69da4f10e97c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] sql instance restart automatically.

Hi there!

My sql instance restart automatically a few hour ago.

restarted at 2018-04-30T04:22:00(UTC) 

i didn't do anything. 

i looked at logs. but i haven't found a problem  yet.

Is that my mistake?

help me plz.

Thank you.

project number is 943233972526.

sql instance name is mad8db.

--
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/057acb48-d432-4b11-8d35-8186abd98772%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Can I drop the failover CloudSQL instance and re-create it?

Hi,

I have a cloud-sql instance setup with a failover. It's noticed that there is a drop in the performance of db queries every 4-5 minutes. It's very regular. There is a feeling that it could be due to some internal operations that need to be done to keep the failover instance in sync.

In order to verify or refute that, I was thinking of dropping the failover instance temporarily and see whether the dip in queries-performance goes away and then bring it back.

Is it a bad idea to do this experiment - other than the fear that for the duration of this experiment, there won't be a failover instance?

My requirement is just to temporarily get rid of the failover instance. If, instead of deleting this failover instance, I can detach it and then re-attach it later, that might be even better. As that may result in less work it'll need to do to bring an up-to-date failover.

Any vies / inputs will be highly appreciated.

Regards,

Roshan

--
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/98ced34f-20e9-4e76-925a-87ad57a095a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Outage/unknown operation on April 29th?

Thanks, I've logged a ticket.

--
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/e937c095-c181-470f-b22b-2184665fad4b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Outage/unknown operation on April 29th?

Hello Hrish,

Thank you for reporting the issue. Seems like the reported issue will require detailed investigation on your project to determine the root cause. I would suggest you open an issue in the GCP private issue component in the public issue tracker with project number, instance id, and related logs so it can be investigated further. If you already have done so, you can get updates from the logged issue.

--
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/6c716a07-b61f-40ad-bf39-64373ff420dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Outage/unknown operation on April 29th?

1. My apps connecting to Google CloudSQL via the cloud_sql_proxy failed to connect for more than a minute. The Google Cloud Status dashboard does not show any outage.Can somebody from Google throw any light on this? This happened at 14:12 Apr 29 2018 UTC

2. Around that time, after 5 minutes or so, my CloudSQL -> Operations dashboard shows an event without a label. What is this operation? Why is this unlabelled? Please see the screenshot. Note that the screenshot times are in IST (UTC +5:30)

--
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/17b0f662-f657-4b34-a52a-cbe46bd4703a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Communications link failure exception (mysql - cloud sql)

It may be worthwhile providing more detail on the solution. Other people in the same situation should find this useful. 

--
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/a80cc97f-aca9-4299-89d1-9a035c7263e0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Postgres 10 Support

Hi Dave-

We are not able to provide a target date for Postgres 10 support, but the Cloud SQL team will post updates (new features, release announcements) to the Cloud SQL announce group. 

Regards,

Brett

On Wednesday, April 25, 2018 at 4:08:32 PM UTC-7, Dave Bettin wrote:

When will Postgres 10 support be released?   And what is the plan for ongoing postgres releases?

Thanks!

Dave

--
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/f9ae31b3-6cbb-4e34-ba66-70bac22c3c34%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-cloud-sql-discuss] PostgreSQL how to increase limit connections?

Hi Thomas, did you manage to set this up eventually using pg_shadow with CloudSQL? If not, how did you work around this shortcoming? Thanks!

On Tuesday, August 8, 2017 at 6:12:37 PM UTC+2, Thomas Yager-Madden wrote:

On Thursday, April 13, 2017 at 9:19:05 AM UTC-5, Vladimir Rusinov wrote:

As a temporary workaround, you can run something like pgbouncer on Compute Engine in the same region as your instance.

Can you explain or point to documentation on how to use pgbouncer with Cloud SQL Postgres instance? Specifically, it seems that for authorizing users, pgbouncer needs access to pg_shadow, which is only available to superusers. 

--
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/51b4b89f-f39e-4ffb-b86f-6304136a5ebb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Communications link failure exception (mysql - cloud sql)

Thanks for replying, in fact i found that the problem is about my google appengine application. So i changed the app and everything works fine.

Le jeudi 26 avril 2018 20:37:19 UTC+1, George (Cloud Platform Support) a écrit :

If you think this is an issue related to Cloud SQL, you should open an issue in the public tracker. For coding issues and general programming problems, you should post your question on stackoverflow or similar forums, where competent programmers are ready to help. 

If you'd like us to have a look at your code, you may consider sending this information via private message. This feature is available from the drop-down menu offered by the reply button at the top right of the editing windows. 

--
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/84c3eac3-a4ed-45bd-a794-bfce0ae4d68d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Postgres Connections Randomly Dropping

Hi Nigel,

Thanks for the feedback. For Postgres SQL instance, fail-over instance is located in the different zone with-in the same configured region, so if the master cannot serve data from its primary zone, it fails over and continues to serve data from its secondary zone. As per the cloud documentation, if cloud SQL instance configured for HA experiences an outage or becomes unresponsive, Cloud SQL automatically switches to serving data from the secondary zone. It is recommended to configure all of your instances that contain production data for HA.

Regarding the connection problem, please check and verify the following points:-

1. Default TCP/IP port on which the postgres server listen is tcp:5432. Any specific reason why you using port 3306 which is default port for MySQL DB? Please correct this if it is a mistake.

2. Please note that there is Maximum concurrent connections limit for Cloud SQL based upon instance memory. Please check if your instance is not going beyond the connection limit during peak hours.

3. Please refer to this StackOverflow thread for the similar problem and suggested solutions for the troubleshooting. 

If above does not help, please share your project number, PostgreSQL instance name, Instance operations logs, and PostgreSQL error logs along with issue date, time and duration via a private email.

Regards,

 
On Wednesday, April 25, 2018 at 5:38:43 PM UTC-4, Nigel Gutzmann wrote:

Thanks for the suggestion Dinesh, but I don't think that's it. We are getting the errors much more frequently than there are events in the operations tab. Typically we get 2-3 bursts of errors per day, but there is generally just one operation: a backup. The timing also doesn't necessarily coincide between the events and the errors. Regardless, if the operations were a problem, would turning on HA fix the issue, or would that not help?

Any other ideas about why we could be seeing these connection problems?

Nigel G.

On Wednesday, 25 April 2018 14:17:18 UTC-7, Dinesh (Google Platform Support) wrote:

As you suggesting you receive such errors only for 2-3 minutes in a day, I suspect your instance might be going through maintenance updates (that require an instance restart) during that times.  Please view operational logs of your Postgre SQL instance. You can view them from cloud console GUI inside instance details view, under operations tab. If you find instance was updated at the same time, that explain the cause of these logs. 

If that is the real cause of the mentioned errors, I will recommend configuring the schedule for the Maintenance window and Maintenance timing to avoid any surprises in the future. 

Let me know if this helps?

Regards,

On Wednesday, April 25, 2018 at 12:59:51 PM UTC-4, Nigel Gutzmann wrote:

I have a django and celery application running inside of Google Kubernetes Engine. I am connecting to my CloudSQL instance (postgres) using a Kubernetes service running the CloudSQL Proxy. Database connections and queries generally work fine, but occasionally we get spurts of errors with connections breaking. They are raised in python like this:

OperationalError: could not connect to server: Connection refused Is the server running on host "cloudsql-proxy-service" and accepting TCP/IP connections on port 3306?

or

OperationalError: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request.

I can't find anything that might cause that in the logs of the CloudSQL instance. There are some messages like this in the CloudSQL proxy logs:

2018/04/24 18:55:18 Instance <project_name>:us-central1:<instance_name> closed connection

But I can't necessarily correlate the timestamps between when those messages appear and when we get the python errors. I have tried setting CONN_MAX_AGE and tcp keepalives like this inside django's settings.py:

DATABASES = {

    'default': {

        'ENGINE': 'django.db.backends.postgresql',

        'NAME': '<db_name>',

        'USER': os.environ.get('DB_USER', None),

        'HOST': os.environ.get('DB_HOST', None),

        'PORT': os.environ.get('DB_PORT', None),

        'PASSWORD': os.environ.get('DB_PASSWORD', None),

        'CONN_MAX_AGE': int(os.environ.get('CONN_MAX_AGE', 0)),

        'OPTIONS': {

            'keepalives': 1,

            'keepalives_idle': 480,

            'keepalives_interval': 10,

            'keepalives_count': 3,

        },

    },

}

But that didn't seem to make a difference. We still get the same errors in bunches, about 20 errors over the span of 2-3 minutes, 2-3 times per day.

--
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/9a483768-b42c-441d-a5be-77a2fc73de25%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Communications link failure exception (mysql - cloud sql)

If you think this is an issue related to Cloud SQL, you should open an issue in the public tracker. For coding issues and general programming problems, you should post your question on stackoverflow or similar forums, where competent programmers are ready to help. 

If you'd like us to have a look at your code, you may consider sending this information via private message. This feature is available from the drop-down menu offered by the reply button at the top right of the editing windows. 

--
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/c76608a4-7d6d-426e-97f8-1743c2a562a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Communications link failure exception (mysql - cloud sql)

Hi there, we are new with this service. We created a mysql instance and we followed the documentation of using cloud sql for mysql with java (https://cloud.google.com/appengine/docs/standard/java/cloud-sql/using-cloud-sql-mysql). we tested with the sample provided by appengine (https://github.com/GoogleCloudPlatform/java-docs-samples/tree/master/appengine-java8/cloudsql). when deploying we get this exception:

org.eclipse.jetty.servlet.ServletHolder$1: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure 

 The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.

the properties we used to build the link connection is : 

<INSTANCE_CONNECTION_NAME>theplayer-game:us-central1:socialboards</INSTANCE_CONNECTION_NAME>

    <user>root</user>

    <password>password</password>

    <database>sqldemo</database>

Any idea how to handle this ?

Cheers.

--
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/cfa25a23-b3ce-4d96-8fc9-1537868087d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Error importing SQL dump from bucket (exported from Google Cloud Console)

Thank you. This post was a duplicate. I didn't not see the notification saying that the post will be reviewed, and I thought I had lost it, so I wrote another one. 

I was able to get around my import issue by using the Console. I read in another thread that you have to export and import specific databases not a whole instance. 

--
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/fe1b7ffa-8b89-469a-ad19-6d06a84701ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: SQL import error (Cloud SQL exported instance)

Thanks for your reply. 

I was able to get around my import issue by using the Console. I read in another thread that you have to export and import specific databases not a whole instance. 

I will try your method next time. Thank you. 

--
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/31ba2211-6ae5-4bfa-819d-299cb4815c22%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Error importing SQL dump from bucket (exported from Google Cloud Console)

I posted a solution for you issue on this link.

On Wednesday, April 25, 2018 at 12:58:57 PM UTC-4, Brett Peary wrote:

I have a Google App Engine project running Wordpress and everything is working fine on that. I exported the Cloud SQL instance to a bucket in that project and then transferred to a bucket in an new Google App Engine project where I want to import the SQL instance. 

I've tried importing through the Google Cloud Console, but I get an unknown error, so I switched to the command line utility. 

Here are the commands I've run following the doc here... 

https://cloud.google.com/sql/docs/postgres/import-export/importing

gcloud sql instances describe  myapp-wp-db-app-v2

// the serviceAccountEmailAddress (a fake version of it)

hvintl4c5h3uot6h7e5vfxz@sparkle-boots-23.iam.gserviceaccount.com

// gsutil acl ch -u [SERVICE_ACCOUNT_ADDRESS]:W gs://[BUCKET_NAME]

gsutil acl ch -u hvintl4c5h3uot6h7e5vfxz@sparkle-boots-23.iam.gserviceaccount.com:W gs://import-myapp-wp-app-v2

// gsutil acl ch -u [SERVICE_ACCOUNT_ADDRESS]:R gs://[BUCKET_NAME]/[IMPORT_FILE_NAME]

gsutil acl ch -u hvintl4c5h3uot6h7e5vfxz@sparkle-boots-23.iam.gserviceaccount.com:R gs://import-myapp-wp-app-v2/Cloud_SQL_Export_2018-04-24 (20:48:52)/

// gcloud sql import sql [INSTANCE_NAME] gs://[BUCKET_NAME]/[IMPORT_FILE_NAME] \

                            --database=[DATABASE_NAME]

gcloud sql import sql myapp-wp-db-app-v2 gs://import-myapp-wp-app-v2/Cloud_SQL_Export_2018-04-24 (20:48:52)/ \

                            --database=wordpress_db

The last command gives me the following in the command line utility..

Importing data into Cloud SQL instance...failed.

ERROR: (gcloud.sql.import.sql) ERROR_RDBMS

and " gs://import-myapp-wp-app-v2/Cloud_SQL_Export_2018-04-24 (20:48:52)/: Not found (bad bucket name?)" in the Console's operations log.

This command below (without a trailing slash) give me unknown error...

gcloud sql import sql myapp-wp-db-app-v2 gs://import-myapp-wp-app-v2/Cloud_SQL_Export_2018-04-24 (20:48:52) \

                            --database=wordpress_db

The documentation says that if you have "ERROR_RDBMS" that it is probably related to permissions and did not elaborate.Since I exported the SQL dump from Cloud SQL, I thought that it would have the correct permissions need to import back in to Cloud SQL. 

Any idea how to handle this?

Cheers.

--
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/f3fe9b0c-3322-47bb-a56f-5852f18aab29%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: SQL import error (Cloud SQL exported instance)

Hello Brett,

gcloud command uses the credential of user account or service account which is active in the machine you run the command. This account can be verified by running gcloud auth list command. The active account has a asterisk front of it. The following example shows that "myjob@project-1.iam.gserviceaccount.com" is the active account that gcloud command uses it credentials to call APIs. 

me@debian9:~$ gcloud auth list

                  Credentialed Accounts

ACTIVE  ACCOUNT

        100000000000-compute@developer.gserviceaccount.com

*       myjob@project-1.iam.gserviceaccount.com

        k.....@google.com

in your case, you should run the gcloud command with an active account which have enough permissions to be able to read the objects (the exported database file) from the specified bucket and write them to the your Cloud SQL instance.

I hope this helps.

On Wednesday, April 25, 2018 at 12:59:16 PM UTC-4, Brett Peary wrote:

I have a working project with a Cloud SQL database that I want to import into a new project, an exact clone of the working one. 

I exported the SQL instance to a bucket in the working project. I then transfered that SQL dump over to a bucket in the new project. 

From there, I tried importing the SQL dump, but I get an unknown error, so I went moved to the CLI. 

Here are the commands I ran following the docs https://cloud.google.com/sql/docs/postgres/import-export/importing ...

gcloud sql instances describe  myapp-wp-db-app-v2

// serviceAccountEmailAddress in the output (a fake version of it)

5vfxzdlh6h7u43tc5onthaevia@sparkle-boots-27.iam.gserviceaccount.com

// gsutil acl ch -u [SERVICE_ACCOUNT_ADDRESS]:W gs://[BUCKET_NAME]

gsutil acl ch -u 5vfxzdlh6h7u43tc5onthaevia@sparkle-boots-27.iam.gserviceaccount.com:W gs://import-myapp-wp-app-v2

// gsutil acl ch -u [SERVICE_ACCOUNT_ADDRESS]:R gs://[BUCKET_NAME]/[IMPORT_FILE_NAME]

gsutil acl ch -u 5vfxzdlh6h7u43tc5onthaevia@sparkle-boots-27.iam.gserviceaccount.com:R gs://import-myapp-wp-app-v2/Cloud_SQL_Export_2018-04-24 (20:48:52)/

// gcloud sql import sql [INSTANCE_NAME] gs://[BUCKET_NAME]/[IMPORT_FILE_NAME] \

//                            --database=[DATABASE_NAME]

gcloud sql import sql myapp-wp-db-app-v2 gs://import-myapp-wp-app-v2/Cloud_SQL_Export_2018-04-24 (20:48:52)/ \

                            --database=wordpress_db

The last command, in the CLI, give me...

Importing data into Cloud SQL instance...failed.

ERROR: (gcloud.sql.import.sql) ERROR_RDBMS

And "gs://import-myapp-wp-app-v2/Cloud_SQL_Export_2018-04-24 (20:48:52)/: Not found (bad bucket name?)" in the Cloud SQL operations log. 

The same command without the trailing slash after the file name give me

Importing data into Cloud SQL instance...failed.

ERROR: (gcloud.sql.import.sql) INTERNAL_ERROR

And "An unknown error occurred." in the Cloud SQL operations log. 

The docs says that an "ERROR_RDBMS" is likely a permissions problem, but it does not elaborate. I thought that since I had exported from Cloud SQL the SQL dump would be fine for importing into Cloud SQL. 

Any direction would be appreciated. 

Cheers.

--
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/10c78c2e-4a50-4824-9b31-49c3b3158deb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Postgres 10 Support

When will Postgres 10 support be released?   And what is the plan for ongoing postgres releases?

Thanks!

Dave

--
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/b614d414-46d4-4480-8c32-55698de7d5e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Postgres Connections Randomly Dropping

Thanks for the suggestion Dinesh, but I don't think that's it. We are getting the errors much more frequently than there are events in the operations tab. Typically we get 2-3 bursts of errors per day, but there is generally just one operation: a backup. The timing also doesn't necessarily coincide between the events and the errors. Regardless, if the operations were a problem, would turning on HA fix the issue, or would that not help?

Any other ideas about why we could be seeing these connection problems?

Nigel G.

On Wednesday, 25 April 2018 14:17:18 UTC-7, Dinesh (Google Platform Support) wrote:

As you suggesting you receive such errors only for 2-3 minutes in a day, I suspect your instance might be going through maintenance updates (that require an instance restart) during that times.  Please view operational logs of your Postgre SQL instance. You can view them from cloud console GUI inside instance details view, under operations tab. If you find instance was updated at the same time, that explain the cause of these logs. 

If that is the real cause of the mentioned errors, I will recommend configuring the schedule for the Maintenance window and Maintenance timing to avoid any surprises in the future. 

Let me know if this helps?

Regards,

On Wednesday, April 25, 2018 at 12:59:51 PM UTC-4, Nigel Gutzmann wrote:

I have a django and celery application running inside of Google Kubernetes Engine. I am connecting to my CloudSQL instance (postgres) using a Kubernetes service running the CloudSQL Proxy. Database connections and queries generally work fine, but occasionally we get spurts of errors with connections breaking. They are raised in python like this:

OperationalError: could not connect to server: Connection refused Is the server running on host "cloudsql-proxy-service" and accepting TCP/IP connections on port 3306?

or

OperationalError: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request.

I can't find anything that might cause that in the logs of the CloudSQL instance. There are some messages like this in the CloudSQL proxy logs:

2018/04/24 18:55:18 Instance <project_name>:us-central1:<instance_name> closed connection

But I can't necessarily correlate the timestamps between when those messages appear and when we get the python errors. I have tried setting CONN_MAX_AGE and tcp keepalives like this inside django's settings.py:

DATABASES = {

    'default': {

        'ENGINE': 'django.db.backends.postgresql',

        'NAME': '<db_name>',

        'USER': os.environ.get('DB_USER', None),

        'HOST': os.environ.get('DB_HOST', None),

        'PORT': os.environ.get('DB_PORT', None),

        'PASSWORD': os.environ.get('DB_PASSWORD', None),

        'CONN_MAX_AGE': int(os.environ.get('CONN_MAX_AGE', 0)),

        'OPTIONS': {

            'keepalives': 1,

            'keepalives_idle': 480,

            'keepalives_interval': 10,

            'keepalives_count': 3,

        },

    },

}

But that didn't seem to make a difference. We still get the same errors in bunches, about 20 errors over the span of 2-3 minutes, 2-3 times per day.

--
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/045116d9-3ec9-494f-a72e-7853a5d67d8c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Postgres Connections Randomly Dropping

As you suggesting you receive such errors only for 2-3 minutes in a day, I suspect your instance might be going through maintenance updates (that require an instance restart) during that times.  Please view operational logs of your Postgre SQL instance. You can view them from cloud console GUI inside instance details view, under operations tab. If you find instance was updated at the same time, that explain the cause of these logs. 

If that is the real cause of the mentioned errors, I will recommend configuring the schedule for the Maintenance window and Maintenance timing to avoid any surprises in the future. 

Let me know if this helps?

Regards,

On Wednesday, April 25, 2018 at 12:59:51 PM UTC-4, Nigel Gutzmann wrote:

I have a django and celery application running inside of Google Kubernetes Engine. I am connecting to my CloudSQL instance (postgres) using a Kubernetes service running the CloudSQL Proxy. Database connections and queries generally work fine, but occasionally we get spurts of errors with connections breaking. They are raised in python like this:

OperationalError: could not connect to server: Connection refused Is the server running on host "cloudsql-proxy-service" and accepting TCP/IP connections on port 3306?

or

OperationalError: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request.

I can't find anything that might cause that in the logs of the CloudSQL instance. There are some messages like this in the CloudSQL proxy logs:

2018/04/24 18:55:18 Instance <project_name>:us-central1:<instance_name> closed connection

But I can't necessarily correlate the timestamps between when those messages appear and when we get the python errors. I have tried setting CONN_MAX_AGE and tcp keepalives like this inside django's settings.py:

DATABASES = {

    'default': {

        'ENGINE': 'django.db.backends.postgresql',

        'NAME': '<db_name>',

        'USER': os.environ.get('DB_USER', None),

        'HOST': os.environ.get('DB_HOST', None),

        'PORT': os.environ.get('DB_PORT', None),

        'PASSWORD': os.environ.get('DB_PASSWORD', None),

        'CONN_MAX_AGE': int(os.environ.get('CONN_MAX_AGE', 0)),

        'OPTIONS': {

            'keepalives': 1,

            'keepalives_idle': 480,

            'keepalives_interval': 10,

            'keepalives_count': 3,

        },

    },

}

But that didn't seem to make a difference. We still get the same errors in bunches, about 20 errors over the span of 2-3 minutes, 2-3 times per day.

--
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/39d4acf1-fa0f-4672-ab08-019ff6d89ee8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-cloud-sql-discuss] Re: Can not import from storage

It should say this in the docs. Basically, you can't import a whole instance through the console, I guess. An error to that effect would help. Too bad I spent 4 hours trying to figure out why it was not working. 

On Sunday, November 20, 2016 at 9:15:06 AM UTC+9, Vadim Berezniker wrote:

When you perform the export, you should specify the databases you want to export.

The issue stems from the fact that the export you have tries to perform DDL changes on the mysql database which we do not allow. 

Alternatively, edit your existing export to remove any statements that modify the mysql database.

On Fri, Nov 18, 2016 at 1:01 PM Rohit Manglik <rohit....@gmail.com> wrote:

Hi,

I am also getting same error. Is there any workaround for this problem?

 ERROR 1227 (42000) at line 22: Access denied; you need (at least one of) the SUPER privilege(s) for this operation

I am having a down time because of this error.

Any lead?

On Tuesday, 9 August 2016 22:09:12 UTC+5:30, James McManus wrote:

When I attempt to import a file using the console, to cloud sql, from storage I get the following message when I "Browse" for the file:

Object not available. Either it does not exist or you do not have access. Try browsing for the object instead.

I've done this many times before and have not had this problem. I've tried changing permissions on the file, in storage, but have the same problem. I can also can download the file, directly using a url, so I do not think the problem is with storage. 

If I change the path, to the file, in the cloud sql import "Browse" console to:

danudata/danunews%2F2016%2Flatest_news_feed080916.csv

I no longer get the error message, but it then fails to import the data.

This appears to be a problem with google sql import console. Has anybody else had this problem? Are there solutions?

Thanks

Jim

--
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/ccd228e7-95d4-454f-90e2-91cd34c40998%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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/42cb1fcf-ddef-4b7b-a06a-648da02846b8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] SQL import error (Cloud SQL exported instance)

I have a working project with a Cloud SQL database that I want to import into a new project, an exact clone of the working one. 

I exported the SQL instance to a bucket in the working project. I then transfered that SQL dump over to a bucket in the new project. 

From there, I tried importing the SQL dump, but I get an unknown error, so I went moved to the CLI. 

Here are the commands I ran following the docs https://cloud.google.com/sql/docs/postgres/import-export/importing ...

gcloud sql instances describe  myapp-wp-db-app-v2

// serviceAccountEmailAddress in the output (a fake version of it)

5vfxzdlh6h7u43tc5onthaevia@sparkle-boots-27.iam.gserviceaccount.com

// gsutil acl ch -u [SERVICE_ACCOUNT_ADDRESS]:W gs://[BUCKET_NAME]

gsutil acl ch -u 5vfxzdlh6h7u43tc5onthaevia@sparkle-boots-27.iam.gserviceaccount.com:W gs://import-myapp-wp-app-v2

// gsutil acl ch -u [SERVICE_ACCOUNT_ADDRESS]:R gs://[BUCKET_NAME]/[IMPORT_FILE_NAME]

gsutil acl ch -u 5vfxzdlh6h7u43tc5onthaevia@sparkle-boots-27.iam.gserviceaccount.com:R gs://import-myapp-wp-app-v2/Cloud_SQL_Export_2018-04-24 (20:48:52)/

// gcloud sql import sql [INSTANCE_NAME] gs://[BUCKET_NAME]/[IMPORT_FILE_NAME] \

//                            --database=[DATABASE_NAME]

gcloud sql import sql myapp-wp-db-app-v2 gs://import-myapp-wp-app-v2/Cloud_SQL_Export_2018-04-24 (20:48:52)/ \

                            --database=wordpress_db

The last command, in the CLI, give me...

Importing data into Cloud SQL instance...failed.

ERROR: (gcloud.sql.import.sql) ERROR_RDBMS

And "gs://import-myapp-wp-app-v2/Cloud_SQL_Export_2018-04-24 (20:48:52)/: Not found (bad bucket name?)" in the Cloud SQL operations log. 

The same command without the trailing slash after the file name give me

Importing data into Cloud SQL instance...failed.

ERROR: (gcloud.sql.import.sql) INTERNAL_ERROR

And "An unknown error occurred." in the Cloud SQL operations log. 

The docs says that an "ERROR_RDBMS" is likely a permissions problem, but it does not elaborate. I thought that since I had exported from Cloud SQL the SQL dump would be fine for importing into Cloud SQL. 

Any direction would be appreciated. 

Cheers.

--
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/81f00ac9-ffa7-43ce-9aa3-3df4e069f7c5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Postgres Connections Randomly Dropping

I have a django and celery application running inside of Google Kubernetes Engine. I am connecting to my CloudSQL instance (postgres) using a Kubernetes service running the CloudSQL Proxy. Database connections and queries generally work fine, but occasionally we get spurts of errors with connections breaking. They are raised in python like this:

OperationalError: could not connect to server: Connection refused Is the server running on host "cloudsql-proxy-service" and accepting TCP/IP connections on port 3306?

or

OperationalError: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request.

I can't find anything that might cause that in the logs of the CloudSQL instance. There are some messages like this in the CloudSQL proxy logs:

2018/04/24 18:55:18 Instance <project_name>:us-central1:<instance_name> closed connection

But I can't necessarily correlate the timestamps between when those messages appear and when we get the python errors. I have tried setting CONN_MAX_AGE and tcp keepalives like this inside django's settings.py:

DATABASES = {

    'default': {

        'ENGINE': 'django.db.backends.postgresql',

        'NAME': '<db_name>',

        'USER': os.environ.get('DB_USER', None),

        'HOST': os.environ.get('DB_HOST', None),

        'PORT': os.environ.get('DB_PORT', None),

        'PASSWORD': os.environ.get('DB_PASSWORD', None),

        'CONN_MAX_AGE': int(os.environ.get('CONN_MAX_AGE', 0)),

        'OPTIONS': {

            'keepalives': 1,

            'keepalives_idle': 480,

            'keepalives_interval': 10,

            'keepalives_count': 3,

        },

    },

}

But that didn't seem to make a difference. We still get the same errors in bunches, about 20 errors over the span of 2-3 minutes, 2-3 times per day.

--
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/a6aabccc-cab2-4eb1-9a64-4d19df9c45e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Error importing SQL dump from bucket (exported from Google Cloud Console)

I have a Google App Engine project running Wordpress and everything is working fine on that. I exported the Cloud SQL instance to a bucket in that project and then transferred to a bucket in an new Google App Engine project where I want to import the SQL instance. 

I've tried importing through the Google Cloud Console, but I get an unknown error, so I switched to the command line utility. 

Here are the commands I've run following the doc here... 

https://cloud.google.com/sql/docs/postgres/import-export/importing

gcloud sql instances describe  myapp-wp-db-app-v2

// the serviceAccountEmailAddress (a fake version of it)

hvintl4c5h3uot6h7e5vfxz@sparkle-boots-23.iam.gserviceaccount.com

// gsutil acl ch -u [SERVICE_ACCOUNT_ADDRESS]:W gs://[BUCKET_NAME]

gsutil acl ch -u hvintl4c5h3uot6h7e5vfxz@sparkle-boots-23.iam.gserviceaccount.com:W gs://import-myapp-wp-app-v2

// gsutil acl ch -u [SERVICE_ACCOUNT_ADDRESS]:R gs://[BUCKET_NAME]/[IMPORT_FILE_NAME]

gsutil acl ch -u hvintl4c5h3uot6h7e5vfxz@sparkle-boots-23.iam.gserviceaccount.com:R gs://import-myapp-wp-app-v2/Cloud_SQL_Export_2018-04-24 (20:48:52)/

// gcloud sql import sql [INSTANCE_NAME] gs://[BUCKET_NAME]/[IMPORT_FILE_NAME] \

                            --database=[DATABASE_NAME]

gcloud sql import sql myapp-wp-db-app-v2 gs://import-myapp-wp-app-v2/Cloud_SQL_Export_2018-04-24 (20:48:52)/ \

                            --database=wordpress_db

The last command gives me the following in the command line utility..

Importing data into Cloud SQL instance...failed.

ERROR: (gcloud.sql.import.sql) ERROR_RDBMS

and " gs://import-myapp-wp-app-v2/Cloud_SQL_Export_2018-04-24 (20:48:52)/: Not found (bad bucket name?)" in the Console's operations log.

This command below (without a trailing slash) give me unknown error...

gcloud sql import sql myapp-wp-db-app-v2 gs://import-myapp-wp-app-v2/Cloud_SQL_Export_2018-04-24 (20:48:52) \

                            --database=wordpress_db

The documentation says that if you have "ERROR_RDBMS" that it is probably related to permissions and did not elaborate.Since I exported the SQL dump from Cloud SQL, I thought that it would have the correct permissions need to import back in to Cloud SQL. 

Any idea how to handle this?

Cheers.

--
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/a0b4711d-c465-444c-a80d-5f7505892a7c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.