Bug #92998 After finishing the backup with mysqldump, mysql crashes and restarts
Submitted: 29 Oct 2018 19:42 Modified: 31 Oct 2018 13:55
Reporter: Fernando Maia Fernando Maia Email Updates:
Status: Unsupported Impact on me:
None 
Category:MySQL Server: mysqldump Command-line Client Severity:S3 (Non-critical)
Version:8.0.13 OS:CentOS (v 7)
Assigned to: CPU Architecture:Any
Tags: crash recovery, mysqldump

[29 Oct 2018 19:42] Fernando Maia Fernando Maia
Description:
Dear, first pardon for translation / concordance errors, I'm using google translator.

After using mysqldump inside the server where the mysql server is running, mysql is automatically restarted.

Looking at the log file, I checked the following message:
2018-10-28T03: 19: 32.029174Z 0 [System] [MY-010229] [Server] Starting crash recovery ...
2018-10-28T03: 19: 32.039897Z 0 [System] [MY-010232] [Server] Crash recovery finished.

I noticed that this problem started after I upgraded the server from version 8.0.12 to version 8.0.13. Note that after updating, I ran mysql_upgrade -u root.

Thankful.

How to repeat:
1-Install the version of mysql 8.0.12.
2-Import any dump;
3-Update mysql to 8.0.13;
4-rum mysql_upgrade -u root
5-Perform backup with mysqldump using the following parameters:

mysqldump --opt --port=54235 --protocol=TCP --verbose --routines --single-transaction --quick --disable-keys --no-autocommit --create-options --comments --dump-date --triggers --add-drop-table --user=${USER} --password=${PASS} --host=127.0.0.1 --all-databases > ${FILE}
[31 Oct 2018 13:55] Sinisa Milivojevic
Hi,

You should read our 8.0 Reference Manual.

Dumping and restoring data between different 8.0 releases is not supported !!!!!

You should run new release, like 8.0.13, over previous release data, like 8.0.12, and run mysql_upgrade. Then and only then you can dump and restore data. Within the same release.
[2 Nov 2018 12:50] Sinisa Milivojevic
Small additional info ...

Fully logical dumps / restores will be soon again supported in 8.0. 

It will be  announced in the future in our WWW pages and documentation.
[5 Nov 2018 13:34] Sinisa Milivojevic
Hi,

One small addition.

We would be grateful if you could come up with a (relatively) small test case of the dump taken from 8.0.12 that fails to restore on 8.0.13.

Thanks in advance.
[14 Nov 2018 0:56] Sri BG
Same issue on my server (CentOS 7) today.
We have mysql 8.0.13 and it crashed a few times.

2018-11-14T00:34:56.926108Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2018-11-14T00:34:56.950938Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.13'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server - GPL.
2018-11-14T00:34:57.072349Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: '/var/run/mysqld/mysqlx.sock' bind-address: '0.0.0.0' port: 33060
2018-11-14T00:36:50.235341Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.13) starting as process 4103
2018-11-14T00:36:51.495682Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.13) starting as process 4148
2018-11-14T00:38:00.587727Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.13) starting as process 4304
2018-11-14T00:38:01.082521Z 0 [System] [MY-010229] [Server] Starting crash recovery...
2018-11-14T00:38:01.097812Z 0 [System] [MY-010232] [Server] Crash recovery finished.
2018-11-14T00:38:01.176186Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2018-11-14T00:38:01.200368Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.13'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server - GPL.
2018-11-14T00:38:01.314030Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: '/var/run/mysqld/mysqlx.sock' bind-address: '0.0.0.0' port: 33060
2018-11-14T00:38:16.839324Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.13) starting as process 4689
2018-11-14T00:38:18.816127Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.13) starting as process 4736
2018-11-14T00:38:19.308486Z 0 [System] [MY-010229] [Server] Starting crash recovery...
2018-11-14T00:38:19.324179Z 0 [System] [MY-010232] [Server] Crash recovery finished.
2018-11-14T00:38:19.401844Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2018-11-14T00:38:19.425341Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.13'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server - GPL.
2018-11-14T00:38:19.540343Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: '/var/run/mysqld/mysqlx.sock' bind-address: '0.0.0.0' port: 33060
[
[14 Nov 2018 12:52] Sinisa Milivojevic
Hi,

I have run 8.0.12, dumped my data and imported it in 8.0.13, without any problems. So, I can only write to you what I already wrote ...

It seems that you have not followed the upgrade procedure as described in our Reference Manual for version 8.0, most specifically the sub-chapter 2.11.1. You have to go the entire procedure described there in order to be able to upgrade successfully ....... You must follow this procedure to the letter, before adding any further comments.

If you manage to pass the entire procedure descrbied in 2.111.1, we would be grateful if you could come up with a (relatively) small, but fully repeatable, test case of the dump taken from 8.0.12 that fails to restore on 8.0.13.

Thanks in advance.
[19 Nov 2018 16:07] Sinisa Milivojevic
Hi,

We truly need a full, repeatable, test case. Plus, be sure that you follow all instructions in the chapter 2.11.1.