Friday, May 31, 2019

[google-cloud-sql-discuss] Re: Cloud Sql Backup Error Blocking Cloud Sql

Hi, 

Without actually looking at your Cloud SQL instance and based on the information you have provided, your instance appears to be conducting high activities during the backup process. 

Typically, the error message you have provided indicates that there was a continuous increase in temp data which led to the point where disk size reached its hard limit at 10,230gb. You may find more information about that here. Essentially, when this limit is hit, the storage disk can no longer increase. This also applies to a instance that has automatic storage increase enabled. Without actually seeing the full scope of operations being conducted on your instance, I can not effectively isolate  Automated Backups being the cause of your issue.

If you would like to take a closer look you can always refer to the support page offered 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/3f6e5172-9d2c-495d-bbe3-dac562193198%40googlegroups.com.

[google-cloud-sql-discuss] Re: Timeout Errors connecting to a Google Cloud SQL instance from a webpage

Hi, this "Aborted connection nnnn to db:" error message is triggered when an existing connection is terminated improperly, which may look erroneous but is actually perfectly normal. 

Aborted connections happen because of unclean closure of connection or networking problem between the server and the client, but not because of the server [1].

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

1) It won't trigger "Aborted connection" error when mysql client closes cleanly.
2) If the proxy client is killed but didn't close mysql client --> The socket connection is still alive.
    a) manually close the socket connection at the client side
    b) OR wait until times out based "wait_timeout" in MySQL server and the connection closed --> "Aborted connection" error. 

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

In conclusion, if you want to reduce such errors in the logs, I'd suggest to cleanly close each connection

[1] https://cloud.google.com/sql/docs/mysql/diagnose-issues#connection
[2] https://dev.mysql.com/doc/refman/8.0/en/communication-errors.html
[3] https://www.percona.com/blog/2016/05/16/mysql-got-an-error-reading-communication-packet-errors/

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/bcd19643-188a-4cd9-bde1-fc87d88ea93e%40googlegroups.com.

[google-cloud-sql-discuss] Re: Unable to use "Serverless VPC Access" across regions, but works within same region

Kurtis, thanks for a lot for looking into this and also considering updating the docs. It cost me a couple days of head scratching. Next up, moving SQL server to different region :-)

Hans

On Friday, May 31, 2019 at 8:58:52 AM UTC-7, Kurtis Van Gent wrote:
Hey Hans,

This is a fine form to ask this kind of question :). 

I looked into this a bit deeper, and Private IP on Cloud SQL currently requires the resource to be in the same region. Unfortunately in this case the VPC connector is in the same region with your Serverless deployment, and thus is unable to connect to the Cloud SQL instance via Private IP. There is work being done to remove this limitation, but unfortunately it isn't finished yet.

This is obviously confusing since the docs contradict, but I've filed an internal bug to try and clarify the position on the VPC Serverless page. Sorry for the confusion. 

Thanks,
Kurtis


On Thursday, May 30, 2019 at 5:37:13 PM UTC-7, Hans Ravnaas wrote:
If there is a better forum for this, please let me know.

On Wednesday, May 29, 2019 at 3:54:55 PM UTC-7, Hans Ravnaas wrote:
Hello,

I'm running into the below and wanted to see if this is a known issue. According to this doc, "a connector can be in a different region than the resource it is sending traffic to", but I'm so far unable to accomplish this. Certainly possible I'm doing something wrong here of course. Here's my setup:

Fails with socket timeout:
Cloud Function (Java) in us-central1 -> serverless VPC connector in us-central1 -> internal IP of Cloud SQL (postgres 11) in us-west1-b

Works fine:
Cloud Function (Java) in us-central1 -> serverless VPC connector in us-central1 -> internal IP of Cloud SQL (postgres 11) in us-central1-a

I'm using the same connector in both of the above scenarios, and the SQL instance should be configured the same way as well, using the default VPC. The connector's ip-range is10.10.0.0/28. Wondering if there is a routing issue between 10.10.0.0/28 (us-central connector) and the default network in us-west1 where SQL resides? I have not changed or added any routes. Also, I don't see any firewall rules blocking here.

Any help appreciated!

VPC_networks.png

