[google-cloud-sql-discuss] Re: Cloud SQL Server: Access from different project in the same Organization (Private IP)

Hi Serg,

Using a Shared VPC would help you achieve that. It works with App Engine Flex, Cloud SQL, as well as Kubernetes Engine, and it connects resources from multiple projects to a common Virtual Private Cloud (VPC) network, and allows them to communicate with each other securely using internal IPs from that network as long as their within the same organization.

To help you get started, you can visit this page for information on how to set up and use a Shared VPC. Hopefully this will help point you in the right direction; please don't hesitate to reply back with any follow-up questions.

--
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/a3e2b3fd-5a22-44d1-9cfb-9af8359949f0%40googlegroups.com.

[google-cloud-sql-discuss] Cloud SQL Server: Access from different project in the same Organization (Private IP)

Hello,

Can you help me understand how to connect App Engine services, Cloud Functions and GKE instances hosted in "Project A" to Cloud SQL Server instance located in "Project B"? SQL Server uses Private IP address and both projects belong to the same Organization.

I have .netcore, nodejs and python clients that use SQL server instance.

Cloud SQL Server seems to work fine with Private IP inside the project.

Thanks,

Sergei

--
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/eb2b99db-9245-44af-b659-e3a3ab9fdd8a%40googlegroups.com.

Re: [google-cloud-sql-discuss] Re: proxy cloud_sql_proxy suddenly gives Error 403: The client is not authorized to make this request., notAuthorized

This is a currently known limitation with Cloud SQL CSV imports and exports (issue #1, issue #2), it appears to be affecting null (\N) and newlines (\n). There is currently no ETA, however, I advise you to press on '+1' to bring more visibility to the issue and CC yourself to stay in the loop whenever there are any new updates.

I'm curious if you have tried importing the CSV file (that you exported from BQ) into Cloud SQL without inserting \N into it?

If you've already tried the above and it did not work, you may want to also consider Dataflow. It can also be used to transfer BigQuery tables to Cloud SQL (see pricing).

--
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/2a003ddc-0115-41ab-94f3-91ae4850d2e8%40googlegroups.com.

[google-cloud-sql-discuss] Re: Cloud SQL Backups Risk

Cloud SQL has two types of Backups locations Default locations and Custom locations. 

For the Default locations Cloud SQL instance stores backup data in two regions for redundancy. If a certain continent has two regions the backup data will remain in the same continent. In case a continent has only one region, for example Australia has only Sydney region for that backup data is also stored in Asia region and for Sao Paulo region data is stored at US centric regions. 

For the Custom locations user has the option to select a location to store the backup data. You can get the list of valid regions here. On the other hand multi-regional locations are large geographic areas which has at least two regions which are used for backups. 

You can save data of Cloud SQL through On-demand backups which you can take any time and through Automated backups it is possible to set a four hour backup window when the backup will be done automatically. This is also possible to disable automated backups. 

You can find the list of stored backups through Console, gcloud or cURL. Unless you are deleting the backups any of the backups you can use for restoring your database.

As for redundancy Google Cloud Platform backing up data of Cloud SQL instance at least in two Regions, so even if something happens to a region another region will still be available for backup data. 

Please note that it is cautioned that if you delete the Cloud SQL instance all data within the instance along with backups will be permanently lost. So in case you decide to delete the Cloud SQL instance but would like to preserve the data you can use Cloud Storage to store these data after exporting it. You can get best practices for importing and exporting data here. 

On Saturday, January 25, 2020 at 10:17:52 PM UTC-5, Mario Alberto Diaz Castellanos wrote:

Hello,

We are using Cloud SQL for storing our customers information. We use the backups provided by GCP. In terms of managing the risk of losing the data, does it make sense that we also would backup this data in AWS, in case of a failure of gcloud providing the backups, or there is a way to make this risk manageable using only GCP provided services?  

--
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/2d8033a2-4c69-4197-bbb0-808b1343e846%40googlegroups.com.

[google-cloud-sql-discuss] Cloud SQL Backups Risk

Hello,

We are using Cloud SQL for storing our customers information. We use the backups provided by GCP. In terms of managing the risk of losing the data, does it make sense that we also would backup this data in AWS, in case of a failure of gcloud providing the backups, or there is a way to make this risk manageable using only GCP provided services?  

--
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/bcefb1dc-dff6-4902-b6c1-5cbf4624d6e1%40googlegroups.com.

[google-cloud-sql-discuss] Re: Got an error reading communication packets and Net packets out of order error

Hi, Albert. 

Actually, the Link could no longer be accessible publicly as project-specific private information were shared on the link. However, the information shared on the link by the CloudSQL Specialist are details about how and why the Aborted Connection errors may be reported. Please view the comment below: 

=====

"Aborted connection nnnn to db:" error message is triggered when an existing connection is not terminated properly, which may look erroneous but is actually perfectly normal. Aborted connections happen because of unclean closure of connection or networking problem between the server and the client, but not because of the server [1].

You should note that this error does not mean that there are problems with your Cloud SQL instance and as far as I know these types of errors in the MySQL logs are harmless but seem to be useful to indicate client side behaviors because of the following:

1) It won't trigger "Aborted connection" error when mysql client closes cleanly.

