Monday, December 30, 2019

[google-cloud-sql-discuss] Re: Is there a way to get the details of a Google Cloud SQL failover replica instance?

Prior to November 2019, Cloud SQL for MySQL failover instances were configured manually and details for those instances were accessible. Since then, enabling the High Availability feature now enables Regional Persistent Disks which synchronously replicate data at the block-level between two zones in a region. As such, the failover replica is not visible and metrics cannot be accessed for it. This is also the configuration for PosgreSQL instances.

It is possible to set an instance to High Availability using the legacy configuration by following this method [1], which will render the failover instance visible but doesn't take advantage of the benefits of the Regional Persistent Disks (virtually non-existent replication lag among others). Please note that this legacy configuration will only be available until April 2020, as mentioned here [2].

[1] https://cloud.google.com/sql/docs/mysql/configure-ha#ha-existing-legacy
[2] https://cloud.google.com/sql/docs/mysql/high-availability#legacy_mysql_high_availability_option

On Monday, December 30, 2019 at 10:58:57 AM UTC-5, Gerome Ren wrote:

I know I can use gcloud sql instances describe or the Cloud SQL REST API to get the details of a Cloud SQL instance, and that I can also get the secondary zone after failover is done (e.g. gceZone).

After enabling the High Availability (regional) feature for a Cloud SQL instance, is there a way to get the details of Cloud SQL failover replica instance?


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/d4f6260e-bdb8-4c4e-ad4a-9d352b3163a4%40googlegroups.com.

[google-cloud-sql-discuss] Is there a way to get the details of a Google Cloud SQL failover replica instance?

I know I can use gcloud sql instances describe or the Cloud SQL REST API to get the details of a Cloud SQL instance, and that I can also get the secondary zone after failover is done (e.g. gceZone).

After enabling the High Availability (regional) feature for a Cloud SQL instance, is there a way to get the details of Cloud SQL failover replica instance?


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/b5750e4d-b17b-4daa-bfb7-d67b8bbb92c1%40googlegroups.com.

Sunday, December 29, 2019

[google-cloud-sql-discuss] Re: Certificate issue with cloud sql instance

Ok, thanks for the clarification. I went ahead and posted my issue to the Issue Tracker board:
https://issuetracker.google.com/issues/146941059

On Friday, December 27, 2019 at 4:35:39 PM UTC-7, Elliott (Google Cloud Platform Support) wrote:
Hello Oliver,

Please note that Google Groups are reserved for general Google Cloud Platform and product discussions and not for reporting issues, which is why I suggest moving the troubleshooting to Issue Tracker, where issues can be turned private in case we need to gather any project specific details.

--
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/46ba336d-c2be-4864-82cc-06fb2da20665%40googlegroups.com.

Friday, December 27, 2019

[google-cloud-sql-discuss] Re: Certificate issue with cloud sql instance

Hello Oliver,

Please note that Google Groups are reserved for general Google Cloud Platform and product discussions and not for reporting issues, which is why I suggest moving the troubleshooting to Issue Tracker, where issues can be turned private in case we need to gather any project specific details.

--
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/033d6478-31ea-49ad-8095-3a28cc65a4db%40googlegroups.com.

Thursday, December 26, 2019

[google-cloud-sql-discuss] Certificate issue with cloud sql instance

I have a couple of cloud sql instances where I receive the following error message when I attempt to connect to them using the cloud sql proxy and a service account: 
'2019/12/20 13:08:57 couldn't connect to "bitcoin-core-test:us-central1:prod5": x509: certificate has expired or is not yet valid'

I have another sql instance under the same project that I can access without issue. It's my understanding that the behavior should be consistent across all instances in a project. If this understanding is correct, then this seems like there is a potential bug. I also tried resetting the ssl configuration for those instances that are failing, but that had no effect.


--
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/cce94c91-8daa-459f-8406-8b07bdd4e3c6%40googlegroups.com.

[google-cloud-sql-discuss] Re: Postgres Vacuum problem

