[google-cloud-sql-discuss] cloud sql failover instance connecting to wrong master instance

I have master-instance-a (ip: 1.1.1.1), and i clone it to another instance call master-instance-b (ip: 2.2.2.2)

When i tried to add a failover for master-instance-b, and the failover instance failed to start, i tried to connect to the failover instance from gcloud, and from show slave status\G, surprisingly the failover instance master host is set to master-instance-a ip!

Then i tried to add a read replica for master-instance-b, and after loading for a while, the read replica shows failed to create, and the error is An unknown error occurred.

Does anyone face this same issue? How should i rectify 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/186b9297-b922-4409-b76a-5d11919e9ae1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] “cat urls.txt | gsutil -m cp -I gs://target-bucket-name/” consistently hangs after transferring ~10,000 files

https://stackoverflow.com/questions/47424273/cat-urls-txt-gsutil-m-cp-i-gs-target-bucket-name-consistently-hangs-aft

--
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/3669c269-cd5f-4154-b0d8-ee4a09776d4c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-cloud-sql-discuss] Re: Error creating failover replica on MySQL 2G

We can't even stop or delete the instance, so we're still being charged for the unavailable server.

On Wed, Nov 29, 2017 at 11:19 PM, Geoffrey Arnold <geoffrey.arnold@gmail.com> wrote:

Done: https://issuetracker.google.com/issues/69937324

On Wed, Nov 29, 2017 at 6:39 PM, 'Carlos (Cloud Platform Support)' via Google Cloud SQL discuss <google-cloud-sql-discuss@googlegroups.com> wrote:

To troubleshoot this error, we might need to have a look into your projects logs. Please open an report on the issue tracker.

--
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/e66b8e9b-d635-4c1a-953b-70d918c6006b%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/CAF388611S%3DvG8kiDNToeHvNpnFuWW01x2RhxTp29o-gfRKVdXA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: App Engine to Cloud SQL connectivity problem

There was an issue with Google Cloud SQL high latency that has been resolved for all affected users as of Thursday, 2017-11-30 02:46 US/Pacific.

We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize future recurrence.

For any kind of billing-related issues you should contact the free Billing and Payments Support.

On Thursday, November 30, 2017 at 9:11:53 AM UTC-5, Andrew Karpushin wrote:

It's still an issue for me, and today it's worse than before. About 4-5 days ago i saw no errors, but starting from today i see hundreds and hundreds of them. Stackdriver reports from time to time that my site is down for few minutes. There is also DeadlineExceededError while app tries to connect to Cloud SQL (seen in the logs). Moreover, as a side effect, because the website doesn't respond in the appropriate time, App Engine creates 19 additional instances and I've got billed to their CPU-hours. My appid is "armorinspector" if that helps.

Am Montag, 13. November 2017 22:26:09 UTC+3 schrieb Yannick (Cloud Platform Support):

Hello Andrew, engineering is aware of this issue and a fix should soon be rolled out to address it.

On Saturday, November 11, 2017 at 12:05:38 PM UTC-5, Andrew Karpushin wrote:

In the past couple of days I started to see hundreds errors in the log like this one:

"Lost connection to MySQL server at 'reading initial communication packet', system error: 38"

Previously it was maybe one or two such errors per day, but now they appear every few minutes. Nothing was changed on my side and I believe something is wrong with Google SQL. Errors in the log started to appear at 2017-11-08. I can't reproduce it myself and most of the requests are handled properly. I have about 180k requests per day and several hundreds of them are now failing due to this error. Anyone else experience this?

--
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/43f1a9f8-8b35-4668-94f9-8cd183f4e477%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Cloud SQL instance stuck in "another operation was already in progress"

Hello, I have exactly the same issue with MySQL 5.7 instance with failover replica on three different projects when trying to delete them - I need these instances deleted but can't do it because of the error.

Is there a known solution yet?

Derek

On Tuesday, 15 August 2017 01:09:10 UTC+1, Kenworth (Google Cloud Platform) wrote:

Thank you for filing a bug on Public Issue Tracker. Your issue is still currently investigated so I do not have any input yet on how it will be prevented. And since your case is already handled by my colleague, I would recommend redirecting all future  discussions to that issue tracker. Please feel free to contribute on this thread once the investigation is finished. 

--
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/3050da6e-376b-4435-b3df-9ac372217c04%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: App Engine to Cloud SQL connectivity problem

It's still an issue for me, and today it's worse than before. About 4-5 days ago i saw no errors, but starting from today i see hundreds and hundreds of them. Stackdriver reports from time to time that my site is down for few minutes. There is also DeadlineExceededError while app tries to connect to Cloud SQL (seen in the logs). Moreover, as a side effect, because the website doesn't respond in the appropriate time, App Engine creates 19 additional instances and I've got billed to their CPU-hours. My appid is "armorinspector" if that helps.

Am Montag, 13. November 2017 22:26:09 UTC+3 schrieb Yannick (Cloud Platform Support):

Hello Andrew, engineering is aware of this issue and a fix should soon be rolled out to address it.

On Saturday, November 11, 2017 at 12:05:38 PM UTC-5, Andrew Karpushin wrote:

In the past couple of days I started to see hundreds errors in the log like this one:

"Lost connection to MySQL server at 'reading initial communication packet', system error: 38"

Previously it was maybe one or two such errors per day, but now they appear every few minutes. Nothing was changed on my side and I believe something is wrong with Google SQL. Errors in the log started to appear at 2017-11-08. I can't reproduce it myself and most of the requests are handled properly. I have about 180k requests per day and several hundreds of them are now failing due to this error. Anyone else experience this?

--
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/ba42cff7-4e28-4ffe-b674-90afd5709d2e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-cloud-sql-discuss] Re: Error creating failover replica on MySQL 2G

Done: https://issuetracker.google.com/issues/69937324

On Wed, Nov 29, 2017 at 6:39 PM, 'Carlos (Cloud Platform Support)' via Google Cloud SQL discuss <google-cloud-sql-discuss@googlegroups.com> wrote:

To troubleshoot this error, we might need to have a look into your projects logs. Please open an report on the issue tracker.

--
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/e66b8e9b-d635-4c1a-953b-70d918c6006b%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/CAF38862GSb%3Dy6HBQG66H_S3MbBzns%3DA-pxR4NedtLERvMLxEQg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Error creating failover replica on MySQL 2G

To troubleshoot this error, we might need to have a look into your projects logs. Please open an report on the issue tracker.

--
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/e66b8e9b-d635-4c1a-953b-70d918c6006b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: App Engine to Cloud SQL connectivity problem

saw a lot of these today too (11/29/17)

On Monday, November 13, 2017 at 2:26:09 PM UTC-5, Yannick (Cloud Platform Support) wrote:

Hello Andrew, engineering is aware of this issue and a fix should soon be rolled out to address it.

On Saturday, November 11, 2017 at 12:05:38 PM UTC-5, Andrew Karpushin wrote:

In the past couple of days I started to see hundreds errors in the log like this one:

"Lost connection to MySQL server at 'reading initial communication packet', system error: 38"

Previously it was maybe one or two such errors per day, but now they appear every few minutes. Nothing was changed on my side and I believe something is wrong with Google SQL. Errors in the log started to appear at 2017-11-08. I can't reproduce it myself and most of the requests are handled properly. I have about 180k requests per day and several hundreds of them are now failing due to this error. Anyone else experience this?

--
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/15464f3a-0598-4da1-8b9b-a1ee1daa7db2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Error creating failover replica on MySQL 2G

Hello,

We attempted to create a failover replica of a MySQL 2G instance and the replica is marked "unavailable" in the Cloud SQL console. The logs show the following error:

Slave I/O: Got fatal error 1236 from master when reading data from binary log: 'Found old binary log without GTIDs while looking for the oldest binary log that contains any GTID that is not in the given gtid set', Error_code: 1236