2) If the proxy client is killed but didn't close mysql client --> The socket connection is still alive.

    a) manually close the socket connection at the client side

    b) OR wait until times out based "wait_timeout" in MySQL server and the connection closed --> "Aborted connection" error.

The official MySQL documentation suggests various reasons why this could happen and some actions to take [2]. And this blog goes into more details on fixes [3].

In conclusion, if you want to reduce such errors in the logs, I'd suggest to:

- cleanly close each connection and this should be fine when your app hits production.

- implement incremental backoff in your code to handle connections when the DB is temporarily unavailable.

Using exponential backoff prevents your application from sending an unhealthy number of connection requests when it can't connect to the database.

I hope this helps. 

[1] https://cloud.google.com/sql/docs/mysql/diagnose-issues#connection

[2] https://dev.mysql.com/doc/refman/8.0/en/communication-errors.html

[3] https://www.percona.com/blog/2016/05/16/mysql-got-an-error-reading-communication-packet-errors/

--
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/e5f4f7cf-9970-43f2-8361-84ecfd72bf7b%40googlegroups.com.

[google-cloud-sql-discuss] Re: MySQL 8.0 support

Hi, Jay

The Cloud SQL product manager earlier advised that announcements about MySQL 8.0 support will be made in the Announce group[1] and in Release Notes[2].

Likewise, there is a feature request open for the implementation. You can follow the information shared on that link for regular updates on the implementation. However, there is still no ETA at the moment. 

[1]https://groups.google.com/forum/#!forum/google-cloud-sql-announce

[2]https://cloud.google.com/sql/docs/release-notes

[3]https://issuetracker.google.com/79910725

--
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/b88cd700-d39e-4ed0-b816-e4b6c08008cb%40googlegroups.com.

Re: [google-cloud-sql-discuss] Re: proxy cloud_sql_proxy suddenly gives Error 403: The client is not authorized to make this request., notAuthorized

The issue in the end had nothing to do with bucket access for the SQL instance's service account, the issue was that the import task-launching service account needed to have cloud.sql.admin role; apparently editor, viewer, and client are inadequate to run an import job. 

Now, I encounter a new issue: gcloud sql import csv for a Mysql database ignores the csv file's NULL values (mysqlimport requires empty/missing fields contain a '\N' value, otherwise the import overrides the default NULL value setting and inserts a zero value or empty string), which BQ extract csv does not insert, so I have to programmatically insert \N into our BQ extract csv files before attempting to upload them.

So, to clarify, I've found that cloud sql import csv does not correctly interpret \N nor missing values as meaning "INSERT NULL", it inserts the literal \N value or 0 values. mysqlimport utility, with some finagling, seems to recognize the \N values as meaning NULL, but it's finicky and easily misinterprets.

On Friday, January 24, 2020 at 5:57:47 AM UTC+9, Jad El Houssami wrote:

Hello Christopher, 

I can understand how inconvenient it can be to run into permission issues when trying to set up an ETL job. From my understanding, you have a service account being used to launch the import task and it already has all the Cloud SQL roles. Once the import task is launched, you have given the SQL instance's service account permission to access the GCS bucket.

From the Cloud SQL documentation, it explains: "To import data from Cloud Storage, the instance's service account needs to have the Bucket Reader ACL permission set in the project." In other words, the service account needs to have the 'roles/storage.legacyBucketReader' role which is equivalent to the 'Bucket Reader' ACL permission. Are you able to confirm if you have already granted that role to your Cloud SQL instance's service account?

