October 2016

Monday, October 31, 2016

[google-cloud-sql-discuss] Sql instance never restarts

I restarted my sql instance 30 minutes ago and stills "restarting" what can i do?

wen i do show processlist in mysql i see

--
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/a7973cfa-631f-485d-bb2e-2e96a3ec56f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Cannot change root password (Google Cloud SQL)

Not yet.

I am appalled by the situation.

I am with the site offline until now. 3 days.

--
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/fe696c57-270e-48b4-b6f8-a685f27f2ae0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Cannot change root password (Google Cloud SQL)

We noticed this internally and have been working to recover your database. I believe someone else on the backend team is already reaching out to you, let me know if that's incorrect.

On Monday, October 31, 2016 at 5:37:27 AM UTC-7, Great Studio wrote:

And this blog is a loop every 5 seconds.

--
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/a7b5c1d7-1ea7-489d-84fb-506797a79729%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Need sql instance un-suspended (due to billing)

My sql instance was suspended when we changed billing info. I now need it un-suspended so devs can work. What can I give you to identify the instance?

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/185956d9-fb1e-49ec-bca3-ccebf76c7682%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Cannot change root password (Google Cloud SQL)

And this blog is a loop every 5 seconds.

--
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/badabbb5-293d-4d2b-9ecb-b81df0b6c382%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Cannot change root password (Google Cloud SQL)

14:34:16.570

+ ROOT=/mysql

14:34:16.570

+ rm -f /mysql/mysql.sock.lock

14:34:16.571

+ cat /mysql/my.cnf

14:34:16.571

+ exec /usr/sbin/mysqld --defaults-file=/mysql/my.cnf

14:34:16.686

2016-10-29T22:34:16.684021Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

14:34:16.686

2016-10-29T22:34:16.684078Z 0 [Warning] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.

14:34:16.687

2016-10-29T22:34:16.684108Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.11-google-log) starting as process 1 ...

14:34:16.687

2016-10-29T22:34:16.686995Z 0 [Note] Plugin 'FEDERATED' is disabled.

14:34:16.687

2016-10-29T22:34:16.687338Z 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

14:34:16.687

2016-10-29T22:34:16.687374Z 0 [Note] InnoDB: PUNCH HOLE support not available

14:34:16.687

2016-10-29T22:34:16.687385Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

14:34:16.688

2016-10-29T22:34:16.687389Z 0 [Note] InnoDB: Uses event mutexes

14:34:16.688

2016-10-29T22:34:16.687392Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

14:34:16.688

2016-10-29T22:34:16.687395Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8

14:34:16.688

2016-10-29T22:34:16.687401Z 0 [Note] InnoDB: Using Linux native AIO

14:34:16.690

2016-10-29T22:34:16.690475Z 0 [Note] InnoDB: Number of pools: 1

14:34:16.690

2016-10-29T22:34:16.690591Z 0 [Note] InnoDB: Using CPU crc32 instructions

14:34:16.971

2016-10-29T22:34:16.971062Z 0 [Note] InnoDB: Initializing buffer pool, total size = 44G, instances = 8, chunk size = 128M

14:34:19.115

2016-10-29T22:34:19.114713Z 0 [Note] InnoDB: Completed initialization of buffer pool

14:34:19.483

2016-10-29T22:34:19.483234Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().

14:34:19.503

2016-10-29T22:34:19.503362Z 0 [Note] InnoDB: Highest supported file format is Barracuda.

14:34:19.609

2016-10-29T22:34:19.609271Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 2236257216

14:34:19.718

2016-10-29T22:34:19.718227Z 0 [Note] InnoDB: Ignoring data file './greatstudio/great_documentos.ibd' with space ID 17071, since the redo log references ./greatstudio/great_documentos.ibd with space ID 16782.

14:34:19.719

2016-10-29T22:34:19.718337Z 0 [Note] InnoDB: Ignoring data file './greatstudio/great_documentos_historico.ibd' with space ID 17101, since the redo log references ./greatstudio/great_documentos_historico.ibd with space ID 16812.