Hans

--
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/ee2513d0-0de6-4478-8411-05913a358918%40googlegroups.com.

[google-cloud-sql-discuss] Cloud Sql Backup Error Blocking Cloud Sql


Hi,

I have a cloud-sql instance with an automated backup enabled, today just after the backup I received the following error appeared in operation :-

May 31, 2019, 5:57:24 AMDelete backup An unknown error occurred


Following that following code error appeared in the cloud-sql log ; -
2019-05-31 05:55:35.424 IST 2019-05-31T00:25:35.423588Z 17866 [ERROR] InnoDB: Write to file ./ibtmp1failed at offset 10801456873472, 1048576 bytes should have been written, only 0 were written. Operating system error number 28. Check that your OS and file system support files of this size. Check also that the disk is not full or a disk quot

After this cloud-sql became almost unresponsive to the queries  until I have to restart the instance. My question is  Automated Backup is the root cause of problem ? If yes, how shall I avoid it in future so that my business does not suffers . 

--
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/65912345-bf49-45c3-9084-081a04648569%40googlegroups.com.

[google-cloud-sql-discuss] Re: Unable to use "Serverless VPC Access" across regions, but works within same region

Hey Hans,

This is a fine form to ask this kind of question :). 

I looked into this a bit deeper, and Private IP on Cloud SQL currently requires the resource to be in the same region. Unfortunately in this case the VPC connector is in the same region with your Serverless deployment, and thus is unable to connect to the Cloud SQL instance via Private IP. There is work being done to remove this limitation, but unfortunately it isn't finished yet.

This is obviously confusing since the docs contradict, but I've filed an internal bug to try and clarify the position on the VPC Serverless page. Sorry for the confusion. 

Thanks,
Kurtis


On Thursday, May 30, 2019 at 5:37:13 PM UTC-7, Hans Ravnaas wrote:
If there is a better forum for this, please let me know.

On Wednesday, May 29, 2019 at 3:54:55 PM UTC-7, Hans Ravnaas wrote:
Hello,

I'm running into the below and wanted to see if this is a known issue. According to this doc, "a connector can be in a different region than the resource it is sending traffic to", but I'm so far unable to accomplish this. Certainly possible I'm doing something wrong here of course. Here's my setup:

Fails with socket timeout:
Cloud Function (Java) in us-central1 -> serverless VPC connector in us-central1 -> internal IP of Cloud SQL (postgres 11) in us-west1-b

Works fine:
Cloud Function (Java) in us-central1 -> serverless VPC connector in us-central1 -> internal IP of Cloud SQL (postgres 11) in us-central1-a

I'm using the same connector in both of the above scenarios, and the SQL instance should be configured the same way as well, using the default VPC. The connector's ip-range is10.10.0.0/28. Wondering if there is a routing issue between 10.10.0.0/28 (us-central connector) and the default network in us-west1 where SQL resides? I have not changed or added any routes. Also, I don't see any firewall rules blocking here.

Any help appreciated!

VPC_networks.png

Hans

--
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/faad9307-7d1b-4de2-95b2-ad6bdcea5a73%40googlegroups.com.

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

Same issue here with App engine (python3 - standard environment) and cloud sql -2nd Gen Mysql instance
 
I think that it's not a problem with sql cloud, or with the configuration of my application, but that it's an app engine problem. I came to this conclusion in the following way:
 

if I connect to the sql cloud instance through Mysql workbench, no connection is aborted
Similarly if I run my application on a local server, but connecting to cloud sql (through the cloud_sql_proxy), no error is generated and everything works perfect.

--
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/0dffed0d-88cd-4334-8a7b-e9df4da99963%40googlegroups.com.

Thursday, May 30, 2019

[google-cloud-sql-discuss] Re: Unable to use "Serverless VPC Access" across regions, but works within same region

If there is a better forum for this, please let me know.

On Wednesday, May 29, 2019 at 3:54:55 PM UTC-7, Hans Ravnaas wrote:
Hello,

I'm running into the below and wanted to see if this is a known issue. According to this doc, "a connector can be in a different region than the resource it is sending traffic to", but I'm so far unable to accomplish this. Certainly possible I'm doing something wrong here of course. Here's my setup:

Fails with socket timeout:
Cloud Function (Java) in us-central1 -> serverless VPC connector in us-central1 -> internal IP of Cloud SQL (postgres 11) in us-west1-b

Works fine:
Cloud Function (Java) in us-central1 -> serverless VPC connector in us-central1 -> internal IP of Cloud SQL (postgres 11) in us-central1-a

I'm using the same connector in both of the above scenarios, and the SQL instance should be configured the same way as well, using the default VPC. The connector's ip-range is10.10.0.0/28. Wondering if there is a routing issue between 10.10.0.0/28 (us-central connector) and the default network in us-west1 where SQL resides? I have not changed or added any routes. Also, I don't see any firewall rules blocking here.

Any help appreciated!

VPC_networks.png

Hans

--
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/35db3552-aafb-4661-bac6-d041fea6583a%40googlegroups.com.

Wednesday, May 29, 2019

[google-cloud-sql-discuss] Timeout Errors connecting to a Google Cloud SQL instance from a webpage

textPayload,insertId,resource.type,resource.labels.project_id,resource.labels.database_id,resource.labels.region,timestamp,severity,logName,receiveTimestamp
innodb_buffer_pool_load_at_startup=ON,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@ad,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.557423Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
innodb_file_format=Barracuda,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@ae,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.557655Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
innodb_file_per_table=ON,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@af,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.557854Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
innodb_flushing_avg_loops=5,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@ag,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.558030Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
innodb_flush_method=O_DIRECT,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@ah,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.558203Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
innodb_flush_neighbors=2,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@ai,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.564601Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
innodb_io_capacity=5000,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@aj,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.564998Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
innodb_log_file_size=512M,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@ak,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.565213Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
innodb_lru_scan_depth=2048,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@al,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.565404Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
innodb_monitor_enable=all,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@am,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.568951Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
innodb_page_cleaners=8,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@an,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.569204Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
master_info_repository=TABLE,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@ao,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.569403Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
max_binlog_size=104857600 # 100 MB,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@ap,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.574701Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
memlock=true,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@aq,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.575004Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
performance_schema=OFF,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@ar,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.575193Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
pid_file=/mysql/mysql.pid,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@as,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.575403Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
relay_log_info_repository=TABLE,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@at,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.576672Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
relay_log=/mysql/relaylog/relay-log,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@au,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.576922Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
relay_log_recovery=ON,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@av,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.577105Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
"require_super_for_system_table_writes=event,func,plugin,proc,heartbeat",s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@aw,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.577288Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
reserved_super_connections=20,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@ax,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.577470Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
rpl_semi_sync_master_async_notify_socket=/semisync/semisync.sock,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@ay,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.581809Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
rpl_semi_sync_master_do_async_notify=ON,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@az,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.582082Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
rpl_semi_sync_master_enabled=1,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@b10,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.582267Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
rpl_semi_sync_master_timeout=3000 # 3 second,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@b11,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.582461Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
rpl_semi_sync_master_wait_point=AFTER_SYNC,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@b12,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.583791Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
secure_file_priv=/mysql/tmp,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@b13,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.584017Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
skip_name_resolve=ON,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@b14,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.584219Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
slave_net_timeout=30,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@b15,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.584401Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
slow_query_log_file=/mysql/logs/slow.log,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@b16,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.590760Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
socket=/mysql/mysql.sock,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@b17,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.591057Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
ssl_ca=/mysql/datadir/client_ca_cert.pem,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@b18,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.591251Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
ssl_cert=/mysql/datadir/server_cert.pem,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@b19,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.591431Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
ssl_cipher=ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@b1a,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.593776Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
ssl_key=/mysql/datadir/server_pkey.pem,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@b1b,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.594016Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
sync_binlog=1,s=45471ca64e5d41ba8e617e8a1780d267;i=42c6fd;b=b59693f07e96460799643fad0cd0fe81;m=fb7076d43f;t=589f54e151ce8;x=3ad55d472d1bae99-0@b1c,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.594281Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.545334627Z
system_user_table=true,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@a1,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.594461Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
tmpdir=/mysql/tmp,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@a2,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.595680Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
max_allowed_packet=64553,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@a3,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.595879Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
wait_timeout=31536000,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@a4,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.596063Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
log_bin=/mysql/binlog/mysql-bin,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@a5,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.596243Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
gtid_mode=ON,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@a6,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.596417Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
log_slave_updates=ON,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@a7,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.603867Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
enforce_gtid_consistency=ON,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@a8,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.604136Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
server-id=3294777933,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@a9,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.604327Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
innodb_buffer_pool_size=1376711884,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@aa,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.604509Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
innodb_buffer_pool_instances=1,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@ab,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.605533Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
max_connections=4030,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@ac,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.606823Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
enforce_storage_engine=Innodb,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@ad,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.607019Z,INFO,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
2019-05-28T16:39:13.750206Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@ae,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.752737Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
2019-05-28T16:39:13.750434Z 0 [Warning] Insecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@af,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.753175Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
2019-05-28T16:39:13.750472Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.14-google-log) starting as process 1 ...,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@ag,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.753369Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
2019-05-28T16:39:13.761535Z 0 [Note] Plugin 'AUDIT_LOG' is disabled.,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@ah,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.762655Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
2019-05-28T16:39:13.763233Z 0 [Note] Plugin 'FEDERATED' is disabled.,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@ai,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.763339Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
2019-05-28T16:39:13.764144Z 0 [Warning] InnoDB: Using innodb_file_format is deprecated and the parameter may be removed in future releases. See http://dev.mysql.com/doc/refman/5.7/en/innodb-file-format.html,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@aj,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.764260Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
2019-05-28T16:39:13.765126Z
0 [Note] InnoDB: PUNCH HOLE support not available,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@ak,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.765236Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
2019-05-28T16:39:13.765587Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@al,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.765685Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
2019-05-28T16:39:13.765950Z 0 [Note] InnoDB: Uses event mutexes,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@am,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.766033Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
2019-05-28T16:39:13.766268Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@an,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.766350Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
2019-05-28T16:39:13.766606Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@ao,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.766686Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
2019-05-28T16:39:13.766938Z 0 [Note] InnoDB: Using Linux native AIO,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@ap,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.767019Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
2019-05-28T16:39:13.777836Z 0 [Note] InnoDB: Number of pools: 1,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@aq,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.778102Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
2019-05-28T16:39:13.778800Z 0 [Note] InnoDB: Using CPU crc32 instructions,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@ar,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.778939Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
"2019-05-28T16:39:13.782067Z 0 [Note] InnoDB: Initializing buffer pool, total size = 1.375G, instances = 1, chunk size = 128M",s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@as,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:13.782249Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
2019-05-28T16:39:14.023417Z 0 [Note] InnoDB: Completed initialization of buffer pool,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@at,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.023777Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
"2019-05-28T16:39:14.202336Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().",s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@au,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.202744Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
2019-05-28T16:39:14.227509Z 0 [Note] InnoDB: Highest supported file format is Barracuda.,s=45471ca64e5d41ba8e617e8a1780d267;i=42c72f;b=b59693f07e96460799643fad0cd0fe81;m=fb707777b4;t=589f54e15c05d;x=203271d8530a5aed-0@av,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.227858Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:19.828229240Z
2019-05-28T16:39:14.500316Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables,s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@a1,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.500741Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.505354Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...,s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@a2,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.505657Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.705627Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.,s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@a3,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.705994Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.707524Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.,s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@a4,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.707793Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.708193Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.,s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@a5,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.708301Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.709097Z 0 [Note] InnoDB: Waiting for purge to start,s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@a6,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.709260Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.760527Z 0 [Note] InnoDB: 5.7.14 started; log sequence number 2418068343,s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@a7,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.760964Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.763574Z 0 [Note] InnoDB: Loading buffer pool(s) from /mysql/datadir/ib_buffer_pool,s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@a8,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.763831Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.768417Z 0 [Note] Semi-sync replication initialized for transactions.,s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@a9,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.768679Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.769125Z 0 [Note] Semi-sync replication enabled on the master.,s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@aa,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.769263Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
"2019-05-28T16:39:14.837114Z 0 [Note] Skip crash recovery, binlog file '/mysql/binlog/mysql-bin.000020' size: 217",s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@ab,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.837403Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.839080Z 0 [Note] Starting ack receiver thread,s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@ac,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.839306Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.853059Z 0 [Note] Found gtids in binlog: '7017ee11-4f80-11e9-83f7-42010a8002c4:1-5454264',s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@ad,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.853418Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.854154Z 0 [Note] Found gtids purged from binlog: '7017ee11-4f80-11e9-83f7-42010a8002c4:1-4749079',s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@ae,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.854375Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.857660Z 0 [Note] Skipping generation of SSL certificates as options related to SSL are specified.,s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@af,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.857898Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.863237Z 0 [Warning] CA certificate /mysql/datadir/client_ca_cert.pem is self signed.,s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@ag,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.863518Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.864017Z 0 [Note] Skipping generation of RSA key pair as key files are present in data directory.,s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@ah,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.864181Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.865478Z 0 [Note] Server hostname (bind-address): '*'; port: 3306,s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@ai,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.865640Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.865973Z 0 [Note] IPv6 is available.,s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@aj,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.866077Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.866354Z 0 [Note] - '::' resolves to '::';,s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@ak,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.866450Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.866733Z 0 [Note] Server socket created on IP: '::'.,s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@al,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.866829Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.879793Z 0 [Warning] 'user' entry 'root@localhost' ignored in --skip-name-resolve mode.,s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@am,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.880145Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.880695Z 0 [Warning] 'user' entry 'cloudsqlimport@localhost' ignored in --skip-name-resolve mode.,s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@an,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.880873Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
"2019-05-28T16:39:14.881150Z 0 [Note] Loaded users from system_user table: root@localhost,cloudsqlreplica@%,cloudsqlimport@localhost.",s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@ao,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.881251Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.881594Z 0 [Note] InnoDB: Buffer pool(s) load completed at 190528 16:39:14,s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@ap,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.881733Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.882179Z 0 [Warning] 'user' entry 'mysql.sys@localhost' ignored in --skip-name-resolve mode.,s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@aq,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.882319Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.884118Z 0 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.,s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@ar,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.884881Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.903266Z 0 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.,s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@as,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.903616Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.919999Z 0 [Note] Event Scheduler: Loaded 0 events,s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@at,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.920313Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
2019-05-28T16:39:14.921108Z 0 [Note] /usr/sbin/mysqld: ready for connections.,s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@au,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.921298Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
Version: '5.7.14-google-log' socket: '/mysql/mysql.sock' port: 3306 (Google),s=45471ca64e5d41ba8e617e8a1780d267;i=42c761;b=b59693f07e96460799643fad0cd0fe81;m=fb70854bdc;t=589f54e239485;x=2ae451af1ada7932-0@av,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:14.921626Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:21.505531864Z
"2019-05-28T16:39:17.938738Z 2 [Warning] Timeout waiting for reply of binlog (file: mysql-bin.000021, pos: 479), semi-sync up to file , position 0.",s=45471ca64e5d41ba8e617e8a1780d267;i=42c7d3;b=b59693f07e96460799643fad0cd0fe81;m=fb70b9c28d;t=589f54e580b35;x=56a6720d3375b054-0@a1,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:17.938997Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:24.341155485Z
2019-05-28T16:39:17.939611Z 2 [Note] Semi-sync replication switched OFF.,s=45471ca64e5d41ba8e617e8a1780d267;i=42c7d3;b=b59693f07e96460799643fad0cd0fe81;m=fb70b9c28d;t=589f54e580b35;x=56a6720d3375b054-0@a2,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-28T16:39:17.940340Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-28T16:39:24.341155485Z
2019-05-29T15:22:47.304818Z 7226 [Note] Aborted connection 7226 to db: 'unconnected' user: 'root' host: '35.243.138.86' (Got an error reading communication packets),s=45471ca64e5d41ba8e617e8a1780d267;i=440935;b=b59693f07e96460799643fad0cd0fe81;m=10e7cf19faa;t=58a085a8fe852;x=e32ae4dc3a0f585f-0@a1,cloudsql_database,galvanic-ward-235617,galvanic-ward-235617:ontimeserver01,us-central,2019-05-29T15:22:47.305298Z,ERROR,projects/galvanic-ward-235617/logs/cloudsql.googleapis.com%2Fmysql.err,2019-05-29T15:22:52.601869056Z
I am seeing a number of timeout errors from our external web application (a Question2Answer site). The errors are attached and I've tried the following items already.