Additionally, if you prefer not to give the import task service account the role of project-wide editor, it was previously suggested to try granting it the "roles/cloudsql.client" role instead, have you already given that a try?

--
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/8424c1d8-001b-4654-b6d6-7f2af4a33a85%40googlegroups.com.

Re: [google-cloud-sql-discuss] Re: proxy cloud_sql_proxy suddenly gives Error 403: The client is not authorized to make this request., notAuthorized

Hello Christopher, 

I can understand how inconvenient it can be to run into permission issues when trying to set up an ETL job. From my understanding, you have a service account being used to launch the import task and it already has all the Cloud SQL roles. Once the import task is launched, you have given the SQL instance's service account permission to access the GCS bucket.

From the Cloud SQL documentation, it explains: "To import data from Cloud Storage, the instance's service account needs to have the Bucket Reader ACL permission set in the project." In other words, the service account needs to have the 'roles/storage.legacyBucketReader' role which is equivalent to the 'Bucket Reader' ACL permission. Are you able to confirm if you have already granted that role to your Cloud SQL instance's service account?

Additionally, if you prefer not to give the import task service account the role of project-wide editor, it was previously suggested to try granting it the "roles/cloudsql.client" role instead, have you already given that a try?

--
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/e5fc3185-5bd4-4f1b-a369-8eb8eeaa20fd%40googlegroups.com.

[google-cloud-sql-discuss] Re: Got an error reading communication packets and Net packets out of order error

Hi Amit,

I apparently don't have permission to view the contents of that post. Could you perhaps share it here? We have addressed all of the know possible causes for the error and yet it persists. Thanks!

On Friday, June 14, 2019 at 12:37:20 PM UTC-7, Amit Sinha wrote:

Hello Melki,

Thank you for your reply.

As mentioned by Nicolas, this post has detailed description regarding the error. I would recommend to go through the link and see if it answers your concern.

On Thursday, June 13, 2019 at 5:47:33 PM UTC-4, Melki Saputro wrote:

I'm having the same issue. When Google will fix this or give us hint how to fix it. If not in 2 months i will change GCP with other Cloud Services.

On Friday, August 18, 2017 at 8:24:56 PM UTC+7, Stenn Kool wrote:

I'm seeing the "Got an error reading communication packets" error in the error log and the "Net packets out of order" message in my applications, those applications are written in different languages and running on different connections.

Some of them are running om GKE and others on premise, it seems to happen when A lot of data is being inserted.

Our SQL servers hosted by a different hosting provider have no such issues while under the same load with similar specs.

We've already tried using another connection and increasing the max_allowed_packet flag.

The server is running with a failover and is using the binlog.

example errors from the log:

E  2017-08-18T12:09:41.883032Z 344745 [Note] Aborted connection 344745 to db: '***' user: '***' host: '***.***.***.***' (Got an error reading communication packets) 
E  2017-08-18T12:11:12.061786Z 362326 [Note] Aborted connection 362326 to db: '***' user: '***' host: '***.***.***.***' (Got timeout reading communication packets) 



E  2017-08-18T13:22:07.443999Z 10400 [Note] Aborted connection 10400 to db: 'cms' user: '***' host: 'cloudsqlproxy~***' (Got an error reading communication packets) 
E  2017-08-18T13:22:07.447055Z 10459 [Note] Aborted connection 10459 to db: 'cms' user: '***' host: 'cloudsqlproxy~***' (Got an error reading communication packets) 
E  2017-08-18T13:22:11.617081Z 10509 [Note] Aborted connection 10509 to db: 'cms' user: '***' host: 'cloudsqlproxy~***' (Got an error reading communication packets) 
E  2017-08-18T13:22:12.841405Z 9892 [Note] Aborted connection 9892 to db: 'cms' user: '***' host: 'cloudsqlproxy~***' (Got timeout reading communication packets) 

--
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/5b44307f-8f72-4d40-ab29-a33bb10623f0%40googlegroups.com.

[google-cloud-sql-discuss] Re: MySQL 8.0 support

Hey Google, your customers have updated this to No.1 by a large margin. https://googlecloudplatform.uservoice.com/forums/302613-cloud-sql/suggestions/35244256-mysql-8-0-support?page=1&per_page=20

where/when do we actually get a response from you?