14:34:19.738

2016-10-29T22:34:19.737834Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 2241434112

14:34:19.749

2016-10-29T22:34:19.748685Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 2246676992

14:34:19.759

2016-10-29T22:34:19.759047Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 2251919872

14:34:19.788

2016-10-29T22:34:19.787690Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 2257162752

14:34:19.818

2016-10-29T22:34:19.817940Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 2262405632

14:34:19.831

2016-10-29T22:34:19.831416Z 0 [Note] InnoDB: Ignoring data file './greatstudio/gestor_mensagens_log.ibd' with space ID 17140, since the redo log references ./greatstudio/gestor_mensagens_log.ibd with space ID 17137.

14:34:19.832

2016-10-29T22:34:19.832161Z 0 [Note] InnoDB: Ignoring data file './greatstudio/gestor_mensagens_log.ibd' with space ID 17140, since the redo log references ./greatstudio/gestor_mensagens_log.ibd with space ID 17138.

14:34:19.832

2016-10-29T22:34:19.832214Z 0 [Note] InnoDB: Ignoring data file './greatstudio/gestor_mensagens_log.ibd' with space ID 17140, since the redo log references ./greatstudio/gestor_mensagens_log.ibd with space ID 17138.

14:34:19.832

2016-10-29T22:34:19.832269Z 0 [Note] InnoDB: Ignoring data file './greatstudio/gestor_mensagens_log.ibd' with space ID 17140, since the redo log references ./greatstudio/gestor_mensagens_log.ibd with space ID 17138.

14:34:19.832

2016-10-29T22:34:19.832538Z 0 [Note] InnoDB: Ignoring data file './greatstudio/gestor_mensagens_log.ibd' with space ID 17140, since the redo log references ./greatstudio/gestor_mensagens_log.ibd with space ID 17138.

14:34:19.833

2016-10-29T22:34:19.832586Z 0 [Note] InnoDB: Ignoring data file './greatstudio/gestor_mensagens_log.ibd' with space ID 17140, since the redo log references ./greatstudio/gestor_mensagens_log.ibd with space ID 17139.

14:34:19.833

2016-10-29T22:34:19.832636Z 0 [Note] InnoDB: Ignoring data file './greatstudio/gestor_mensagens_log.ibd' with space ID 17140, since the redo log references ./greatstudio/gestor_mensagens_log.ibd with space ID 17138.

14:34:19.833

2016-10-29T22:34:19.832688Z 0 [Note] InnoDB: Ignoring data file './greatstudio/gestor_mensagens_log.ibd' with space ID 17140, since the redo log references ./greatstudio/gestor_mensagens_log.ibd with space ID 17139.

14:34:19.833

2016-10-29T22:34:19.832723Z 0 [Note] InnoDB: Ignoring data file './greatstudio/gestor_mensagens_log.ibd' with space ID 17140, since the redo log references ./greatstudio/gestor_mensagens_log.ibd with space ID 17138.

14:34:19.833

2016-10-29T22:34:19.832768Z 0 [Note] InnoDB: Ignoring data file './greatstudio/gestor_mensagens_log.ibd' with space ID 17140, since the redo log references ./greatstudio/gestor_mensagens_log.ibd with space ID 17139.

14:34:19.833

2016-10-29T22:34:19.833004Z 0 [Note] InnoDB: Ignoring data file './greatstudio/gestor_mensagens_log.ibd' with space ID 17140, since the redo log references ./greatstudio/gestor_mensagens_log.ibd with space ID 17139.

14:34:19.833

2016-10-29T22:34:19.833082Z 0 [Note] InnoDB: Ignoring data file './greatstudio/gestor_mensagens_log.ibd' with space ID 17140, since the redo log references ./greatstudio/gestor_mensagens_log.ibd with space ID 17139.

14:34:19.834

2016-10-29T22:34:19.833153Z 0 [Note] InnoDB: Ignoring data file './greatstudio/gestor_mensagens_log.ibd' with space ID 17140, since the redo log references ./greatstudio/gestor_mensagens_log.ibd with space ID 17139.

