[google-cloud-sql-discuss] Re: Google Cloud SQL instance stuck at restart

Hey Jad,

Is this issue still occurring for you? If so, or in future, you should post to the Cloud SQL Public Issue Tracker and include your instance and project name, so we can take a look.

Cheers,

Nick
Cloud Platform Community Support

On Thursday, January 19, 2017 at 10:38:53 AM UTC-5, Jad Kaadi wrote:

Google Cloud SQL instance has been stuck at restart since 1 hour. I cannot do anything with it. What is the solution?

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/83a2c8d7-4f91-48f9-8040-fc1117885f56%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-cloud-sql-discuss] Backup restore to different instance, in different project

Thanks for the context - use cases are really helpful for feature requests!

David

On Tue, Jan 24, 2017 at 10:35 AM, Dan Gardner <dan.gardner@baddogdown.com> wrote:

Thanks David,  I agree.  Was hoping to avoid replacing the CloudSQL backup strategy with rolling our own, but hey ho.  Just FYI our use case is that we need to segregate environments by GCP project +  I always like a daily automatic backsync data from a Production environment back through TEST,SI Ci etc.  I also like to utilise a backup / restore approach as an easy way to also verify the Production backup into the bargain.  Thx.

 

On Tuesday, 24 January 2017 18:08:31 UTC, David Newgas wrote:

Hi,

I just dug into our code and I can confirm that there is not currently a way to do this via our API. I can see that we do have an feature request open internally for this, and I will mention that you are interested in this on it. However I don't expect that it will be implemented in the short term.

The "next best thing" is to restore to an instance in the same project, export the database to GCS and then import it into an instance in another project.

Yours,

David

On Tue, Jan 24, 2017 at 6:53 AM, Dan Gardner <dan.g...@baddogdown.com> wrote:

I'm failing to restore a backup from a source instance to a target instance when each instance is in a different project.  Is this simply not supported ?

I get ambiguous permissions error from the target instance restore cmd**.   Also if I look in the console no option is offered to target instances in diff projects,  resonable I suppose for thr console.  

I guess unless you can pass a project in the restoreBackupContext json, as below, this isn't supported yet ?

  

**  below from https://cloud.google.com/sql/docs/mysql/backup-recovery/restoring#restorebackups   

curl --header "Authorization: Bearer ${ACCESS_TOKEN}" \
     --header 'Content-Type: application/json' \
     --data '{ "restoreBackupContext": {"backupRunId": "[BACKUP_ID]", "instanceId": "[SOURCE_INSTANCE_NAME]", "kind": "sql#restoreBackupContext"}}' \
     -X POST \
     https://www.googleapis.com/sql/v1beta4/projects/[PROJECT-ID]/instances/[TARGET_INSTANCE_NAME]/restoreBackup

--
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/75aa9ab4-fbd2-48cb-96c3-f6ee4b2a86be%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/303fedf5-292a-43ca-befc-a83a5ac5e8ee%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/CAJZK_bYkVdOt0H6_M3d--NjPkpC_e5%3DTyTr3f5Oe3d%3D4wzX-MA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-cloud-sql-discuss] Backup restore to different instance, in different project

Thanks David,  I agree.  Was hoping to avoid replacing the CloudSQL backup strategy with rolling our own, but hey ho.  Just FYI our use case is that we need to segregate environments by GCP project +  I always like a daily automatic backsync data from a Production environment back through TEST,SI Ci etc.  I also like to utilise a backup / restore approach as an easy way to also verify the Production backup into the bargain.  Thx.

 

On Tuesday, 24 January 2017 18:08:31 UTC, David Newgas wrote:

Hi,

I just dug into our code and I can confirm that there is not currently a way to do this via our API. I can see that we do have an feature request open internally for this, and I will mention that you are interested in this on it. However I don't expect that it will be implemented in the short term.

The "next best thing" is to restore to an instance in the same project, export the database to GCS and then import it into an instance in another project.

Yours,

David

On Tue, Jan 24, 2017 at 6:53 AM, Dan Gardner <dan.g...@baddogdown.com> wrote:

I'm failing to restore a backup from a source instance to a target instance when each instance is in a different project.  Is this simply not supported ?

