Cannot change root password (Google Cloud SQL)

[Great Studio]

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

[Adam (Cloud Platform Support)]

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

[Great Studio]

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

[Great Studio]

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.

[Great Studio]

And this blog is a loop every 5 seconds.

[Kevin Malachowski]

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.

[Great Studio]

Not yet.

I am appalled by the situation.

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

[Adam (Cloud Platform Support)]

I see that support had reached out to you and were able to recover the instance. Please don't hesitate to let us know if you experience any further issues.