14:34:19.834

2016-10-29T22:34:19.833182Z 0 [Note] InnoDB: Ignoring data file './greatstudio/#sql-ib17334-3839323182.ibd' with space ID 17140. Another data file called ./greatstudio/gestor_mensagens_log.ibd exists with the same space ID.

14:34:19.834

2016-10-29T22:34:19.833212Z 0 [Note] InnoDB: Ignoring data file './greatstudio/gestor_mensagens_log.ibd' with space ID 17140, since the redo log references ./greatstudio/gestor_mensagens_log.ibd with space ID 17139.

14:34:19.834

2016-10-29T22:34:19.833241Z 0 [Note] InnoDB: Ignoring data file './greatstudio/#sql-ib17334-3839323182.ibd' with space ID 17140. Another data file called ./greatstudio/gestor_mensagens_log.ibd exists with the same space ID.

14:34:19.885

2016-10-29T22:34:19.885086Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 2267648512

14:34:19.923

2016-10-29T22:34:19.923462Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 2272891392

14:34:19.960

2016-10-29T22:34:19.959799Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 2276022231

14:34:19.960

2016-10-29T22:34:19.960226Z 0 [Note] InnoDB: Database was not shutdown normally!

14:34:19.960

2016-10-29T22:34:19.960239Z 0 [Note] InnoDB: Starting crash recovery.

14:34:20.579

2016-10-29T22:34:20.578895Z 0 [Note] InnoDB: Starting an apply batch of log records to the database...

14:34:20.919

InnoDB: Progress in percent: 25 26 27 28 29 30 31 32 2016-10-29T22:34:20.918727Z 0 [ERROR] InnoDB: Trying to access page number 8 in space 14603, space name greatstudio/great_entradassaidas_historico, which is outside the tablespace bounds. Byte offset 0, len 16384, i/o type read. If you get this error at mysqld startup, please check that your my.cnf matches the ibdata files that you have in the MySQL server.

14:34:20.919

2016-10-29T22:34:20.918767Z 0 [ERROR] InnoDB: Server exits.

--
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/65440d14-7410-453f-9ce2-9f65a136b8ff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Cannot change root password (Google Cloud SQL)

Problem: Server in constant loop never starts and does not give access to any activity (Start, change root password, restart, backup, connect, export and replicate).

I can not do anything because he does not care.

Connect errors:
Google Compute Engine:
root@greatstudio-instancia:/var/lib/mysql# mysql -u root -p
Enter password:
mysql> connect greatstudio xxx.xxx.xxx.xxx
ERROR 2003 (HY000): Can't connect to MySQL server on 'xxx.xxx.xxx.xxx' (111)
Google Shell:
Welcome to Cloud Shell! Type "help" to get started.
alison@greatstudio-projeto:~$ gcloud beta sql connect greatstudio-sql --user=root
Whitelisting your IP for incoming connection for 1 minute...done.
Enter password:
ERROR 2003 (HY000): Can't connect to MySQL server on 'xxx.xxx.xxx.xxx' (110)

Used https://translate.google.com - I'm brazilian

--
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/43cb8749-2029-4b0f-850d-068ba1e5d5eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Sunday, October 30, 2016

[google-cloud-sql-discuss] Re: Cannot change root password (Google Cloud SQL)

If you check the operation logs for the instance under Logging -> Logs -> CloudSQL, what do they say?

On Saturday, October 29, 2016 at 12:05:32 PM UTC-4, Great Studio wrote:

Hi,

I'm using Google Cloud SQL 2nd generation instance.
I tried to change root password but I couldn't because of unknown reason.