I get ambiguous permissions error from the target instance restore cmd**.   Also if I look in the console no option is offered to target instances in diff projects,  resonable I suppose for thr console.  

I guess unless you can pass a project in the restoreBackupContext json, as below, this isn't supported yet ?

  

**  below from https://cloud.google.com/sql/docs/mysql/backup-recovery/restoring#restorebackups   

curl --header "Authorization: Bearer ${ACCESS_TOKEN}" \
     --header 'Content-Type: application/json' \
     --data '{ "restoreBackupContext": {"backupRunId": "[BACKUP_ID]", "instanceId": "[SOURCE_INSTANCE_NAME]", "kind": "sql#restoreBackupContext"}}' \
     -X POST \
     https://www.googleapis.com/sql/v1beta4/projects/[PROJECT-ID]/instances/[TARGET_INSTANCE_NAME]/restoreBackup

--
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/75aa9ab4-fbd2-48cb-96c3-f6ee4b2a86be%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/303fedf5-292a-43ca-befc-a83a5ac5e8ee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-cloud-sql-discuss] Backup restore to different instance, in different project

Hi,

I just dug into our code and I can confirm that there is not currently a way to do this via our API. I can see that we do have an feature request open internally for this, and I will mention that you are interested in this on it. However I don't expect that it will be implemented in the short term.

The "next best thing" is to restore to an instance in the same project, export the database to GCS and then import it into an instance in another project.

Yours,

David

On Tue, Jan 24, 2017 at 6:53 AM, Dan Gardner <dan.gardner@baddogdown.com> wrote:

I'm failing to restore a backup from a source instance to a target instance when each instance is in a different project.  Is this simply not supported ?

I get ambiguous permissions error from the target instance restore cmd**.   Also if I look in the console no option is offered to target instances in diff projects,  resonable I suppose for thr console.  

I guess unless you can pass a project in the restoreBackupContext json, as below, this isn't supported yet ?

  

**  below from https://cloud.google.com/sql/docs/mysql/backup-recovery/restoring#restorebackups   

curl --header "Authorization: Bearer ${ACCESS_TOKEN}" \
     --header 'Content-Type: application/json' \
     --data '{ "restoreBackupContext": {"backupRunId": "[BACKUP_ID]", "instanceId": "[SOURCE_INSTANCE_NAME]", "kind": "sql#restoreBackupContext"}}' \
     -X POST \
     https://www.googleapis.com/sql/v1beta4/projects/[PROJECT-ID]/instances/[TARGET_INSTANCE_NAME]/restoreBackup

--
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/75aa9ab4-fbd2-48cb-96c3-f6ee4b2a86be%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/CAJZK_baFuzNGqrkdnCvAd05XAVLPFFWNWEPjrDbS6AxsLaBsKw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Backup restore to different instance, in different project

I'm failing to restore a backup from a source instance to a target instance when each instance is in a different project.  Is this simply not supported ?

I get ambiguous permissions error from the target instance restore cmd**.   Also if I look in the console no option is offered to target instances in diff projects,  resonable I suppose for thr console.  

I guess unless you can pass a project in the restoreBackupContext json, as below, this isn't supported yet ?

  

**  below from https://cloud.google.com/sql/docs/mysql/backup-recovery/restoring#restorebackups   

curl --header "Authorization: Bearer ${ACCESS_TOKEN}" \
     --header 'Content-Type: application/json' \
     --data '{ "restoreBackupContext": {"backupRunId": "[BACKUP_ID]", "instanceId": "[SOURCE_INSTANCE_NAME]", "kind": "sql#restoreBackupContext"}}' \
     -X POST \
     https://www.googleapis.com/sql/v1beta4/projects/[PROJECT-ID]/instances/[TARGET_INSTANCE_NAME]/restoreBackup