Thanks

On Friday, April 12, 2019 at 9:33:55 AM UTC-4, Tim Holme wrote:

We urgently need cloud managed MySQL 8 please!

On Friday, November 30, 2018 at 5:07:20 PM UTC-8, Katayoon (Cloud Platform Support) wrote:

Hi,

You may follow this feature request which already exists in the Issue Tracker via this link. I transferred your interest on having MySQL 8.0 support to Google Cloud SQL product team 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/b720e8f9-b94d-483d-9ceb-89f868a80a6e%40googlegroups.com.

Re: [google-cloud-sql-discuss] Re: proxy cloud_sql_proxy suddenly gives Error 403: The client is not authorized to make this request., notAuthorized

Almost 3 years later, and I am running into this issue, trying to set up an ETL job for my organization, to import a csv file from GCS into a Cloud SQL instance. The only time it has been possible so far is to make the service account a project-wide editor, which is obviously not desirable for us. It was also necessary to add the SQL instance's service account to the GCS bucket's permissions list, but that is insufficient. The service account being used to launch the import task has all of the Cloud SQL roles available already: Editor, Viewer, Client.

On Friday, March 3, 2017 at 8:11:35 AM UTC+9, David Newgas wrote:

I also looked into this earlier (https://groups.google.com/d/topic/google-cloud-sql-discuss/5jU0Upr7uqY/discussion). Nick is correct, and we are also trying to address fix this so that cloudsql.client is sufficient. I don't believe our fix is in prod yet though, so follow nick's advice in the mean time.

On Thu, Mar 2, 2017 at 2:59 PM, 'paynen' via Google Cloud SQL discuss <google-cloud...@googlegroups.com> wrote:

Hey Pierfrancesco,

That seems like a strange error - you'd think if it was an auth issue, it would be all-or-nothing, or else it might occur after only 1 hour (maybe an oauth token timeout issue, where usually 3600 seconds - or 1 hour - is the timeout when a refresh token is needed).

However, thankfully it appears that this is a known issue reported on the Cloud SQL github page. 9 days ago, a user "abstrctn" had the same issue (from the sounds of it), and they resolved it by adding the "roles/cloudsql.client" role to the service account. Other users said that adding the service account as a project editor resolved the issue, so that would be worth checking as well.

Could you see about whether that resolves the issue and let me know? I'll be happy to answer any additional questions you have as well.

Cheers,

Nick
Cloud Platform Community Support

On Wednesday, March 1, 2017 at 7:20:32 PM UTC-5, Pierfrancesco Marsiaj wrote:

I have an SQL cloud instance and a compute Engine with a Centos 7 VM on different projects. I use Utilizzo l'SQL proxy cloud_sql_proxy to connect to the SQL instance with mysql CLI client and via php-mysql (wordpress). accesses are configured properly, VM's service account has a role of SQL administrator on the SQL instance. everything works fine for 30-40 minutes, I can run mysql CLI commands, wordpress works fine.

then suddenly I get on the proxy console: 

2017/03/01 23:17:44 couldn't connect to "database-xxxx:europe-west1:xxxx": ensure that the account has access to "database-xxxx:europe-west1:xxxx" (and make sure there's no typo in that name). Error during createEphemeral for database-xxxx:europe-west1:xxxx: googleapi: Error 403: The client is not authorized to make this request., notAuthorized

and the mysql connection is lost. I tried the proxy authenticated as service account (VM has SQL apis enabled) AND with a service account created on purpose to run the proxy authenticated with the  -credential-file option and the private JSON generated for that service account. works for a while, sometimes 10 minutes, sometimes an hour, maybe more, and then suddenly I get "notAuthorized" errors.

closing and restarting the proxy doesn't help, closing and reopening the SQL connection doesn't help either. 

This happens at differents times of the day, mornings, afternoons, evenings, nights. 

Are there stability issues with this infrastructure? It seems totally unreliable. 

Really reluctant to put my production server here until I don't understand what's going on.

--
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/7ca5799f-4874-49be-ba7f-d7e272f989e3%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/0f2f4082-d78a-4c3f-a9b1-f5d865851574%40googlegroups.com.

Re: [google-cloud-sql-discuss] Re: I have no idea how to resovled this problem when I tried to restore a MySQL database

thanks for replying,I really appreciate it,I have resolved this problem