The NULL values from the select * from pg_stat_progress_vacuum is a known issue[1] which is why the are no visible results as to the progress of the vacuum. Please note that the process may be able to stopped with the function pg_cancel_backend(pid int) which cancels a backend's current query. You can execute this against another backend that has exactly the same role as the user calling the function. In all other cases, you must be a superuser which is not supported by Cloud SQL[3]. 

It seems you can truncate the table which is probably faster then vacuuming to reclaim that disk space though it is unclear if you can do it while vacuuming on the table is occurring. 

Finally if the above options do not work I suggest opening a private issue tracker[5] and provide your project id and the instance name of the effected instance but it is generally advised you try to either cancel/restart the vacuum yourself first. 

--
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/ac5bc040-a846-4b3a-8683-d03fdbb8dd40%40googlegroups.com.

Wednesday, December 25, 2019

[google-cloud-sql-discuss] Postgres Vacuum problem

Hi, 

I can't work with the database other than the "select" statement. When I update or edit the table or column data it reports an error like this:

ERROR: database is not accepting commands to avoid wraparound data loss in database "xxx"
HINT
: Stop the postmaster and vacuum that database in single-user mode.
You might also need to commit or roll back old prepared transactions.

Table information:
Screenshot from 2019-12-25 23-05-50.png















It has been running for over 10 hours but does not see anything happening:
Screenshot from 2019-12-25 23-22-55.pngScreenshot from 2019-12-25 23-25-12.png


How do I know when the "VACUUM table" statement completes? Can I truncate that table?

Thanks a lot
Hung

--
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/38d2d1b6-cf4c-4787-90af-7bf13a6d6d1b%40googlegroups.com.

Sunday, December 22, 2019

Re: [google-cloud-sql-discuss] Create table command setting Default value for column not working

Hi Matt,
I figured this out. As Google cloud SQL is still on MySQL 5.7 , it is not supporting function use in default. My local MySQL was 8x so it was working there. To overcome this issue, i had to pass UUID from node.js app itself than depending on MySQL.

Thanks a lot
Kiran


On 23-Dec-2019 4:20 AM, 'Matt Turner' via Google Cloud SQL discuss <google-cloud-sql-discuss@googlegroups.com> wrote:
Kiran,

Do you know which part of the default is causing the error? Have you tried simplifying as a test? Also check the quotes you sometimes get conversions on copy and paste. 

Regards,

Matt