1. Go to Access Control > Users (https://console.cloud.google.com/sql/instances/[instance_name]/access-control/users)
2. Press "Change root password" button
3. Yellow tooltip: "Operation completed with errors, check the operation log for details." is shown.

It happens on a instance, but it didn't happen on another error.

Is it a bug, or did I do something wrong?

Thanks,
Alison

--
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/507cabed-1093-447e-b81b-64091fae5b67%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Saturday, October 29, 2016

[google-cloud-sql-discuss] Cannot change root password (Google Cloud SQL)

Hi,

I'm using Google Cloud SQL 2nd generation instance.
I tried to change root password but I couldn't because of unknown reason.

1. Go to Access Control > Users (https://console.cloud.google.com/sql/instances/[instance_name]/access-control/users)
2. Press "Change root password" button
3. Yellow tooltip: "Operation completed with errors, check the operation log for details." is shown.

It happens on a instance, but it didn't happen on another error.

Is it a bug, or did I do something wrong?

Thanks,

Alison

--
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/e27b1bb9-c57a-4e66-bfce-e98c446cf05c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Cannot connect to Cloud SQL 2nd generation

Hi,

I think Google Cloud SQL 2nd generation is inaccessible now.

I tried to connect from GCE instances to Cloud SQL via Cloud SQL Proxy, but I cannot connect.
This happened when I restarted Cloud SQL instance (with changing instance spec) at about June 11, 15:00 UTC (June 12, 00:00 JST).

I updated my.cnf variables and machine specs for several times, and just restarted instance for several times.
It takes so long (5 - 10 mins) to complete restart. I viewed Stackdriver logging page [ https://console.cloud.google.com/logs ] and saw ton of warnings.
In the operations tab [ https://console.cloud.google.com/sql/instances/INSTANCE_NAME/operations ], there are several "An unknown error occurred" logs on restart and update.

Next, I gave up to continue with Google Cloud SQL and get back to our old server instance which is hosted by another cloud vendor.
To keep data, I tried to export current data with export button in the overview page of Cloud SQL instance [ https://console.cloud.google.com/sql/instances/INSTANCE_NAME/overview ]

I saved it in SQL format, but the file is 0 byte and empty.

In the operation page, I found following error message:
mysqldump: Got error: 2002: Can't connect to local MySQL server through socket '/mysql/mysql.sock' (111) when trying to connect

Thanks in advance.

Alison

--
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/baa48e36-bc9a-4d0e-8172-6b7658a69dcb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Friday, October 28, 2016

[google-cloud-sql-discuss] unable to connect to cloud sql instance after deploying

Hi,

I just deployed my app. I am not sure why I am unable to connect to the socket for the cloudsqlproxy. Here is my log:

2016-10-28 18:48:11 default[20161028t222353] > start /app

2016-10-28 18:48:11 default[20161028t222353] > node app.js

2016-10-28 18:48:11 default[20161028t222353]

2016-10-28 18:48:20 default[20161028t222353] 2016/10/28 18:48:20 listenInstance: "santex-1101:asia-east1:santexdb"

2016-10-28 18:48:20 default[20161028t222353] 2016/10/28 18:48:20 Remove("/cloudsql/santex-1101:asia-east1:santexdb") error: remove /cloudsql/santex-1101:asia-east1:santexdb: no such file or directory

2016-10-28 18:48:20 default[20161028t222353] 2016/10/28 18:48:20 Open socket for "santex-1101:asia-east1:santexdb" at "/cloudsql/santex-1101:asia-east1:santexdb"

2016-10-28 18:48:20 default[20161028t222353] 2016/10/28 18:48:20 Socket prefix: /cloudsql

2016-10-28 18:48:22 default[20161028t222353] this module is main

2016-10-28 18:48:22 default[20161028t222353] server on at port 8080

2016-10-28 18:48:22 default[20161028t222353] server on at port 3333

2016-10-28 18:48:22 default[20161028t222353] read : admin.html

2016-10-28 18:48:22 default[20161028t222353] read : index.html

2016-10-28 18:48:22 default[20161028t222353] read : admin.css

2016-10-28 18:48:22 default[20161028t222353] read : admin.js

2016-10-28 18:48:22 default[20161028t222353] read : index.css

2016-10-28 18:48:22 default[20161028t222353] read : index.js

2016-10-28 18:48:23 default[20161028t222353] bucket exists

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/fb427766-fafe-47ac-b85a-3a57fb5c868d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: cannot unsuspend suspended cloud sql instances

Hi there,

Be sure to give at least a time frame of 24 hours to see the changes to your billing account propagate to your Cloud SQL instances.

In the meantime, you could try going to the Developer's Console -> 'SQL' -> <instance name> and restart the desired instance or alternatively, export the data from your suspended instance. More information about importing and exporting data can be found on this link.

Note that his type of question is more appropriate for Public Issue Tracker as it would require further steps to investigate your Cloud SQL instances. Make sure to fill in this form with the required information highlighting the problem if it persists after the 24 hour time frame.

--
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/5b71c460-4daa-4e1d-b181-cee613484237%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] cannot unsuspend suspended cloud sql instances

My cloud sql instances were suspended due to a billing issue (end of free trial). I have already made a new billing account, and added the project to it. However my instances are still suspended. I'm able to make a new instance, but I would like to get my data from the suspended instances. I noticed in this discussion group that other people had similar problems.

Instance name: actriskregister-prod:europe-west1

--
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/96e042c0-4009-4ab9-bc66-1fc64cee15f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Monday, October 24, 2016

Re: [google-cloud-sql-discuss] Mysql Proxy unable to connect Two instances

Use a comma instead of semicolon to separate the instances in the instances list.

On Mon, Oct 24, 2016 at 6:53 AM Pabanas Ashok <pabanasashok@gmail.com> wrote:

I am using Google Cloud Sql Proxy to connect two Mysql Instance rsco1617 & aimsadmin Google Cloud Mysql like this .

cloud_sql_proxy_x64 -instances=hypnotic-pier-147101:asia-east1:rsco1617;hypnotic-pier-147101:asia-east1:aimsadmin=tcp:3306 -credential_file="My First Project-13f775139ca0.json"

If any one Instance is given the above statement no issues and works fine .
But when both Instances ( rsco1617, aimsadmin) are given i get the following error
Error 403: The client is not authorized to make this request., notAuthorized like this .

I have enabled api and created Json authorization for the project .

couldn't connect to "hypnotic-pier-147101:asia-east1:rsco1617;hypnotic-pier-147101:asia-east1:aimsadmin": ensure that the account has access to "hypnotic-pier-147101:asia-east1:rsco1617;hypnotic-pier-147101:asia-east1:aimsadmin" (and make sure there's no typo in that name). Error during createEphemeral for hypnotic-pier-147101:asia-east1:rsco1617;hypnotic-pier-147101:asia-east1:aimsadmin: googleapi: Error 403: The client is not authorized to make this request., notAuthorized

Pls 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/4a718b64-df4c-427d-ae1e-1f3b3fc52dc9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/CABDU3p3cTxwpEddqoaDtFMDL44LZH_nUXVdstS66%2BgGR8J_Y6Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Mysql Proxy unable to connect Two instances

I am using Google Cloud Sql Proxy to connect two Mysql Instance rsco1617 & aimsadmin Google Cloud Mysql like this .

cloud_sql_proxy_x64 -instances=hypnotic-pier-147101:asia-east1:rsco1617;hypnotic-pier-147101:asia-east1:aimsadmin=tcp:3306 -credential_file="My First Project-13f775139ca0.json"

If any one Instance is given the above statement no issues and works fine .

But when both Instances ( rsco1617, aimsadmin) are given i get the following error

Error 403: The client is not authorized to make this request., notAuthorized like this .

I have enabled api and created Json authorization for the project .

couldn't connect to "hypnotic-pier-147101:asia-east1:rsco1617;hypnotic-pier-147101:asia-east1:aimsadmin": ensure that the account has access to "hypnotic-pier-147101:asia-east1:rsco1617;hypnotic-pier-147101:asia-east1:aimsadmin" (and make sure there's no typo in that name). Error during createEphemeral for hypnotic-pier-147101:asia-east1:rsco1617;hypnotic-pier-147101:asia-east1:aimsadmin: googleapi: Error 403: The client is not authorized to make this request., notAuthorized

Pls 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/4a718b64-df4c-427d-ae1e-1f3b3fc52dc9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Sunday, October 23, 2016

[google-cloud-sql-discuss] Re: Issues connecting to Google Cloud SQL for wordpress

If you're using a second-gen Cloud SQL instance, you need to include the full instance connection name (including region), e.g. your-project-name:us-central1:wordpress, as well as the root password for your Cloud SQL instance. That worked for me...

On Saturday, January 23, 2016 at 7:23:26 PM UTC-8, NP wrote:

I'm trying to host a wordpress blog on google app engine (GAE). I am following the steps outlined on the link below
http://googlecloudplatform.github.io/appengine-php-wordpress-starter-project/
I have created my project, deployed it, created an SQL instance and also created a database using the steps outlined in the link above (Note: I can't see the databases directly on Google Cloud SQL but when I query it from my console, I can see it).
One of the steps in the link above says to navigate to http://.appspot.com/wp-admin/install.php
When I do that, I get the following error
Error establishing a database connection  This either means that the username and password information in your wp-config.php file is incorrect or we can't contact the database server at :/cloudsql/<PROJECT_ID>:production. This could mean your host's database server is down.
Please note that 'production' is my SQL instance name. I had earlier tried 'wordpress' as recommended in the starter-project but deleted it when i had issues and I'm unable to reuse it.
I also noticed that the Google Cloud SQl window has the following entry
Instance connection name     <PROJECT_ID>:us-central1:production
i.e. it automatically appended the location to my project id and instance name. So I tried using that in my config.php file in the place where it said to use ':/cloudsql/your-project-id:your-instance-name' but that still doesn't solve the problem.
Anybody have a solution?

--
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/da66ddcc-ea7e-40e2-8dec-b03f97909476%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Wednesday, October 19, 2016

Re: [google-cloud-sql-discuss] Re: DB_HOST

Hi again,

Thanks for providing details about your environment. Still, I was unable to reproduce your error using a similar setup to yours, mainly consisting of a WordPress website hosted on Compute Engine and linked to a MySQL database on Cloud SQL.

For the reproduction, I used the Cloud Launcher to launch a WordPress solution. After importing a "dump.sql" file (from MySQL database of the WordPress Solution) to a first generation Cloud SQL instance, I followed this guide to successfully connect my WordPress website to the transferred database.

Important steps to note:

1. Generate an IPv4 address on both instances(static IPv4 on GCE) and authorise the one form GCE to connect to the Cloud SQL instance.

2. Create a user account on the Cloud SQL instance under the Access Control tab and set the "Host name" to the GCE's instance static IPv4 or to "Allow any host (%)" for testing purposes.

3. Edit the wp-config.php file in the \var\www\html directory of the Wordpress site on the GCE instance with DB_HOST set to '[Cloud SQL Generated IPv4 address]', and the other variables matching your newly created user and uploaded database name on the Cloud SQL instance.

Note that you can test your Cloud SQL database connection from the GCE instance through SSH on the instance menu and running the GCloud command "mysql --host=[Cloud SQL Generated IPv4 address] --user=[Created User] --password". This way you can make sure that the uploaded database on Cloud SQL is reachable after having configured a new user, all the IPv4 addresses and authorisation steps. More information can be found on this link.

Concerning the redirect issue, it may be caused by a misconfigured Apache server and so you may want to use external tools such as this one to identify what is causing it.

Let me know if those tips help you to connect to the Cloud SQL database and if you need any additional clarification.

--
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/75ea26dd-6cf4-4e93-a10f-f30d94f28b74%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-cloud-sql-discuss] Google Cloud Second Generation Utf8Mb4 Problem

On Tue, Oct 18, 2016 at 11:41 PM, John Walker <john@chaosdevs.com> wrote:

Hey Lee S.

Quick moment of your time please.

Wondering if (character_set_client and collation_connection) can be set at the session level yet?

they've always been settable at the session level as far as I know.

Thank you,
John

On Wednesday, August 10, 2016 at 9:10:27 AM UTC-6, Lee S. wrote:

On Wed, Aug 10, 2016 at 7:58 AM, Tolga Tanrıverdi <tolgata...@gmail.com> wrote:
We are using Google Cloud Sql Second Generation with our AppEngine application. However today we've discovered some problem, we cannot insert emoji characters to our database because we cannot change some server flags to utf8mb4 character encoding.
We've changed character_set_server flag to utf8mb4 but it wasnt enough
We have to change: character_set_system character_set_client collaction_connection
The mysql docs (for 5.6 and 5.7) say "character_set_system The character set used by the server for storing identifiers. The value is always utf8." You don't need to set this one to store utf8mb4 values (if you want to use emoji for your column names, you're out of luck ;)).