On Sat, Jan 18, 2020 at 1:08 AM 'Amit Sinha' via Google Cloud SQL discuss <google-cloud-sql-discuss@googlegroups.com> wrote:

Hello,

Could you please try exporting the sql dump using the instruction here and then import it? As mentioned in the note "These instructions exclude all triggers, stored procedures, views, and functions from the export. This is needed to enable Cloud SQL to import the dump file. If your database relies on any of these elements, you must manually recreate them after importing."


On Thursday, January 16, 2020 at 9:51:30 AM UTC-5, asjdfkasjkf kasjfksjfk wrote:

sorry for getting back you late,I apperciated

On Wednesday, January 15, 2020 at 1:52:55 AM UTC+8, Aref Amiri (Cloud Platform Support) wrote:

This error occurs when you try to import a file that contains elements that cannot be imported into Cloud SQL. Your exported file might include DEFINER clauses, that means that it contains one or more triggers, views, or stored procedures. I would suggest following the instruction provided here to avoid such errors.

--
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/61209b84-9241-4e09-808b-fb098b210d50%40googlegroups.com.

--
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/CAHhxvqOZt9cLpump_Mx9h8Q2vvrf60oY0L_OFiZy0xSmVmcnrg%40mail.gmail.com.

[google-cloud-sql-discuss] Re: I have no idea how to resovled this problem when I tried to restore a MySQL database

Hello,

Could you please try exporting the sql dump using the instruction here and then import it? As mentioned in the note "These instructions exclude all triggers, stored procedures, views, and functions from the export. This is needed to enable Cloud SQL to import the dump file. If your database relies on any of these elements, you must manually recreate them after importing."


On Thursday, January 16, 2020 at 9:51:30 AM UTC-5, asjdfkasjkf kasjfksjfk wrote:

sorry for getting back you late,I apperciated

On Wednesday, January 15, 2020 at 1:52:55 AM UTC+8, Aref Amiri (Cloud Platform Support) wrote:

This error occurs when you try to import a file that contains elements that cannot be imported into Cloud SQL. Your exported file might include DEFINER clauses, that means that it contains one or more triggers, views, or stored procedures. I would suggest following the instruction provided here to avoid such errors.

--
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/61209b84-9241-4e09-808b-fb098b210d50%40googlegroups.com.

[google-cloud-sql-discuss] Re: I have no idea how to resovled this problem when I tried to restore a MySQL database

Hey there,I have watched this link

https://stackoverflow.com/questions/39221261/triggers-cloud-sql-2nd-generation

and even I have set log_bin_trust_function_creators to be on within the flag confgiuare on the MySQL instance configuration,but it doesn' work as well

On Wednesday, January 15, 2020 at 1:52:55 AM UTC+8, Aref Amiri (Cloud Platform Support) wrote:

This error occurs when you try to import a file that contains elements that cannot be imported into Cloud SQL. Your exported file might include DEFINER clauses, that means that it contains one or more triggers, views, or stored procedures. I would suggest following the instruction provided here to avoid such errors.

--
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/315ef842-c252-41c9-be57-4f3960e8de3d%40googlegroups.com.

[google-cloud-sql-discuss] Re: I have no idea how to resovled this problem when I tried to restore a MySQL database

sorry for getting back you late,I apperciated

On Wednesday, January 15, 2020 at 1:52:55 AM UTC+8, Aref Amiri (Cloud Platform Support) wrote:

This error occurs when you try to import a file that contains elements that cannot be imported into Cloud SQL. Your exported file might include DEFINER clauses, that means that it contains one or more triggers, views, or stored procedures. I would suggest following the instruction provided here to avoid such errors.

--
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/24018535-31b3-4df3-a9e1-66b7638ab10f%40googlegroups.com.

[google-cloud-sql-discuss] Re: Connection failed to the Mysql database

Hello Ajit, 

Thank you for using the Google Group.

Did you follow any documentation to connect with the database? This might need to investigate further to find the issue here. So I would recommend opening a private issue in the issue tracker and providing more information regarding the issue such as the steps that you followed including the project ID and database name that you are trying to connect so we can investigate further. 

On Monday, January 13, 2020 at 1:04:13 PM UTC-5, ajit sahoo wrote:

Error: Connection failed: php_network_getaddresses: getaddrinfo failed: Name or service not known

Code: 

<?php