Added 4 database flags related to timeouts
Verified that my user has full resource access using SequelPro client
Verified that my user can create tables, etc from the SequelPro client
Enabled access to the IP address associated with the website and an IP address found in the logs
Researched the various connection issues associated with mysql
Confirmed that I can use an alternate mysql db connection from the web application
Verified that the instance public IP accessibility is configured and working
Noted that some additional error messages appear in the logs and attached

I am hoping someone can provide additional insight on how to resolve the connectivity issue from my networksolutions hosted website to my GCS instance.


Thanks in advance,
Tom

--
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/f3591a07-4c20-4a78-b71e-08b109b2cf70%40googlegroups.com.

[google-cloud-sql-discuss] Unable to use "Serverless VPC Access" across regions, but works within same region

Hello,

I'm running into the below and wanted to see if this is a known issue. According to this doc, "a connector can be in a different region than the resource it is sending traffic to", but I'm so far unable to accomplish this. Certainly possible I'm doing something wrong here of course. Here's my setup:

Fails with socket timeout:
Cloud Function (Java) in us-central1 -> serverless VPC connector in us-central1 -> internal IP of Cloud SQL (postgres 11) in us-west1-b

Works fine:
Cloud Function (Java) in us-central1 -> serverless VPC connector in us-central1 -> internal IP of Cloud SQL (postgres 11) in us-central1-a