Any help would be greatly appreciated,

Geoff. 

--
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/8d6b397c-89b0-4210-8115-d03b776f5a79%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Cloud Sql

I believe most of your questions are answered on [1] and [2]. The event is triggered by an outage in the zone and existing connections are closed. Nevertheless your application can reconnect in the new zone using the same IP. 

This discussion provides additional insight (check Jay Zhu's comments) on how the failover is experienced in your side, which is basically seeing the master being moved to a healthy zone. 

--
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/b4091b1a-8b27-4491-afca-5df5aa0757ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Is it possible to change workmem for postgres?

Hello George,

My apologies if I misspoke about ALTER SYSTEM command. It does require superuser access. I performed the test in my lab system and it is possible to set work_mem  "per-session" without superuser privileges, Below is the output :

postgres=> set work_mem = '5MB';

SET

postgres=> show work_mem;

work_mem

----------

5MB

(1 row)

As you mentioned, since Cloud SQL is a managed instance it is not possible to perform this setup at the system level. Please note changing the "work_mem" might drive the system into an undesirable state.

--
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/2b1e3302-c3f6-4ed5-98e3-f4c4dc5fe580%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Cloud Sql

What is Fail over in Cloud SQL? and What happens to the SQL server during fail-over? and After fail-over of master how the master recovers from failover

--
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/5e76716b-f8ce-4264-8f9c-330dc0a036f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Is it possible to change workmem for postgres?

Do you mean the following command?

ALTER SYSTEM SET work_mem;

Because ALTER SYSTEM requires superuser privileges. Which is not available in Cloud SQL for Postgres.

On Friday, November 24, 2017 at 12:58:01 AM UTC+4, Karthick (Cloud Platform Support) wrote:

You can  still edit by Alter System as per this document

--
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/86b8b5ba-4db7-49aa-82fb-59c1980ea421%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Is it possible to change workmem for postgres?

Hello Sharoon,

Please note that Cloud SQL for PostgreSQL is still in Beta. And as you are aware already that currently the work_mem parameter is not in the list of settable flags . You can  still edit by Alter System as per this document, but we do not guarantee as it could affect the behavior of the instance. And the parameter change is per session basis but not at system level. You can also visit this document for further understanding.   

--
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/af8874d9-3bfd-4730-a16f-5f4690a8b636%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: PostgreSQL, Postgis, ST_GeomFromGeoJSON and JSON-C

Just to echo too. We are trying migrate to Cloud SQL but we need the ST_GeomFromGeoJSON().

Thank you!

On Friday, May 19, 2017 at 2:33:20 PM UTC-3, Samuel ROZE wrote:

I've being trying to use Google Cloud SQL PostgreSQL with Postgis. After experiencing the "missing uuid-ossp extension issue", I've been trying to use the "ST_GeomFromGeoJSON" function:

```

INSERT INTO "locations" ("id","datetime","travelIdentifier","point","accuracy","altitude","altitudeAccuracy","heading","speed","segment") VALUES (DEFAULT,'2017-05-19 17:17:33.022 +00:00','93d4bc6e-ea3e-46db-95e4-4f5ee450070a',ST_GeomFromGeoJSON('{"type":"Point","coordinates":[-122.31259857,37.49677685]}'),5,0,-1,297.42,32.73,7) RETURNING *;

ERROR:  You need JSON-C for ST_GeomFromGeoJSON

```

Based on Postgis' documentation, JSON-C is a required dependency and I understood from various Search queries that it is why I would have this issue. Any idea how, if possible, can we get Postgres with JSON-C ?

Thank you very much,

Samuel.

--
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/ee325833-18de-4a59-978a-6c73d2a15a85%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Reduce migration downtime

Hello Markus, 

You are right: replicas are always the same generation (First Generation or Second Generation) as the master instance, as detailed on the "Requirements and Tips for Configuring Replication" documentation page.

The need to dump first is justified by the time-related differences in database content, as one needs to import data for a certain moment in time. More information on the migration process to second-generation can be gathered from the "Migrating an Instance to Second Generation" page.  

--
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/2b436e5e-c550-422f-9f71-5c06e3203ca1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Is it possible to change workmem for postgres?

I see that it's not one of the supported flags and the defaults are not optimized to the memory on the spinned up database 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/b77fe306-9002-4106-8ade-3c22fdef7568%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Reduce migration downtime

Hello group!

I've been doing some research and seems it's absolutely impossible to migrate to 2nd generation without a dump, nor to setup 2nd generation MySQLs as slave of external masters or 1st Gen master...

Seems like quite a high barrier for migration;  Is there some hack/workaround/undocumented voodoo spell we can cast to avoid the dump and reload? Without being able to setup replication that means massive downtimes, and in all honesty: is pretty surprising to find a hopefully-more-advanced 2nd generation product which does not provide any low-downtime migration path (even when it could imply more machines or more complexity... *some* way would be great).

I hope am missing something and that in fact setting up 2nd generation as a slave of 1st generation would be possible?

Thanks in advance,

Markus

--
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/96e586c9-f5c3-46d9-8e9e-33d1e69241e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: PostgreSQL, Postgis, ST_GeomFromGeoJSON and JSON-C

Just to echo, just wondering is there any update on this? 

On Friday, 19 May 2017 18:33:20 UTC+1, Samuel ROZE wrote:

I've being trying to use Google Cloud SQL PostgreSQL with Postgis. After experiencing the "missing uuid-ossp extension issue", I've been trying to use the "ST_GeomFromGeoJSON" function:

```

INSERT INTO "locations" ("id","datetime","travelIdentifier","point","accuracy","altitude","altitudeAccuracy","heading","speed","segment") VALUES (DEFAULT,'2017-05-19 17:17:33.022 +00:00','93d4bc6e-ea3e-46db-95e4-4f5ee450070a',ST_GeomFromGeoJSON('{"type":"Point","coordinates":[-122.31259857,37.49677685]}'),5,0,-1,297.42,32.73,7) RETURNING *;

ERROR:  You need JSON-C for ST_GeomFromGeoJSON

```

Based on Postgis' documentation, JSON-C is a required dependency and I understood from various Search queries that it is why I would have this issue. Any idea how, if possible, can we get Postgres with JSON-C ?

Thank you very much,

Samuel.

--
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/8f0cd824-85a3-4a84-852c-9c331b6cfdc7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Cloud SQL backup failing with "Unknown error"

Hi Gustavo, a thread like this is off-topic for Google Groups. As it may potentially be a defect on the platform and most likely lead to a specific situation which may require some exchange of project information to reproduce the behavior you described, I highly encourage you to submit a defect report as described in this article so that proper attention and weight will be given to it. We monitor that issue tracker closely.

We look forward to this issue report.

--
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/0ac3ecc4-45a9-40e7-9d36-477ccddfeecf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Cloud SQL backup failing with "Unknown error"

The instance seems to be stuck with failing backup operations. The last successful backup was made on November 12 and since then the instance has been stuck trying (and failing) to create a new backup.

This is a db-f1-micro instance used for development, it only has 3 out of 20 GB used (meaning there is more than enough free space) and I can connect to and query the instance the just fine.

It is a second gen MySQL instance with no replication or HA. I could make a dump of the data and recreate everything on another instance, but I'm not even sure I would be able to delete this instance while it is stuck on this state.

Anyone has any idea on how to "unstuck" it?

Regards,

Gustavo Rocha.

Esta mensagem e seus eventuais anexos podem conter dados confidenciais ou privilegiados. Se você a recebeu por engano ou não é um de seus destinatários, elimine imediatamente a mensagem e seus eventuais anexos ou cópias e comunique o remetente. É proibida a divulgação, distribuição, retenção ou utilização através de qualquer meio das informações contidas nesta mensagem. Agradecemos sua colaboração.

This message may contain confidential and/or privileged information. If you are not the addressee or if you are not authorized to receive this message on behalf of the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message by mistake, please inform the sender immediately by replying this e-mail and delete this message. Thank you for your cooperation.

--
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/79d8aeb8-d72e-434c-9900-d610853fa25d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Cannot connect to Google Cloud SQL (MySQL) - No settings changed

Hi Allan,

I will need some sensitive information from your side. Please provide me following detail in a private message.

1. Please let me know the output of gcloud sql instance describe command as mentioned in my initial post.

2. Please give me your project number and instance name that is having issue.

3. When you observed this issue first time? Did you install some application that need frequent DB access?

On Monday, November 20, 2017 at 9:05:17 AM UTC-5, Allan Porras wrote:

I have the same issue. From localhost using Client Proxy works fine.  Any ideas?

On Friday, 17 November 2017 04:49:44 UTC-6, Francis Austria wrote:

Hi Dinesh,

I reported this to the Support team and it is already fixed now.


On Thursday, November 16, 2017 at 4:41:17 AM UTC+8, Dinesh (Google Platform Support) wrote:

Hello Francis,

Current we do not have any reported issue for cloud SQL and are able to extract user and database informations from SQL instance.

Can you please execute gcloud sql instance describe command [1] and verify instance state?

Instance could be in following six state:-

RUNNABLE: The instance is running, or is ready to run when accessed.

SUSPENDED: The instance is not available, for example due to problems with billing.

PENDING_CREATE: The instance is being created.

MAINTENANCE: The instance is down for maintenance.

FAILED: The instance creation failed.

UNKNOWN_STATE: The state of the instance is unknown.

You can send me o/p of this command in a private message.

Meanwhile, you can restart your instance to see if this behavior changed. 

[1]: https://cloud.google.com/sdk/gcloud/reference/sql/instances/describe

On Wednesday, November 15, 2017 at 9:30:03 AM UTC-5, Francis Austria wrote:

Hi,

Has anyone already experienced same issue as ours?

No setting has been changed but suddenly everything in the Google Cloud SQL was not working.


It says the instance is "runnable".




Cannot retrieve and create new User Accounts


Also with the databases


No detailed info about the errors are shown in the logs.



Anyone who experienced the same issue and solved it?

Hoping for a swift response. 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/b8c011d2-8ca3-41c3-9e0f-22384133e970%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: SQL stuck "operation failed because another operation was already in progress"

I can see you have raised a PIT bug for this same issue and engineering team is already working on that case. 

I'll close this issue as a duplicate case. You can follow and update the other case for further assistance.

On Monday, November 20, 2017 at 9:05:11 AM UTC-5, WebByte Media wrote:

no, you cant. Every command throws back. ERROR: (gcloud.sql.instances.patch) HTTPError 403: Operation failed because another operation was already in progress.. I submitted a bug report and your back-end team is supposed to be reviewing, over a week still no solution. This is horrible service. 

On Monday, November 13, 2017 at 2:21:37 PM UTC-5, Dinesh (Google Platform Support) wrote:

Hello

As I understand here, you are trying to stop master DB instance? Please note that you must delete the master DB's replicas first in order to stop master DB.

Moreover, If you are trying to add a user, create database etc. please note that such operations are not allowed from a read replica (failover instance). You can perform such operations from master DB. Though you can add authorisation IP from replica instance independently.

Please send me the text of message along with screenshots of failed operations as I believe you are trying to perform such operations from cloud console?

You can add a user, add authorisation IP from gcloud command as well.

On Monday, November 13, 2017 at 8:44:26 AM UTC-5, WebByte Media wrote:

Can't add users, DB, authorization IPs or delete backup instance to stop primary...not too sure what to do 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/ff908286-3804-407b-9cfa-984208964828%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: SQL stuck "operation failed because another operation was already in progress"

no, you cant. Every command throws back. ERROR: (gcloud.sql.instances.patch) HTTPError 403: Operation failed because another operation was already in progress.. I submitted a bug report and your back-end team is supposed to be reviewing, over a week still no solution. This is horrible service. 

On Monday, November 13, 2017 at 2:21:37 PM UTC-5, Dinesh (Google Platform Support) wrote:

Hello

As I understand here, you are trying to stop master DB instance? Please note that you must delete the master DB's replicas first in order to stop master DB.

Moreover, If you are trying to add a user, create database etc. please note that such operations are not allowed from a read replica (failover instance). You can perform such operations from master DB. Though you can add authorisation IP from replica instance independently.

Please send me the text of message along with screenshots of failed operations as I believe you are trying to perform such operations from cloud console?

You can add a user, add authorisation IP from gcloud command as well.

On Monday, November 13, 2017 at 8:44:26 AM UTC-5, WebByte Media wrote:

Can't add users, DB, authorization IPs or delete backup instance to stop primary...not too sure what to do 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/b0bb19dc-593f-4a24-9e74-46f1d16adcd2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Cannot delete MySQL instance (failover), stuck with "Operation failed because another operation was already in progress"

Hi Titus, a thread like this is off-topic for Google Groups. As it may potentially be a defect on the platform and most likely lead to a specific situation which may require some exchange of project information to reproduce the behavior you described, I highly encourage you to submit a defect report as described in this article so that proper attention and weight will be given to it (include the instance details). We monitor that issue tracker closely.

We look forward to this issue report.

--
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/a2baa61e-c4d2-47ab-ae30-eb3f2a99c57a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Cannot connect to Google Cloud SQL (MySQL) - No settings changed

I have the same issue. From localhost using Client Proxy works fine.  Any ideas?

On Friday, 17 November 2017 04:49:44 UTC-6, Francis Austria wrote:

Hi Dinesh,

I reported this to the Support team and it is already fixed now.


On Thursday, November 16, 2017 at 4:41:17 AM UTC+8, Dinesh (Google Platform Support) wrote:

Hello Francis,

Current we do not have any reported issue for cloud SQL and are able to extract user and database informations from SQL instance.

Can you please execute gcloud sql instance describe command [1] and verify instance state?

Instance could be in following six state:-

RUNNABLE: The instance is running, or is ready to run when accessed.

SUSPENDED: The instance is not available, for example due to problems with billing.

PENDING_CREATE: The instance is being created.

MAINTENANCE: The instance is down for maintenance.

FAILED: The instance creation failed.

UNKNOWN_STATE: The state of the instance is unknown.

You can send me o/p of this command in a private message.

Meanwhile, you can restart your instance to see if this behavior changed. 

[1]: https://cloud.google.com/sdk/gcloud/reference/sql/instances/describe

On Wednesday, November 15, 2017 at 9:30:03 AM UTC-5, Francis Austria wrote:

Hi,

Has anyone already experienced same issue as ours?

No setting has been changed but suddenly everything in the Google Cloud SQL was not working.


It says the instance is "runnable".




Cannot retrieve and create new User Accounts


Also with the databases


No detailed info about the errors are shown in the logs.



Anyone who experienced the same issue and solved it?

Hoping for a swift response. 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/ea8d2f64-dd12-4917-bb81-52e8d03ffb2b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Cannot delete MySQL instance (failover), stuck with "Operation failed because another operation was already in progress"

Hello,

I'm having issues deleting a mySQL failover instance.

I created a new instance + replica. A few minustes later I wanted to drop both instances but I keep getting that same message "Operation failed because another operation was already in progress"

even when I restart the replica.

I also tried to remove the replica from the command line 'gcloud sql'.

It's been 24 hours now and I keep getting the same message.

Not too sure what to do here... I'm being billed for something I don't want to use anymore.

Thanks for the help.

--
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/1afe9db9-4cd6-455a-a94a-cb33cb2a149e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Cannot connect to Google Cloud SQL (MySQL) - No settings changed

Hi Dinesh,

I reported this to the Support team and it is already fixed now.


On Thursday, November 16, 2017 at 4:41:17 AM UTC+8, Dinesh (Google Platform Support) wrote:

Hello Francis,

Current we do not have any reported issue for cloud SQL and are able to extract user and database informations from SQL instance.

Can you please execute gcloud sql instance describe command [1] and verify instance state?

Instance could be in following six state:-

RUNNABLE: The instance is running, or is ready to run when accessed.

SUSPENDED: The instance is not available, for example due to problems with billing.

PENDING_CREATE: The instance is being created.

MAINTENANCE: The instance is down for maintenance.

FAILED: The instance creation failed.

UNKNOWN_STATE: The state of the instance is unknown.

You can send me o/p of this command in a private message.

Meanwhile, you can restart your instance to see if this behavior changed. 

[1]: https://cloud.google.com/sdk/gcloud/reference/sql/instances/describe

On Wednesday, November 15, 2017 at 9:30:03 AM UTC-5, Francis Austria wrote:

Hi,

Has anyone already experienced same issue as ours?

No setting has been changed but suddenly everything in the Google Cloud SQL was not working.


It says the instance is "runnable".




Cannot retrieve and create new User Accounts


Also with the databases


No detailed info about the errors are shown in the logs.



Anyone who experienced the same issue and solved it?

Hoping for a swift response. 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/1fe01419-facc-4f21-8b28-56beea203f18%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Could not complete the operation message when trying to create a new mySQL First Gen database

You are following the right procedure, I obtained the same error while trying to deploy in europe-west. I was able to create the instance in us-central. 

As you mention the error is very generic but in this case is related to a stock out on that particular region. Our teams are currently working on the system so that it can return a meaningful message.  At the moment I can only suggest to try in a different region. 

--
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/97b35d2c-f1ce-487f-b111-bf36a6dc2415%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Could not complete the operation message when trying to create a new mySQL First Gen database

I'm trying to create a new mySQL database on the Web interface and I keep getting the message "Could not complete the operation"

• instance ID: promeva-apf-sql
  
• Region: europe-west
• Tier: D1 512 MB RAM
• Database version MySQL 5.6
• Billing plan D1: Per use
• Preferred location: Follow App Engine app
• Automate backups 05:00 - 09:00
• Activation policy: Always
• Fire system replication: Asynchronous
• IPv4 addrss: Yes
• No Networks defined (yet)
• Only App Engine app as Authorised app

Is there any prerequisite to doing this? I have a working system so I'm following the setup documentation I've made. But since the error is so generic, I'm at a loss as to how to proceed.

Any thoughts?

--
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/6c4eb561-c1dd-49a2-a6c6-0dcc7be59435%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Cannot connect to Google Cloud SQL (MySQL) - No settings changed

Hello Francis,

Current we do not have any reported issue for cloud SQL and are able to extract user and database informations from SQL instance.

Can you please execute gcloud sql instance describe command [1] and verify instance state?

Instance could be in following six state:-

RUNNABLE: The instance is running, or is ready to run when accessed.

SUSPENDED: The instance is not available, for example due to problems with billing.

PENDING_CREATE: The instance is being created.

MAINTENANCE: The instance is down for maintenance.

FAILED: The instance creation failed.

UNKNOWN_STATE: The state of the instance is unknown.

You can send me o/p of this command in a private message.

Meanwhile, you can restart your instance to see if this behavior changed. 

[1]: https://cloud.google.com/sdk/gcloud/reference/sql/instances/describe

On Wednesday, November 15, 2017 at 9:30:03 AM UTC-5, Francis Austria wrote:

Hi,

Has anyone already experienced same issue as ours?

No setting has been changed but suddenly everything in the Google Cloud SQL was not working.


It says the instance is "runnable".




Cannot retrieve and create new User Accounts


Also with the databases


No detailed info about the errors are shown in the logs.



Anyone who experienced the same issue and solved it?

Hoping for a swift response. 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/e7d8200e-5754-4326-ad69-31c1149ea7a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.