The other two (character_set_client and collation_connection) can be set at the session level. I'll look into making these settable.

flags to utf8mb4 also, but second generation db is not allowing root user to change those flags. What can we do to solve this problem
Does anyone have any idea about that?
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/96ffa068-077c-4677-9aea-7a26d2f3c471%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Lee Schumacher | Software Engineer | lschu...@google.com | (650) 336-5330

--
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/29732c14-869e-4929-ae12-36eb595056b8%40googlegroups.com.

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

Lee Schumacher | Software Engineer | lschumacher@google.com | (650) 336-5330

--
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/CAOMt%3DVgGU6V_vZqKLZ73miD384OyO%3DerdtEGt39JoEBhDETWMg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Tuesday, October 18, 2016

Re: [google-cloud-sql-discuss] Google Cloud Second Generation Utf8Mb4 Problem

Hey Lee S.

Quick moment of your time please.

Wondering if (character_set_client and collation_connection) can be set at the session level yet?

Thank you,

John

On Wednesday, August 10, 2016 at 9:10:27 AM UTC-6, Lee S. wrote:

On Wed, Aug 10, 2016 at 7:58 AM, Tolga Tanrıverdi <tolgata...@gmail.com> wrote:
We are using Google Cloud Sql Second Generation with our AppEngine application. However today we've discovered some problem, we cannot insert emoji characters to our database because we cannot change some server flags to utf8mb4 character encoding.
We've changed character_set_server flag to utf8mb4 but it wasnt enough
We have to change: character_set_system character_set_client collaction_connection
The mysql docs (for 5.6 and 5.7) say "character_set_system The character set used by the server for storing identifiers. The value is always utf8." You don't need to set this one to store utf8mb4 values (if you want to use emoji for your column names, you're out of luck ;)).