I'm using the same connector in both of the above scenarios, and the SQL instance should be configured the same way as well, using the default VPC. The connector's ip-range is10.10.0.0/28. Wondering if there is a routing issue between 10.10.0.0/28 (us-central connector) and the default network in us-west1 where SQL resides? I have not changed or added any routes. Also, I don't see any firewall rules blocking here.

Any help appreciated!

VPC_networks.png

Hans

--
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/75c25b52-2626-4c01-83bb-fbf608546b3a%40googlegroups.com.

Re: [google-cloud-sql-discuss] Re: Cloud Functions -> Cloud SQL via Socket Factory too slow

Hello Hans,

It seems that Kurtis has submitted an open issue on your behalf for this in the 'cloud-sql-jdbc-socket-factory' GitHub repository. I'd suggest to add any relevant information and findings you might have gathered from your specific use cases in that thread as well.

On Monday, May 27, 2019 at 11:37:25 PM UTC-4, Hans Ravnaas wrote:
Hi, Kurtis

Thanks for the suggestion. I did try that on Friday, and even though the log showed the setting took effect, it didn't change things for the better.

Sent from my iPhone

On May 27, 2019, at 4:51 PM, 'Kurtis Van Gent' via Google Cloud SQL discuss <google-cloud-sql-discuss@googlegroups.com> wrote:

Hey Hans,

That is much higher latency than I would expect to see with the socket factory. 

In the meantime, you can try setting the env var `CLOUD_SQL_FORCE_UNIX_SOCKET=true` to see if that improves the situation. This takes advantage of the `/clousql` unix socket that is provided to functions environments. 

Please let me know if that works for you.

Thanks,
Kurtis

On Sunday, May 26, 2019 at 11:37:18 AM UTC-7, Hans Ravnaas wrote:
    So I'm connecting from Cloud Functions for Java in us-central1 to Cloud SQL (postgres 11) in us-west1 using the socket factory approach ('com.google.cloud.sql:postgres-socket-factory:1.0.13'). Everything works, but it takes around ~10 seconds to first obtain the connection, which is the problem. I am spanning two locations, but I didn't think it'd make that much of a difference. Here are the key log entries and the amount of time each one takes. Is this inline with what everyone else is seeing too? I haven't tried creating my own client cert yet but was hoping to avoid managing that.
    • 6 ms:  INFO: Connecting to Cloud SQL instance [projectid:us-west1:instancename] via SSL socket.
    • 7 sec: INFO: First Cloud SQL connection, generating RSA key pair
    • 3 sec: INFO: Obtaining ephemeral certificate for Cloud SQL instance [projectid:us-west1:instancename]...
    • 1 sec: INFO: Connecting to Cloud SQL instance [projectid:us-west1:instancename] on IP [public ip].
    Any insight appreciated.
    Hans

    --
    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/85386faa-3a78-4d0a-905c-6019145f55cf%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/d27aa0a5-f403-453d-9bb2-c58c4f4f1fbd%40googlegroups.com.

    Tuesday, May 28, 2019

    [google-cloud-sql-discuss] Re: Cloud sql mysql event cannot be deleted



    徐弘宇於2019年5月28日星期二UTC + 8下午9時17分51秒寫道:
    Cloud sql啟用了event_scheduler。
    我在mysql事件中添加了一個新的,但我無法刪除它。

    拒絕訪問; 您需要(至少一個)SUPER權限才能執行此操作。

    我該如何刪除此事件?

    Sorry, I made a stupid mistake.
    I found a solution, I went to the mysql db event delete:

    The correct process should not be removed in the default mysql db event.

    Thank you for your assistance. 

    --
    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/f44174c4-e695-4917-81f5-0e91c20e6e28%40googlegroups.com.

    [google-cloud-sql-discuss] Re: Cloud sql mysql event cannot be deleted

    You are able to enable the flag on your instance, however, there are some restrictions or unsupported feature on some activity that only Super Users (backend) have access to and therefore you might get the same error you are encountering now.

    In addition, what might have happened here, is that the privileges of root was revoked and to grant root privileges, could you try to run the command below in your Cloud SQL instance and try again:

    - GRANT ALL PRIVILEGES ON *.* TO 'root'@'%' WITH GRANT OPTION;

    Please note that Google Groups is reserved for general product discussions and is not for technical support. If the issue persists, I would suggest to post a detailed description of the issue and post it on Stackoverflow, as experienced programmers are within reach and ready to 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/438acb0a-ec5f-405c-866d-887d786c942b%40googlegroups.com.

    [google-cloud-sql-discuss] Re: App Engine phpmyadmin cannot connect to my Cloud SQL instance

    Hey KS,

    Just as an FYI, you can grant your Serverless Environments access to a VPC with the Serverless VPC Connector (in beta).

    Thanks,
    Kurtis

    On Sunday, May 26, 2019 at 11:37:18 AM UTC-7, K S wrote:
    I've found the solution: I had to enable the Public IP Address from Connection tab.
    I still don't understand why I have to enable public IP address, when I want to connect between Cloud SQL and App Engine; they're all GCP services. I didn't have to enable Public IP address to connect Cloud SQL from my Compute Engine.
    My Cloud SQL service is now ping-able, which makes me nervous too.

    On Tuesday, May 21, 2019 at 9:45:37 AM UTC-7, K S wrote:
    Here's the tutorial I've followed:
    https://cloud.google.com/sql/docs/mysql/phpmyadmin-on-app-engine

    Once I deploy, I see the phpmyadmin index page, asking for me to log in. When I try, I get following messages:
    Cannot log in to the MySQL server

    mysqli_real_connect
    (): MySQL server has gone away
    mysqli_real_connect
    (): Error while reading greeting packet. PID=-1
    mysqli_real_connect
    (): (HY000/2006): MySQL server has gone away



    this is what I used for my instance name
    myprojectID:us-west1:mycloudsqlname

    I can't figure out what I'm doing wrong. I tried the both version on the doc and the latest doc.
    I tried to allow unsecure connections for Cloud SQL, didn't work.
    App Engine authorization under "Connections" tab is checked greed - Apps in this project: All authorized.
    I'm only using Private IP address, associated with "default" network setting.
    Nothing on logs.

    Can someone confirm that the tutorial above is working?
    Any help would be 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/c9b774e2-b421-4433-bb2f-413324100977%40googlegroups.com.

    Monday, May 27, 2019

    [google-cloud-sql-discuss] Cloud sql mysql event cannot be deleted

    Cloud sql has event_scheduler enabled.
    I added a new one to the mysql event, but I can't delete it.

    Deny access; you need (at least one) SUPER permission for this operation.

    How can I delete this incident?

    --
    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/69158526-eb2c-4e27-8cfe-36da7d37dd00%40googlegroups.com.

    Re: [google-cloud-sql-discuss] Re: How to get MySQL slow query log in its 'native' format from a Cloud SQL instance?

    It seems you have successfully filed a Feature Request for this here. Additionally, I can see that it has been processed and sent to the Cloud SQL engineering team for investigation. 

    All further updates regarding this issue will occur there. Currently, there is no ETA mentioned by the team.

    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/453d023f-2341-4d3c-bbb2-a7286386e24c%40googlegroups.com.

    Re: [google-cloud-sql-discuss] Re: Cloud Functions -> Cloud SQL via Socket Factory too slow

    Hi, Kurtis

    Thanks for the suggestion. I did try that on Friday, and even though the log showed the setting took effect, it didn't change things for the better.

    Sent from my iPhone

    On May 27, 2019, at 4:51 PM, 'Kurtis Van Gent' via Google Cloud SQL discuss <google-cloud-sql-discuss@googlegroups.com> wrote:

    Hey Hans,

    That is much higher latency than I would expect to see with the socket factory. 

    In the meantime, you can try setting the env var `CLOUD_SQL_FORCE_UNIX_SOCKET=true` to see if that improves the situation. This takes advantage of the `/clousql` unix socket that is provided to functions environments. 

    Please let me know if that works for you.

    Thanks,
    Kurtis

    On Sunday, May 26, 2019 at 11:37:18 AM UTC-7, Hans Ravnaas wrote:
      So I'm connecting from Cloud Functions for Java in us-central1 to Cloud SQL (postgres 11) in us-west1 using the socket factory approach ('com.google.cloud.sql:postgres-socket-factory:1.0.13'). Everything works, but it takes around ~10 seconds to first obtain the connection, which is the problem. I am spanning two locations, but I didn't think it'd make that much of a difference. Here are the key log entries and the amount of time each one takes. Is this inline with what everyone else is seeing too? I haven't tried creating my own client cert yet but was hoping to avoid managing that.
      • 6 ms:  INFO: Connecting to Cloud SQL instance [projectid:us-west1:instancename] via SSL socket.
      • 7 sec: INFO: First Cloud SQL connection, generating RSA key pair
      • 3 sec: INFO: Obtaining ephemeral certificate for Cloud SQL instance [projectid:us-west1:instancename]...
      • 1 sec: INFO: Connecting to Cloud SQL instance [projectid:us-west1:instancename] on IP [public ip].
      Any insight appreciated.
      Hans

      --
      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/85386faa-3a78-4d0a-905c-6019145f55cf%40googlegroups.com.

      [google-cloud-sql-discuss] Re: Cloud Functions -> Cloud SQL via Socket Factory too slow

      Hey Hans,

      That is much higher latency than I would expect to see with the socket factory. 

      In the meantime, you can try setting the env var `CLOUD_SQL_FORCE_UNIX_SOCKET=true` to see if that improves the situation. This takes advantage of the `/clousql` unix socket that is provided to functions environments. 

      Please let me know if that works for you.

      Thanks,
      Kurtis

      On Sunday, May 26, 2019 at 11:37:18 AM UTC-7, Hans Ravnaas wrote:
        So I'm connecting from Cloud Functions for Java in us-central1 to Cloud SQL (postgres 11) in us-west1 using the socket factory approach ('com.google.cloud.sql:postgres-socket-factory:1.0.13'). Everything works, but it takes around ~10 seconds to first obtain the connection, which is the problem. I am spanning two locations, but I didn't think it'd make that much of a difference. Here are the key log entries and the amount of time each one takes. Is this inline with what everyone else is seeing too? I haven't tried creating my own client cert yet but was hoping to avoid managing that.
        • 6 ms:  INFO: Connecting to Cloud SQL instance [projectid:us-west1:instancename] via SSL socket.
        • 7 sec: INFO: First Cloud SQL connection, generating RSA key pair
        • 3 sec: INFO: Obtaining ephemeral certificate for Cloud SQL instance [projectid:us-west1:instancename]...
        • 1 sec: INFO: Connecting to Cloud SQL instance [projectid:us-west1:instancename] on IP [public ip].
        Any insight appreciated.
        Hans

        --
        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/85386faa-3a78-4d0a-905c-6019145f55cf%40googlegroups.com.