$servername = "34.68.186.29";

$username = "root";

$password = "root";

$dsn = "mysql:dbname=myage;unix_socket=/cloudsql/xxxx-xx-xx-xxxxxxdac1fe3f8506:us-central1:irs"; 

// Create connection

$conn = new mysqli($dsn, $severname, $username, $password);

.

.

.

?>

app.yaml file: Refer to the screenshot

FYI:

API: App Engine Admin API Enabled

--
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/c9b78818-3579-4583-b103-6b1260c27b2b%40googlegroups.com.

[google-cloud-sql-discuss] Re: I have no idea how to resovled this problem when I tried to restore a MySQL database

This error occurs when you try to import a file that contains elements that cannot be imported into Cloud SQL. Your exported file might include DEFINER clauses, that means that it contains one or more triggers, views, or stored procedures. I would suggest following the instruction provided here to avoid such errors.

--
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/8541ab7f-0990-4603-b2ce-2ff1f8fc15cd%40googlegroups.com.

[google-cloud-sql-discuss] Connection failed to the Mysql database

Error: Connection failed: php_network_getaddresses: getaddrinfo failed: Name or service not known

Code: 

<?php

$servername = "34.68.186.29";

$username = "root";

$password = "root";

$dsn = "mysql:dbname=myage;unix_socket=/cloudsql/xxxx-xx-xx-xxxxxxdac1fe3f8506:us-central1:irs"; 

// Create connection

$conn = new mysqli($dsn, $severname, $username, $password);

.

.

.

?>

app.yaml file: Refer to the screenshot

FYI:

API: App Engine Admin API Enabled

--
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/121affdf-133d-413b-a276-9cb7f29e357a%40googlegroups.com.

[google-cloud-sql-discuss] I have no idea how to resovled this problem when I tried to restore a MySQL database

Hey guys ,I uploaded my database backup file which was a sql file to GCP storage,then I tried to import this backup file into the MySQL vm,after a while it occured ths exception

Import failed: Import error: exit status 1 ERROR 1227 (42000) at line 10871: Access denied; you need (at least one of) the SUPER privilege(s) for this operation

it can't be resolved anyway though,it's impossible to grant super privilleges to any users in MySQL vm though

--
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/896594df-21f7-490d-97a2-4aaa59f46b91%40googlegroups.com.

Re: [google-cloud-sql-discuss] Re: couldn't connect to "connection-string": dial tcp X.X.X.X:3307: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed

Thank you for the update. I will begin configuring them today. I appreciate you help with this issue. 

On Wed, Jan 8, 2020 at 12:59 PM 'George (Cloud Platform Support)' via Google Cloud SQL discuss <google-cloud-sql-discuss@googlegroups.com> wrote:

Hello Wouter, 

You need to implemented a VPC peering connection between your VPC network and the Google services VPC network where your Cloud SQL instance resides. There are other conditions for successful connectivity, all described on the "Private IP" documentation page. How do your settings compare with the requirements on this page? You may also check requirements on About the Cloud SQL Proxy. 

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/6999b7aa-8e40-4afa-847c-fee2135ca7dc%40googlegroups.com.

--

Barry Tarlton | serviceworksmarketing.com | 770-557-9541 | barry.tarlton@serviceworksmarketing.com

--
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/CAHYJuEU7x_KLmUywameGHP8RZZUfuskTTtdbsWD9Zt1W2wzCxg%40mail.gmail.com.

[google-cloud-sql-discuss] Re: Set SQL Server connections to TLSv1.0

It is not possible to set the the TLS version for the database, as it uses the latest and most secure version. It is not recommended to downgrade security to 1.0, and if clients are still using this version it would be best to upgrade them. This is recommended by Microsoft for SQL Server [1].

If you have and outdated application that doesn't support a version of TLS that is compatible with SQL Server, you can always use the Cloud SQL proxy [2] to encrypt connections.

[1] https://support.microsoft.com/en-us/help/3135244/tls-1-2-support-for-microsoft-sql-server

[2] https://cloud.google.com/sql/docs/sqlserver/sql-proxy

On Thursday, January 9, 2020 at 9:50:49 AM UTC-5, Leandro Barbosa wrote:

Greetings

How to set the database connection encryption to   TLSv1.0  instead of  TLSv1.2.    Thanks

Leandro and Lucas