--
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/75aa9ab4-fbd2-48cb-96c3-f6ee4b2a86be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Error Dropping Database (Can't rmdir '.database\', errno: 39)

I just saw your issue on the googleappengine tracker, so I'll follow up there.

On Friday, January 20, 2017 at 12:28:19 PM UTC-5, erwin boc wrote:

I was restoring the database in an instance of cloud sql but for internet connection this fault and now I throw error in a table and when I want to delete the database I generate the following error    Error Dropping Database (Can't rmdir '.database\', errno: 39)

--
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/2a127852-666e-4689-87ce-2db1831c828f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Error Dropping Database (Can't rmdir '.database\', errno: 39)

If recreating the database is not an option, please open an issue at https://code.google.com/p/googlecloudsql/issues/list and request it to be manually removed, or send me a private message with the project id, instance name and database name.

This error occurs when there are extra files left over in the directory '.database\' (errno: 39 is 'directory not empty') but since Cloud SQL is managed you would not have access to remove these yourself.

On Friday, January 20, 2017 at 12:28:19 PM UTC-5, erwin boc wrote:

I was restoring the database in an instance of cloud sql but for internet connection this fault and now I throw error in a table and when I want to delete the database I generate the following error    Error Dropping Database (Can't rmdir '.database\', errno: 39)

--
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/cf3dbf3b-cee5-48e5-80c7-6833350e196c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Error Dropping Database (Can't rmdir '.database\', errno: 39)

I was restoring the database in an instance of cloud sql but for internet connection this fault and now I throw error in a table and when I want to delete the database I generate the following error    Error Dropping Database (Can't rmdir '.database\', errno: 39)

--
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/95b6c6a6-377c-4ddc-b8e5-9eea1745ae2a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Google Cloud SQL instance stuck at restart

Google Cloud SQL instance has been stuck at restart since 1 hour. I cannot do anything with it. What is the solution?

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/b070ceeb-0013-45dd-80e3-652508bbd793%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Cloud SQL periodic issues connecting OperationalError: (2062, 'Cloud SQL socket open failed with error: Transport endpoint is not connected')

Periodically connection attempts to the 2nd Gen MySQL server receives this error:

OperationalError: (2062, 'Cloud SQL socket open failed with error: Transport endpoint is not connected')




This will persist for ~10 minutes and then go away. It also seems to happen at the same time every day (across 3 different projects that all access the same server it'll happen for the first time within 2 minutes).

The only reference to this error in conjunction with Cloud SQL I could find is that it may be related to connection limits (https://groups.google.com/d/msg/google-cloud-sql-discuss/sdeD17oDBOQ/wtTewl4-EgAJ) but there is very little else going on with the instance outside of one TaskQueue task so I find it unlikely we're hitting even the 12 per-instance limit (and definitely not the 4k overall limit).

The code that causes this exception uses the same DB settings as the rest of the app and is simply trying toSELECT a row by primary key (so a small query).

In the DB logs there are a lot of entries of this error:

[Note] Aborted connection 39643 to db: 'my_schema' user: 'root' host: 'cloudsqlproxy~<instance_ip>' (Got an error reading communication packets)

but I'm not sure if they're related as they occur pretty consistently throughout the day and the above error only occurs at a certain time for ~10 minutes.

This only started after upgrading to 2nd Gen Cloud SQL.

Any insights on this? Is there some sort of instance maintenance that may be causing this?

Thanks!

--
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/a9dc8323-cfc4-4a4e-92c1-8b0cfb4e08aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Sql instance restarted

Hello
Yesterday my customer called me and told me the data in the database was not actual anymore. I checked and i saw in console that at 18:45 yesterday Google restarted sql instance. But i was not notified and i think this is the reason the last backup of the day before was restored ? This is strange right ? Does anyobe know how it works when sql instance is restarted ? Does Google do this without telling me and am i right that last cloud backup is restored automatically then ?
--
DISCLAIMER:

*The information contained in this message may be confidential or
privileged and is only intended for the use of the addressee. If you are
not the intended recipient, you are requested by Qualogy to report this to
the sender and to delete the message and you are notified that the use or
distribution of the information contained in this message is strictly
prohibited and unlawful.*

--
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/09e62271-722b-419a-9e5e-f7df87d44da0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: SQL instance is not responding

Hey Adrian,

This issue corresponds to one which we've identified on other Cloud SQL instances. The instance becomes unresponsive after the CPU and memory usage spike. In your case, the instance spiked above around 2.8 G (memory) right before the issue. The issue has yet to be fully identified and fixed, but we're working on it. You can follow this thread in the Public Issue Tracker for updates.

Cheers,

Nick
Cloud Platform Community Support

On Thursday, December 29, 2016 at 9:11:50 AM UTC-5, Adrian Dybwad wrote:

This instance of MySQL has not responded for around two hours.

I cannot restore a backup to a new database either.

Please let me know what I should do?

purpleair-1293:us-central1:mysql-01

Thank you

Adrian

--
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/e015c760-8429-43c9-b053-c6d4fbb5d7a8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Communications Link Failure connecting to MySQL Cloud Instace

Hey Dave,

Could you share a code snippet showing how you build the connection, and if possible, any error text and stack traces which come when the issue manifests?

This seems like something that we can either solve here or will end up producing a Public Issue Tracker issue thread.

Cheers,

Nick
Cloud Platform Community Support

On Thursday, January 12, 2017 at 11:22:35 AM UTC-5, Dave Greenly wrote:

Hi there, 

We have a Cloud Instance of a MySQL Database which we use daily.  We have multiple compute engines that pull and push data to it, and on those compute engines are Java programs that connect to the database and read/write.

Pretty standard stuff.

On a semi-consistent basis, our Java programs have difficulty connecting to the database, and we receive a "Communications Link Failure" and our code cannot connect to the DB.  After some indeterminate amount of time, things "just start working again".

We actually put a check in our code for this error, and if we get it, we wait a few seconds, and try again, but even after 5 or so retry attempts, sometimes it is still not working.

We have chalked this up in the past to some type of network anomaly going on in the cloud.

We are using mysql-connector-java-5.1.38, and the MySQL instance on the cloud is version MySQL 5.5.

Has anyone else experienced this?

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/0801da4e-9271-46b6-8a52-4e6b568ab36a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Can not add "Authorized networks" for cloud sql instance

I see you currently have three Authorized networks and that the usage of your Cloud SQL instance is currently reduced (meaning not a lot of operations currently running). Were you able to add in your new network since the 13th? 

From the graphs I see that your instance usage peaks everyday, which could be the reason for the operation block you experienced. Performing database configuration changes during low traffic is most recommended. 

You can always attempt to log into your instance from one of the Authorized Networks, and run the 'show processlist' command to see what operations are running. You can then kill any processes that you think may be causing high resource usage (aka the operation block) and retry your configuration change. 

--
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/33803393-91b5-4006-9cbe-35d5dacc3c1e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Can not add "Authorized networks" for cloud sql instance

Hi all,

I want add more "Authorized networks" for my cloud sql instance but not complete with error message "Operation failed because another operation was already in progress"

My project id "id-vatgia-com"

Anyone help me with this problem

Tks,

--
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/ac3d6a65-be7b-4ae3-a576-07354993630d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] backups failing with message " An unknown error occurred."

We have several 1st gen cloud sql instances for customers. one of them is not auto backing up reliably any longer. The past two nights the backups have failed with the following error message:

Jan 13, 2017, 5:23:58 AM

Backup

An unknown error occurred.

Can you please look into this? project is parasql-app and the problem cloud sql instance is di-fresh-trends-56

Thanks.

--
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/0ca7a297-b547-41c1-96f2-f6559f294ff3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Communications Link Failure connecting to MySQL Cloud Instace

Hi there, 

We have a Cloud Instance of a MySQL Database which we use daily.  We have multiple compute engines that pull and push data to it, and on those compute engines are Java programs that connect to the database and read/write.

Pretty standard stuff.

On a semi-consistent basis, our Java programs have difficulty connecting to the database, and we receive a "Communications Link Failure" and our code cannot connect to the DB.  After some indeterminate amount of time, things "just start working again".

We actually put a check in our code for this error, and if we get it, we wait a few seconds, and try again, but even after 5 or so retry attempts, sometimes it is still not working.

We have chalked this up in the past to some type of network anomaly going on in the cloud.

We are using mysql-connector-java-5.1.38, and the MySQL instance on the cloud is version MySQL 5.5.

Has anyone else experienced this?

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/8aa2f640-125e-4a82-8e11-97d96e32e682%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: CloudSQL create replica slave problem (external replication)

Nicholas, I'm experiencing the same, I tried by using the API explorer and received the same answer.

Any other information you might be interested in?

cache-control:  private, max-age=0  content-encoding:  gzip  content-length:  153  content-type:  application/json; charset=UTF-8  date:  Thu, 12 Jan 2017 14:31:33 GMT  expires:  Thu, 12 Jan 2017 14:31:33 GMT  server:  GSE  vary:  Origin, X-Origin  

{
 "error": {
  "errors": [
   {
    "domain": "global",
    "reason": "notAuthorized",
    "message": "The client is not authorized to make this request."
   }
  ],
  "code": 403,
  "message": "The client is not authorized to make this request."
 }
}

On Thursday, December 15, 2016 at 5:56:00 PM UTC-3, Nicholas (Google Cloud Support) wrote:

Apologies for the lengthy radio silence.  I could not reproduce this issue on my end.  I got a 200 every time I tried, including when trying with some deliberate typos in the request body values.

Have you tried creating the replica from the API explorer for Instances: insert?  You can supply the JSON request body the way it's provided in the curl example and authenticate through the web OAuth flow.  If you're authorized, it should return a 200 OK with a operation resource.  You can inspect the progress of the operation providing its name to the Operations: get API.  This should show the errors encountered in replica creation or success.

On Friday, December 2, 2016 at 2:40:14 PM UTC-5, Nicholas (Google Cloud Support) wrote:

I am working on trying to reproduce this error but no luck yet.  I still have a few things to try.  I'll get back to you early next week.

On Tuesday, November 29, 2016 at 9:05:25 AM UTC-5, Lisei Andrei wrote:

I'm following this guide here for creating a cloudsql slave for an external mysql database.

https://cloud.google.com/sql/docs/replication/configure-external-master

I've managed to create an internal master but when i try to create the replica I have this error: 

I'm the project owner of the GCP project. 

{

 "error": {

  "errors": [

   {

    "domain": "global",

    "reason": "notAuthorized",

    "message": "The client is not authorized to make this request."

   }

  ],

  "code": 403,

  "message": "The client is not authorized to make this request."

 }

}

Thanks! 

--
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/4129174f-b0c7-49d7-a2d8-1df2e0345e47%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Mysql Flags replica on failover Cloud SQL instance

You can star the Public Issue Tracker to get email updates when the issue is resolved. All further progress will occur within the provided PIT.

--
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/65791005-c6b8-4f47-a5b2-d0ecd644b208%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: How to disable Read-Only in SQL replica?

Ah, I understand. Feel free to message back to this thread if you have any questions in setting up the external replicas. 

Cheers,

Nick
Cloud Platform Community Support

On Tuesday, January 10, 2017 at 6:03:11 AM UTC-5, Ann Su wrote:

Ah, I'm sorry, apparently my browser autocorrected "binlog" to "bingo". Running replicas on Compute Engine could do the trick, thanks.

Ann,

On Monday, January 9, 2017 at 11:00:36 PM UTC+1, paynen wrote:

Hey Ann,

It seems Bingo is an SQL server software? In that case you should run it on a Compute Engine instance. You could also run the replicas on Compute Engine instances. Read more in the documentation about Cloud SQL -external replicas and masters and let me know if you have any more questions.

Cheers,

Nick
Cloud Platform Community Support

On Monday, January 9, 2017 at 2:27:36 PM UTC-5, Ann Su wrote:

Hi Nick,

I've just filed a feature request.  

Is there a way to set up a custom slave using bingo from SQL master instance?

thanks,

Ann

On Monday, January 9, 2017 at 4:46:32 PM UTC+1, paynen wrote:

Hey Ann,

Thanks for your patience. As it turns out, altering this flag on replicas is not possible, and it's been an oversight to have left this flag alterable in the interface / API. We'll have this corrected. Since it appears you'd like to have this flag be alterable on the replica instances, you can file a Feature Request in the Public Issue Tracker for Cloud SQL detailing the feature you'd like to see, why you'd need to use it, etc. and we'll quickly get it logged and considered going forward.

Cheers,

Nick
Cloud Platform Community Support

On Saturday, January 7, 2017 at 5:45:21 AM UTC-5, Ann Su wrote:

Nick, any updates on this? 

Ann

On Saturday, December 31, 2016 at 2:48:39 AM UTC+1, Ann Su wrote:

Hi Nick,

many thanks for a quick turnaround! 

Ann

On Friday, December 30, 2016 at 10:14:50 PM UTC+1, paynen wrote:

Hey Ann Su,

I've replicated this and will be making sure it's seen by the relevant Cloud SQL specialists. I'll return to this thread to post a Public Issue Tracker link where you can follow the progress on this issue.

Cheers,

Nick
Cloud Platform Community Support 

On Wednesday, December 28, 2016 at 9:22:17 AM UTC-5, Ann Su wrote:

Google Console interface allows to set up "read-only" flag to OFF for a read replica. However, regardless of the flag's value, which according to: 

$ gcloud sql instances describe {{replica}}

is correctly set:

[...]

  - name: read_only

    value: 'off'

the global variable in mysql is still set to ON:

mysql> show variables like "read_only";

+---------------+-------+

| Variable_name | Value |

+---------------+-------+

| read_only     | ON    |

+---------------+-------+

Is this a bug? 

I'm aware of all related risks of writing to a replica and am willing to do that anyway. If I can't disable read_only mode for built-in replicas, what are my options? Can I manually configure replication using SQL instances in a way that such replica wouldn't get into read_only mode?

--
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/eee7700f-309a-42b9-8198-36ad7662de34%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: How to disable Read-Only in SQL replica?

Ah, I'm sorry, apparently my browser autocorrected "binlog" to "bingo". Running replicas on Compute Engine could do the trick, thanks.

Ann,

On Monday, January 9, 2017 at 11:00:36 PM UTC+1, paynen wrote:

Hey Ann,

It seems Bingo is an SQL server software? In that case you should run it on a Compute Engine instance. You could also run the replicas on Compute Engine instances. Read more in the documentation about Cloud SQL -external replicas and masters and let me know if you have any more questions.

Cheers,

Nick
Cloud Platform Community Support

On Monday, January 9, 2017 at 2:27:36 PM UTC-5, Ann Su wrote:

Hi Nick,

I've just filed a feature request.  

Is there a way to set up a custom slave using bingo from SQL master instance?

thanks,

Ann

On Monday, January 9, 2017 at 4:46:32 PM UTC+1, paynen wrote:

Hey Ann,

Thanks for your patience. As it turns out, altering this flag on replicas is not possible, and it's been an oversight to have left this flag alterable in the interface / API. We'll have this corrected. Since it appears you'd like to have this flag be alterable on the replica instances, you can file a Feature Request in the Public Issue Tracker for Cloud SQL detailing the feature you'd like to see, why you'd need to use it, etc. and we'll quickly get it logged and considered going forward.

Cheers,

Nick
Cloud Platform Community Support

On Saturday, January 7, 2017 at 5:45:21 AM UTC-5, Ann Su wrote:

Nick, any updates on this? 

Ann

On Saturday, December 31, 2016 at 2:48:39 AM UTC+1, Ann Su wrote:

Hi Nick,

many thanks for a quick turnaround! 

Ann

On Friday, December 30, 2016 at 10:14:50 PM UTC+1, paynen wrote:

Hey Ann Su,

I've replicated this and will be making sure it's seen by the relevant Cloud SQL specialists. I'll return to this thread to post a Public Issue Tracker link where you can follow the progress on this issue.

Cheers,

Nick
Cloud Platform Community Support 

On Wednesday, December 28, 2016 at 9:22:17 AM UTC-5, Ann Su wrote:

Google Console interface allows to set up "read-only" flag to OFF for a read replica. However, regardless of the flag's value, which according to: 

$ gcloud sql instances describe {{replica}}

is correctly set:

[...]

  - name: read_only

    value: 'off'

the global variable in mysql is still set to ON:

mysql> show variables like "read_only";

+---------------+-------+

| Variable_name | Value |

+---------------+-------+

| read_only     | ON    |

+---------------+-------+

Is this a bug? 

I'm aware of all related risks of writing to a replica and am willing to do that anyway. If I can't disable read_only mode for built-in replicas, what are my options? Can I manually configure replication using SQL instances in a way that such replica wouldn't get into read_only mode?

--
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/459f5646-6af7-434e-863c-af2a984dfce4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: How to disable Read-Only in SQL replica?

Hey Ann,

It seems Bingo is an SQL server software? In that case you should run it on a Compute Engine instance. You could also run the replicas on Compute Engine instances. Read more in the documentation about Cloud SQL -external replicas and masters and let me know if you have any more questions.

Cheers,

Nick
Cloud Platform Community Support

On Monday, January 9, 2017 at 2:27:36 PM UTC-5, Ann Su wrote:

Hi Nick,

I've just filed a feature request.  

Is there a way to set up a custom slave using bingo from SQL master instance?

thanks,

Ann

On Monday, January 9, 2017 at 4:46:32 PM UTC+1, paynen wrote:

Hey Ann,

Thanks for your patience. As it turns out, altering this flag on replicas is not possible, and it's been an oversight to have left this flag alterable in the interface / API. We'll have this corrected. Since it appears you'd like to have this flag be alterable on the replica instances, you can file a Feature Request in the Public Issue Tracker for Cloud SQL detailing the feature you'd like to see, why you'd need to use it, etc. and we'll quickly get it logged and considered going forward.

Cheers,

Nick
Cloud Platform Community Support

On Saturday, January 7, 2017 at 5:45:21 AM UTC-5, Ann Su wrote:

Nick, any updates on this? 

Ann

On Saturday, December 31, 2016 at 2:48:39 AM UTC+1, Ann Su wrote:

Hi Nick,

many thanks for a quick turnaround! 

Ann

On Friday, December 30, 2016 at 10:14:50 PM UTC+1, paynen wrote:

Hey Ann Su,

I've replicated this and will be making sure it's seen by the relevant Cloud SQL specialists. I'll return to this thread to post a Public Issue Tracker link where you can follow the progress on this issue.

Cheers,

Nick
Cloud Platform Community Support 

On Wednesday, December 28, 2016 at 9:22:17 AM UTC-5, Ann Su wrote:

Google Console interface allows to set up "read-only" flag to OFF for a read replica. However, regardless of the flag's value, which according to: 

$ gcloud sql instances describe {{replica}}

is correctly set:

[...]

  - name: read_only

    value: 'off'

the global variable in mysql is still set to ON:

mysql> show variables like "read_only";

+---------------+-------+

| Variable_name | Value |

+---------------+-------+

| read_only     | ON    |

+---------------+-------+

Is this a bug? 

I'm aware of all related risks of writing to a replica and am willing to do that anyway. If I can't disable read_only mode for built-in replicas, what are my options? Can I manually configure replication using SQL instances in a way that such replica wouldn't get into read_only mode?

--
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/255b13af-401b-4039-ab90-7ca5b9419b5c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: gtid_mode = off?

'gtid_mode' is used when binary logging is enabled to prevent data loss during replica creation and failover. It is recommended you migrate your queries to work with GTID as this is now a default setting on all Cloud SQL instances. 

Note that super privileges are disabled for Cloud SQL instances. If you require super level access, you can host a custom SQL instance on Compute Engine.

--
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/a6d6339e-ae6c-4964-bf08-9805d93795ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: CloudSQL instance stuck on restart operation

Hi,

For this type of issue, submitting a Bug on the Google Cloud SQL public issue tracker [1] as you did, is the most appropriate method for seeking help from the Google Cloud support team. Now concerning your issue, it is not common and as you have already submitted a bug [2] on the referenced PIT, you can follow its resolution there.

Concerning a faster response time from the Google Cloud Platform technical support, you may want to consider the different available options of Premium Support [3] depending on your needs. Note that as part of the features available for each support packages, different targets are set for the initial response time for critical issues.

For anyone reading this post, please refer to the opened PIT thread [2] if experiencing a similar issue.

Regards,

[1] https://code.google.com/p/googlecloudsql/

[2] https://code.google.com/p/googlecloudsql/issues/detail?id=206

[3] https://cloud.google.com/support/

--
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/5d84fe03-dfae-41a3-8ed0-69aa5c7f00a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.