On Mon, 23 Dec 2019 at 6:47 am, Kiran Padiyar <kiran.padiyar@zenspectra.com> wrote:
Hi, 
We have set of tables developed earlier in onprem MySQL database. Now we are moving to Google SQL for production run. 
For example a sample table creation like follows onprem MySQL works perfect.
create table myschema.test (
valt int auto_increment primary key,
valkey varchar(50) default (replace(uuid(),''-'','''')),
valtree varchar(30)
)

However, when we connect to Google SQL instance and try to create same table, it shows error at the default. If we remove default for the column it works all ok.
Any idea how to fix this?

Thank you
Kiran

--
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/ded64fbc-e642-41b9-ad10-166a08a7a9ea%40googlegroups.com.
--


  
Matt Turner | mattyt@google.com
  Cloud Customer Engineer
  +61 (0) 447 533 754
  
Perth, Western Australia
The Sustainable Cloud

--
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/CADy4DuH%2BWQxfKd7mmYnwW14tZjGpoeaGAwr6JNa3Tooz9ZYmrw%40mail.gmail.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/fda8cc79-74f0-48c6-adf5-536ae22869f8%40email.android.com.

Re: [google-cloud-sql-discuss] Create table command setting Default value for column not working

Kiran,

Do you know which part of the default is causing the error? Have you tried simplifying as a test? Also check the quotes you sometimes get conversions on copy and paste. 

Regards,

Matt

On Mon, 23 Dec 2019 at 6:47 am, Kiran Padiyar <kiran.padiyar@zenspectra.com> wrote:
Hi, 
We have set of tables developed earlier in onprem MySQL database. Now we are moving to Google SQL for production run. 
For example a sample table creation like follows onprem MySQL works perfect.
create table myschema.test (
valt int auto_increment primary key,
valkey varchar(50) default (replace(uuid(),''-'','''')),
valtree varchar(30)
)

However, when we connect to Google SQL instance and try to create same table, it shows error at the default. If we remove default for the column it works all ok.
Any idea how to fix this?

Thank you
Kiran

--
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/ded64fbc-e642-41b9-ad10-166a08a7a9ea%40googlegroups.com.
--


  
Matt Turner | mattyt@google.com
  Cloud Customer Engineer
  +61 (0) 447 533 754
  
Perth, Western Australia
The Sustainable Cloud

--
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/CADy4DuH%2BWQxfKd7mmYnwW14tZjGpoeaGAwr6JNa3Tooz9ZYmrw%40mail.gmail.com.

Saturday, December 21, 2019

[google-cloud-sql-discuss] Create table command setting Default value for column not working

Hi, 
We have set of tables developed earlier in onprem MySQL database. Now we are moving to Google SQL for production run. 
For example a sample table creation like follows onprem MySQL works perfect.
create table myschema.test (
valt int auto_increment primary key,
valkey varchar(50) default (replace(uuid(),''-'','''')),
valtree varchar(30)
)

However, when we connect to Google SQL instance and try to create same table, it shows error at the default. If we remove default for the column it works all ok.
Any idea how to fix this?

Thank you
Kiran

--
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/ded64fbc-e642-41b9-ad10-166a08a7a9ea%40googlegroups.com.

Tuesday, December 17, 2019

[google-cloud-sql-discuss] Re: auto sync table using query

Dully Noted and thanks for bringing it to my attention.

On Monday, December 16, 2019 at 8:38:42 PM UTC+5:30, Jun (Cloud Platform Support) wrote:
Hi, 

Google Groups are reserved for general product discussion, StackOverflow for technical questions whereas Issue Tracker for product bugs (unexpected behaviors) and feature requests.

To get a better support you should post to the relevant forum, thus please read the Community Support article for better understanding.




On Friday, November 29, 2019 at 8:45:30 AM UTC-5, LETS LEARN SOMETHING wrote:
HI friends ,

I am new in Google Big query . Currently I am trying to create a table/view based on data of few different tables.

let us assume the query is like this :

create table datasetC.TableA as

select col1, col2, ..... from (
select col1,col2,col3 ,sum(col5),sum(col6) .....
   datasetA.tableA   left join  datasetA. tableb   left join  datasetA.tablec ) inner join ( select ....... datasetA.tablea ,datasetA.tableb)
union all
select col1, col2, ..... from (
select col1,col2,col3 ,sum(col5),sum(col6) .....
   datasetB.tableB   left join   datasetB.tableC   left join  datasetB.tableD ) inner join ( select ....... datasetB.tablee ,datasetB.tablef)


Now these tables are being refreshed at different times and while loading data in our table, we may have some tables which are yet to be refreshed.
Is there any way to set auto sync of the table just like we have materialised view.

normal view is not reliable as we have very huge data (around 6 tables with 50+ TB of data )  and we get memory issue.

any advice will be helpful .

Thanks in advance

--
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/c7a63df7-8f6a-474a-8801-b12f0898b010%40googlegroups.com.

Monday, December 16, 2019

[google-cloud-sql-discuss] Re: auto sync table using query

Hi, 

Google Groups are reserved for general product discussion, StackOverflow for technical questions whereas Issue Tracker for product bugs (unexpected behaviors) and feature requests.

To get a better support you should post to the relevant forum, thus please read the Community Support article for better understanding.




On Friday, November 29, 2019 at 8:45:30 AM UTC-5, LETS LEARN SOMETHING wrote:
HI friends ,

I am new in Google Big query . Currently I am trying to create a table/view based on data of few different tables.

let us assume the query is like this :

create table datasetC.TableA as

select col1, col2, ..... from (
select col1,col2,col3 ,sum(col5),sum(col6) .....
   datasetA.tableA   left join  datasetA. tableb   left join  datasetA.tablec ) inner join ( select ....... datasetA.tablea ,datasetA.tableb)
union all
select col1, col2, ..... from (
select col1,col2,col3 ,sum(col5),sum(col6) .....
   datasetB.tableB   left join   datasetB.tableC   left join  datasetB.tableD ) inner join ( select ....... datasetB.tablee ,datasetB.tablef)


Now these tables are being refreshed at different times and while loading data in our table, we may have some tables which are yet to be refreshed.
Is there any way to set auto sync of the table just like we have materialised view.

normal view is not reliable as we have very huge data (around 6 tables with 50+ TB of data )  and we get memory issue.

any advice will be helpful .

Thanks in advance

--
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/14744461-3196-4650-937b-4e00799ae8b8%40googlegroups.com.

Friday, December 13, 2019

[google-cloud-sql-discuss] Re: Connect to Cloud SQL from within another pod using cloud proxy

To answer your question directly about being able to connect to CloudSQL Instance from GKE using CloudSQL proxy in a different Project, I say Yes, it is possible.

There is this documentation[1] that explains how to connect to a CloudSQL from GKE however, to connect from within a different Project, there are a few changes that needed to be made:

Firstly, ensure that the network port 5434 (or whichever port you are deploying Cloud SQL **Proxy**) is not in use, then refresh the GKE pod. To do this, run "$ netstat -tulpn" in your console. If the port is listed at the end of one of the entires in the "Local Address" column, kill that connection by running "kill [PID]", where PID is the corresponding PID for that row. After this, reload the GKE pod that is trying to connect to Cloud SQL [2]. This is important to do because if the port is already occupied when the port runs Cloud SQL Proxy and attempts to bind to that port, the binding will fail and cause a connection error. 

- Refresh the credentials for service account cloud-sql@[project-ID].iam.gserviceaccount.com. Validate that the service account has the "roles/cloudsql.client" role [3]. Delete the service account's .json key and generate a new one [4]. Delete the GKE secret holding the service account crednetials and redeploy a new one. For example, if your service account credentials file is called "key.json", the target secret name is "credentials.json", and your console is in the directory containing "key.json", run: "$ kubectl create secret generic cloudsql-instance-credentials --from-file=credentials.json=../key.json". Finally, reload the GKE pod that is trying to connect to Cloud SQL [2]. This reload is necessary to refresh the pod's consumption of the secret. 

[1]https://cloud.google.com/sql/docs/mysql/connect-kubernetes-engine
[2] To restart your pods, go to Cloud Console > Kubernetes Engine > Workloads > select your workload > Overview tab. Then, under the "Managed pods" section, copy the pod name. In your console, first authenticate kubectl if you haven't already in this session ("$ gcloud container clusters get-credentials [CLUSTER_NAME] --zone europe-west1-b"). Then run "$ kubectl delete pod [POD_NAME]" to delete the pod. GKE will automatically spawn a new one, which will be ready to serve in a few seconds.
[3] https://cloud.google.com/sql/docs/mysql/project-access-control#roles
[4] https://cloud.google.com/iam/docs/creating-managing-service-account-keys#creating_service_account_keys

--
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/53cf552f-ada5-4ed7-9e97-600e747300b8%40googlegroups.com.

Thursday, December 12, 2019

[google-cloud-sql-discuss] Re: MySQL 5.8

Hello Euan, 

There is a general tendency to adopt more recent MySQL versions in time. When exactly each new version is going to get released is not yet determined, but the releases get published in due course. This applies to MySQL 5.8 as well. You may find relevant information in the "Database version policies" 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/06cb52c8-a00b-4832-a15f-4cb3135d95cc%40googlegroups.com.

Wednesday, December 11, 2019

[google-cloud-sql-discuss] MySQL 5.8

Hi, 

I am just wondering if there are any plans for cloud-sql to implement MySQL 5.8? I do see that RDS supports MySQL 5.8 and was wondering anyone knows whether it is on the roadmap for cloud-sql?

Thanks,
Euan

--
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/7a60ed98-c375-4896-a1fd-cb4ca0996d2f%40googlegroups.com.

Monday, December 9, 2019

[google-cloud-sql-discuss] Re: Getting the error message "_server FATAL: connection to client lost" on Cloud SQL Postgres 9.6

Hello Mapperkids,


I don't think this forum is meant to report issues. Google Groups is used to discuss Google products and share opinions. Google Issue Tracker is meant to report issues.


As I can't see your project details, I can't offer advice on what to do next.


--
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/292cfe35-547c-458f-9973-4e9b8a6742ea%40googlegroups.com.

Re: [google-cloud-sql-discuss] Export and database availability

Thanks, that's what I assumed but I wanted to make sure before going ahead. Cheers!

Le lundi 9 décembre 2019 11:48:17 UTC-5, Pavel Ivanov a écrit :
This warning is only about Google API operations. The database will
remain available for SQL queries, though depending on your load it
might get a little slower, and some DDL queries might get blocked.

On Mon, Dec 9, 2019 at 8:42 AM Louis-Philippe Papillon
<lp.pa...@gmail.com> wrote:
>
> Hi guys,
>
> I'm trying to create a read replicate in another org/project, therefore it's looking like an external replica. When creating it, it's asking me to restore from an export in Cloud Storage, so I went to create the export in the original instance, and I get this warning:
>
>
> I just want to clarify what this means "you will not be able to perform operations on your instance". Does that include SELECT/INSERT/UPDATE/DELETE? Or just higher level Google API operations on the instance? If the database will be unavailable, I need a better estimate of how long it will take, too. My database is 235 Gb in size.
>
> 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/05b27148-54d0-4412-9170-91f1a8ab5ade%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/9df1844d-299e-453c-b0ca-5f86f261d9d6%40googlegroups.com.

Re: [google-cloud-sql-discuss] Export and database availability

This warning is only about Google API operations. The database will
remain available for SQL queries, though depending on your load it
might get a little slower, and some DDL queries might get blocked.

On Mon, Dec 9, 2019 at 8:42 AM Louis-Philippe Papillon
<lp.papillon@gmail.com> wrote:
>
> Hi guys,
>
> I'm trying to create a read replicate in another org/project, therefore it's looking like an external replica. When creating it, it's asking me to restore from an export in Cloud Storage, so I went to create the export in the original instance, and I get this warning:
>
>
> I just want to clarify what this means "you will not be able to perform operations on your instance". Does that include SELECT/INSERT/UPDATE/DELETE? Or just higher level Google API operations on the instance? If the database will be unavailable, I need a better estimate of how long it will take, too. My database is 235 Gb in size.
>
> 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/05b27148-54d0-4412-9170-91f1a8ab5ade%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/CAAG%3DWUt9GKBdV%2BuwmWU%3DVZx-10RXifN52pR3BhCdKdA5Jc0Ypw%40mail.gmail.com.

Re: [google-cloud-sql-discuss] Audit Logs not showing for Cloud SQL?

Nevermind, it is fixed now.

On Mon, Dec 9, 2019 at 9:16 AM Eric Benjamin <eric.benjamin2010@gmail.com> wrote:
I turned on Admin Read, Data Read and Data Write in Audit Logs for Cloud SQL, created a test table and wrote some data. However, there's still nothing in my logs viewer even though it's set to view Audited Resource / All Logs. Did I miss a step?

--
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/0a9fc247-b34e-4a4e-921e-742680b3f5f4%40googlegroups.com.


--
Thanks,
Eric Benjamin

--
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/CAHpr0Cs182JnHOzHPM2qGc080%2BmOoQ_XPfg%3DSvr7%3DrMuxkuDJg%40mail.gmail.com.

[google-cloud-sql-discuss] Export and database availability

Hi guys,

I'm trying to create a read replicate in another org/project, therefore it's looking like an external replica. When creating it, it's asking me to restore from an export in Cloud Storage, so I went to create the export in the original instance, and I get this warning:

Screen Shot 2019-12-05 at 3.41.57 PM.png


I just want to clarify what this means "you will not be able to perform operations on your instance". Does that include SELECT/INSERT/UPDATE/DELETE? Or just higher level Google API operations on the instance? If the database will be unavailable, I need a better estimate of how long it will take, too. My database is 235 Gb in size.

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/05b27148-54d0-4412-9170-91f1a8ab5ade%40googlegroups.com.

Saturday, December 7, 2019

[google-cloud-sql-discuss] Audit Logs not showing for Cloud SQL?

I turned on Admin Read, Data Read and Data Write in Audit Logs for Cloud SQL, created a test table and wrote some data. However, there's still nothing in my logs viewer even though it's set to view Audited Resource / All Logs. Did I miss a step?

--
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/0a9fc247-b34e-4a4e-921e-742680b3f5f4%40googlegroups.com.

Friday, December 6, 2019

[google-cloud-sql-discuss] Getting the error message "_server FATAL: connection to client lost" on Cloud SQL Postgres 9.6

Hi,

We set up a cloud SQL - Postgres instance and connect with the Flex app engine running python app, today the app getting stuck/slow and I check the log and the error showing is related to the cloud SQL

Here is the error message "_server FATAL:  connection to client lost"  and it keeps comes up every 15-20 minutes. Does anyone know what causes that error?

Our Cloud SQL Instance is the f1-micro which only has 0.6GB ram and 1vCPU, 10GG storge.

Or is that possible not enough resource on our flex app engine which is one instance, 1vCPU, and 1.7GB ram.

Thanks for your 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/c1f35de5-6d6d-4437-9445-da208a9579cc%40googlegroups.com.

Re: [google-cloud-sql-discuss] Re: Create Locales or change Template1 locale

Hello Peter,

Although this forum is for discussing Google products and sharing opinions, I'll do my best to assist you. 

What gcloud command with options are you using? I will need this to reproduce and confirm the behavior.

--
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/d015bbcc-9e96-49f3-8c81-fdf4439cd588%40googlegroups.com.

[google-cloud-sql-discuss] Re: HELP: My Cloud SQL is DOWN and its not working in any posible way.

Helllo Pablo,

Please note that Google Groups are reserved for general Google Cloud Platform and product discussions and not for reporting issues, which is why I suggest moving the troubleshooting to Issue Tracker, where issues can be turned private in case we need to gather any project specific details.

--
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/b54620b3-5f51-4efe-afc9-74e8ba884e68%40googlegroups.com.

Re: [google-cloud-sql-discuss] Re: Create Locales or change Template1 locale

Dear Team,

this issue is over 2 years old and I got still the equivalent error, when trying to create Databases with the gcloud CLI-Tool. In Docs is written, that one can use the Collation and Encoding options mentioned in postgres Docs. You even support the CLI Options for collation and enconding. (see here https://cloud.google.com/sql/docs/postgres/create-manage-databases#create)

Do I miss something? If not, is there a workaround?

Kind regards

Peter

Am Dienstag, 28. März 2017 15:10:20 UTC+2 schrieb Ankush Agarwal:
Hey Oscar,

We are aware of the issue. We are planning to include support for a large set of collations soon. Release notes will be published here: https://cloud.google.com/sql/docs/postgres/release-notes

On Mon, Mar 27, 2017 at 2:22 PM, 'paynen' via Google Cloud SQL discuss <google-cloud...@googlegroups.com> wrote:
Hey Oscar,

Thanks for this report. I've replicated your findings. I'm unsure at the moment what solution to offer. Could you explain more about your use-case, and why you can't just store UTF-8 data without setting any locale?

Cheers,

Nick
Cloud Platform Community Support

On Monday, March 20, 2017 at 11:54:45 AM UTC-4, Oscar Serrano wrote:
Hi,
I'm trying to create a new postgresql database, but I cannot use the spanish Location. I've tried this:
create database mydb with ENCODING = 'UTF-8' LC_CTYPE = 'es_ES' LC_COLLATE = 'es_ES';

But I get an error: invalid Locale Name es_ES
How do I create it?
I've tried this:

postgres=> create collation es (locale="es_ES.utf8");ERROR: could not create locale "es_ES.utf8": Success
As you can say, it says Success, but also I get the error.How should I proceed?
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/396f11c6-1349-4510-83c8-a82f9dae81cf%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Ankush Agarwal

Software Engineer, Cloud SQL
 
There are 10 types of people in this world - those who understand binary and those who don't

--
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/8622b835-b9d7-4d2b-9bf2-6c686e7dc9dc%40googlegroups.com.

[google-cloud-sql-discuss] Re: Connect to Cloud SQL from within another pod using cloud proxy

Hi David

Thank you for your reply. Very helpful and following your guidelines, I was able to connect with Cloud SQL instance setup in the same GCP project. The issue was that my cluster was not VPC native. Is it possible to connect to Cloud SQL instance from GKE using Cloud SQL proxy  in a different project? Can you point me to see documentation that would help me out with this?

Warm Regards
Shikha

--
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/443ccaf9-66d4-41f9-9be4-1307d2f18a71%40googlegroups.com.

Thursday, December 5, 2019

Re: [google-cloud-sql-discuss] HELP: My Cloud SQL is DOWN and its not working in any posible way.

What does Google Stackdriver report for this instance?

Is there an Upgrade button next to the instance name?

Double check that you do not have a billing problem.

From: google-cloud-sql-discuss@googlegroups.com <google-cloud-sql-discuss@googlegroups.com> on behalf of Pablo Lopez <pablolf@gmail.com>
Sent: Thursday, December 5, 2019 5:54 PM
To: Google Cloud SQL discuss <google-cloud-sql-discuss@googlegroups.com>
Subject: [google-cloud-sql-discuss] HELP: My Cloud SQL is DOWN and its not working in any posible way.
 
I have a MySQL 1st Gen 5.6  that has been working fine for a couple of years and now its been down for at least 24 hours and we have tried restarting it and stopping and starting and nothing seems to work. 

Also we just noticed the automatic backups have been failing silently for a month so we can't try to do a restore from backup without loosing a month worth of data. 

Storage used dropped to cero on graph.

On the google console when I try to access the Users or Databases section I get this error: "Users cannot be loaded from MySQL at this time. Make sure your instance is runnable.", "Databases cannot be loaded from MySQL at this time. Make sure your instance is runnable.".

--
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/26e38d65-3270-469c-95ae-534d9421be1a%40googlegroups.com.

[google-cloud-sql-discuss] HELP: My Cloud SQL is DOWN and its not working in any posible way.

I have a MySQL 1st Gen 5.6  that has been working fine for a couple of years and now its been down for at least 24 hours and we have tried restarting it and stopping and starting and nothing seems to work. 

Also we just noticed the automatic backups have been failing silently for a month so we can't try to do a restore from backup without loosing a month worth of data. 

Storage used dropped to cero on graph.

On the google console when I try to access the Users or Databases section I get this error: "Users cannot be loaded from MySQL at this time. Make sure your instance is runnable.", "Databases cannot be loaded from MySQL at this time. Make sure your instance is runnable.".

--
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/26e38d65-3270-469c-95ae-534d9421be1a%40googlegroups.com.

[google-cloud-sql-discuss] Re: Can't get SSL to work for Postgresql

Hello Taylor,

Please note that Google Groups are reserved for general Google Cloud Platform and product discussions and not for reporting issues, which is why I suggest moving the troubleshooting to Issue Tracker, where issues can be turned private in case we need to gather any project specific details.

--
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/6a4830d1-32af-49ab-b8c1-d5cc60679fad%40googlegroups.com.

[google-cloud-sql-discuss] Re: Connect to Cloud SQL from within another pod using cloud proxy

Hello,


As a starting point, I would review the official documentation about connecting to Cloud SQL from Kubernetes Engine using the Cloud SQL Proxy Docker image if you haven't since there are some requirements that your GKE cluster needs to meet such as:


Must be running version 1.2 or higher, with the kubectl command-line tool installed and configured to communicate with the cluster.

Having an application container in a pod on the GKE cluster.


In the Cloud SQL side:

The Cloud SQL Admin API is enabled.

You must know the location of the key file associated with a service account with the proper privileges for your Cloud SQL instance.


This is only the most important requirements that I see could cause such error for the complete requirements you can review the document shared above.


You can also follow the connection overview part of the documentation where you can see a properly configured pod configuration file as I see you are using 0.0.0.0:3306 on your connection strong but can't see your pod configuration file.


If after reviewing the documentation shared above and making sure that the requirements are fulfilled, you have not been able to connect to your Cloud SQL instance, you can create an Issue Tracker and we may be able to investigate further.

--
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/aa412a44-e66b-48a7-8f60-e24aa1f88243%40googlegroups.com.

Wednesday, December 4, 2019

[google-cloud-sql-discuss] Re: Mysql SSL certificates

Hello Pedja,

According to our documentation, it is not possible to share an SSL certificate among different instances at this time. You may find the information 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/c95493d4-75a3-4088-83e2-f4c3a4a81310%40googlegroups.com.

[google-cloud-sql-discuss] Re: Can't get SSL to work for Postgresql

Thanks for your reply, Elliott. This group is for "Cloud SQL", so I didn't provide that information, but you are wise to ask. I am using Google Cloud SQL and downloaded all the certificates/keys from the "Connections" tab on the SQL dashboard.

On Wednesday, December 4, 2019 at 5:42:32 PM UTC-6, Elliott (Google Cloud Platform Support) wrote:
Hello Taylor,

To provide you with the best answer, can you provide the documentation you used to download the server and client certificates? Are you using Cloud SQL or did you install database software on a Compute Virtual machine?

--
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/92cee663-ecfa-4e73-b19d-a0e6488bf6c1%40googlegroups.com.

[google-cloud-sql-discuss] Re: Can't get SSL to work for Postgresql

Hello Taylor,

To provide you with the best answer, can you provide the documentation you used to download the server and client certificates? Are you using Cloud SQL or did you install database software on a Compute Virtual machine?

--
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/ddea93e6-8e91-404c-a78c-59bd5a3c90d6%40googlegroups.com.

[google-cloud-sql-discuss] Can't get SSL to work for Postgresql

I downloaded the server & client certificates, but they don't verify using openssl:

openssl verify -verbose -issuer_checks -CAfile /etc/database/certificates/server-ca.pem -purpose sslclient /etc/database/certificates/client-cert.pem

It fails with the message:

CN = Test, O = "Google, Inc", C = US
error 20 at 0 depth lookup: unable to get local issuer certificate
error /etc/database/certificates/client-cert.pem: verification failed

Also, when plugging in the file paths into DbVisualizer, I get this error:

Long Message:
FATAL: connection requires a valid client certificate

Details:
   Type: org.postgresql.util.PSQLException
   SQL State: 28000


My understanding is that the issuer of the client should match the subject of the server, but using the following commands suggest that they don't:

openssl x509 -in /etc/database/certificates//client-cert.pem -noout -issuer
openssl x509 -noout -subject -in /etc/database/certificates/server-ca.pem

issuer=dnQualifier = 319a6a2b-0750-41d3-9b05-16cdf8b121cf, CN = Google Cloud SQL Client CA Test, O = "Google, Inc", C = US
subject=dnQualifier = 41ff6064-07be-43c1-9e00-94a9de7cc5c1, CN = Google Cloud SQL Server CA, O = "Google, Inc", C = US



Any suggestions on how to debug appreciated.

--
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/a869663c-d835-44df-a681-1a930143450f%40googlegroups.com.

[google-cloud-sql-discuss] Mysql SSL certificates

Hi,

is it possible to use same SSL certificates to connect different instances?
I want to split tables over few instances, or we will exceed 10.000 tables limit? i hope that i don't have to define a new certificate for each instance...

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/90f7cd36-da0b-4f6a-99ae-37b108750ec3%40googlegroups.com.