The other two (character_set_client and collation_connection) can be set at the session level. I'll look into making these settable.

flags to utf8mb4 also, but second generation db is not allowing root user to change those flags. What can we do to solve this problem
Does anyone have any idea about that?
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/96ffa068-077c-4677-9aea-7a26d2f3c471%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Lee Schumacher | Software Engineer | lschu...@google.com | (650) 336-5330

--
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/29732c14-869e-4929-ae12-36eb595056b8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Monday, October 17, 2016

Re: [google-cloud-sql-discuss] Re: DB_HOST

thanks for your reply.

i have already authorised my ip hence i dont get the 'error contacting to database'

it's not a appengine project but a compute engine

please note my answers below;

- first gen cloud sql

- hosted on compute engine

- cloud sql ip = 173.194.81.232

- mysql 5.6

On 18 October 2016 at 07:21, 'Alex (Cloud Platform Support)' via Google Cloud SQL discuss <google-cloud-sql-discuss@googlegroups.com> wrote:

Hi Salim,

Depending on your environment, you have several options available to you in the following link for connecting to your Cloud SQL instance. As in the subsection "Configure access to your Cloud SQL instance", you may have to authorise the IP address of the client machine where your MySQL client is installed.

To answer your question about setting up the DB_HOST variable, again depending on your environment(Wordpress site hosted on Google App Engine) you may be able to fix your redirect issue by setting it to ':/cloudsql/[YOUR_PROJECT_ID]:[Instance Region]:[Instance name]' as in the following "Setting up the WordPress project" link.