--
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/1beb5acf-628a-4505-af00-8e60868a77df%40googlegroups.com.

[google-cloud-sql-discuss] Set SQL Server connections to TLSv1.0

Greetings

How to set the database connection encryption to   TLSv1.0  instead of  TLSv1.2.    Thanks

Leandro and Lucas

--
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/ee8e4011-db66-4b89-b94f-b1a8b1a440f0%40googlegroups.com.

[google-cloud-sql-discuss] Re: couldn't connect to "connection-string": dial tcp X.X.X.X:3307: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed

Hello Wouter, 

You need to implemented a VPC peering connection between your VPC network and the Google services VPC network where your Cloud SQL instance resides. There are other conditions for successful connectivity, all described on the "Private IP" documentation page. How do your settings compare with the requirements on this page? You may also check requirements on About the Cloud SQL Proxy. 

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/6999b7aa-8e40-4afa-847c-fee2135ca7dc%40googlegroups.com.

[google-cloud-sql-discuss] couldn't connect to "connection-string": dial tcp X.X.X.X:3307: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to

I'm trying to use the cloud SQL proxy to connect to a MySQL instance that only has a private IP. The proxy starts just fine using this command:

cloud_sql_proxy -instances=connection-string=tcp:3310

However, when I try to connect with mysql in a different window, I can enter a password, but after a few seconds, the connection drops, and the proxy shows this message:

couldn't connect to "connection-string": dial tcp X.X.X.X:3307: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

When I look at the logs in GCP, the incoming connection is shown and seems to be allowed (somewhere in the log json, it says granted: true). However, it appears the proxy either doesn't receive the response from the SQL instance, or is unable to parse it.

I tried opening up all possible firewall rules, but that changes nothing. I also tried all suggestions mentioned here: https://github.com/GoogleCloudPlatform/cloudsql-proxy/issues/164

Does anyone have any idea what's going on? Google documentation is really lacking here.

--
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/e90488dc-f6da-4e42-969c-98aa8cfcde93%40googlegroups.com.

Re: [google-cloud-sql-discuss] Re: Enterprise Cloud SQL Masking

Thank you!

Am Fr., 3. Jan. 2020 um 19:32 Uhr schrieb 'Jad El Houssami' via Google Cloud SQL discuss <google-cloud-sql-discuss@googlegroups.com>:

Hello Ashwin, 

It is not possible to install Enterprise Masking and De-identification on CloudSQL instances because that would require the "INSTALL PLUGIN" statement which is not supported by CloudSQL (see "Unsupported statements").

As a workaround, you can install your MySQL databases on Google Compute Engine (GCE) instances instead. Those instances will have to be managed by you, however it will allow you to use the statements required to install Masking and De-identification. You may estimate the costs of using GCE instances using the Google Cloud Platform Pricing Calculator.

--
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/2f96dddd-2221-4ef3-8583-67d9715b3a2e%40googlegroups.com.

--

Ashwin Purohit

Director of Operations, EMEA | Lilt GmbH, Berlin

--
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/CAEfoz4godY%3D9u80tkbjJOjSpeAAaye7cGWEN_yw3ZPZZg%2BO1jg%40mail.gmail.com.

[google-cloud-sql-discuss] Re: Enterprise Cloud SQL Masking

Hello Ashwin, 

It is not possible to install Enterprise Masking and De-identification on CloudSQL instances because that would require the "INSTALL PLUGIN" statement which is not supported by CloudSQL (see "Unsupported statements").

As a workaround, you can install your MySQL databases on Google Compute Engine (GCE) instances instead. Those instances will have to be managed by you, however it will allow you to use the statements required to install Masking and De-identification. You may estimate the costs of using GCE instances using the Google Cloud Platform Pricing Calculator.

--
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/2f96dddd-2221-4ef3-8583-67d9715b3a2e%40googlegroups.com.

[google-cloud-sql-discuss] Enterprise Cloud SQL Masking

Is there a way to enable MySQL's Enterprise Masking and De-identification (https://www.mysql.com/de/products/enterprise/masking.html) on Google Cloud SQL? We could pay for a license, I just don't know if this is possible. If this is not possible, does anyone know a way around this that isn't as expensive as DataSunrise (which costs 8k yearly per instance + 6k for all further instances)?

--
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/d00affa3-8405-474e-8aac-9fe211629b66%40googlegroups.com.