Alternatively, it is possible that the redirect can be caused by a plugin within the Wordpress environment. In that case, the best remedial action is to test each plugin individually after disabling them all.

In case none of the previous solutions works, please provide the following information about your set up:
- The generation of the Cloud SQL instance that you are using
- Where you are hosting your Wordpress Site
- The exact value of the DB_HOST that you have set
- Which version of MySQL are you using

Let me know if you're able to resolve it and share your setup infos if need more help with connecting to the Cloud SQL instance.

On Monday, October 17, 2016 at 9:45:43 AM UTC-4, Salim Karim wrote:
hi,

i am trying to run Wordpress with Cloud SQL.

I need to know what the DB_HOST should say?

currently it is set to the IP of Cloud SQL but I get 'redirected you too many times.'

P: (03) 9866 7737
E: info@itfutures.edu.au
A: 424 St Kilda Rd, Melbourne, 3004



Did you receive      service?
Feel free to leave a Google Review
Not Happy? Please contact our CEO

Connect with us:



Please consider the environment before printing this email.

This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential, may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of National Training and Solutions Provider Pty Ltd ABN 34 123 831 023, or any of its related entities. NTSP does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication.

--
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/ad50845f-ebb4-4033-8656-01223eb16ec5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Salim Karim

General Manager

salim@itfutures.edu.au

ext. 14

P: (03) 9866 7737

E: info@itfutures.edu.au

A: 424 St Kilda Rd, Melbourne, 3004

Did you receive

service?

Feel free to leave a Google Review

Not Happy? Please contact our CEO

Connect with us:

Please consider the environment before printing this email.

This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential, may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of National Training and Solutions Provider Pty Ltd ABN 34 123 831 023, or any of its related entities. NTSP does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication.

--
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/CAK9u%2BjmkLw6zkMyWctWHGbVCxtPDbYJTBvcdBpDrv56CizqMNw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: DB_HOST

Hi Salim,

Depending on your environment, you have several options available to you in the following link for connecting to your Cloud SQL instance. As in the subsection "Configure access to your Cloud SQL instance", you may have to authorise the IP address of the client machine where your MySQL client is installed.

To answer your question about setting up the DB_HOST variable, again depending on your environment(Wordpress site hosted on Google App Engine) you may be able to fix your redirect issue by setting it to ':/cloudsql/[YOUR_PROJECT_ID]:[Instance Region]:[Instance name]' as in the following "Setting up the WordPress project" link.

Alternatively, it is possible that the redirect can be caused by a plugin within the Wordpress environment. In that case, the best remedial action is to test each plugin individually after disabling them all.

In case none of the previous solutions works, please provide the following information about your set up:

- The generation of the Cloud SQL instance that you are using

- Where you are hosting your Wordpress Site

- The exact value of the DB_HOST that you have set

- Which version of MySQL are you using

Let me know if you're able to resolve it and share your setup infos if need more help with connecting to the Cloud SQL instance.

On Monday, October 17, 2016 at 9:45:43 AM UTC-4, Salim Karim wrote:

hi,

i am trying to run Wordpress with Cloud SQL.

I need to know what the DB_HOST should say?

currently it is set to the IP of Cloud SQL but I get 'redirected you too many times.'

P: (03) 9866 7737
E: info@itfutures.edu.au
A: 424 St Kilda Rd, Melbourne, 3004



Did you receive      service?
Feel free to leave a Google Review
Not Happy? Please contact our CEO

Connect with us:



Please consider the environment before printing this email.

This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential, may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of National Training and Solutions Provider Pty Ltd ABN 34 123 831 023, or any of its related entities. NTSP does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication.