MySQL won't start after upgrade 5.7 to 8.0

NLServ

New member
Joined
Sep 29, 2019
Messages
2
Hi all,

I did a update via custombuild all d to MySQL 8.0. After the update MySQL 8.0 won't start at all, all the logs seems to be empty so I can't find any explanation why MySQL wont start. On SSH it's just shows

Stopping mysqld: [ OK ]
Timeout error occurred trying to start MySQL Daemon.
Starting mysqld: [FAILED]

I tried several things but till now without success. What can I do to fix this?

Thanks in advance for all the help :).
 

NLServ

New member
Joined
Sep 29, 2019
Messages
2
In my /var/lib/mysql/hostname.err log I did found this:

2019-09-29T12:53:11.764760Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 11
2019-09-29T12:53:11.766864Z 1 [ERROR] [MY-012592] [InnoDB] Operating system error number 11 in a file operation.
2019-09-29T12:53:11.766912Z 1 [ERROR] [MY-012596] [InnoDB] Error number 11 means 'Resource temporarily unavailable'
2019-09-29T12:53:11.766979Z 1 [ERROR] [MY-012215] [InnoDB] Cannot open datafile './ibdata1'
2019-09-29T12:53:11.767023Z 1 [ERROR] [MY-012959] [InnoDB] Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2019-09-29T12:53:11.767061Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Cannot open a file.
2019-09-29T12:53:11.944024Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2019-09-29T12:53:11.944336Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2019-09-29T12:53:11.945691Z 0 [ERROR] [MY-010119] [Server] Aborting
2019-09-29T12:53:11.948359Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.17) MySQL Community Server - GPL.
2019-09-29T12:53:45.617347Z 2 [Warning] [MY-010200] [Server] Resolving dependency for the view 'auser2_datawarehouse.all_order_list_w_SKU' failed. View is no more valid to use
2019-09-29T12:53:46.528306Z 0 [ERROR] [MY-010022] [Server] Failed to Populate DD tables.
2019-09-29T12:53:46.528657Z 0 [ERROR] [MY-010119] [Server] Aborting
2019-09-29T12:53:48.311545Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.17) MySQL Community Server - GPL.
2019-09-29T12:54:02.120226Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.17) starting as process 31311
2019-09-29T12:54:02.133712Z 1 [System] [MY-011012] [Server] Starting upgrade of data directory.
2019-09-29T12:55:17.193234Z 2 [ERROR] [MY-012064] [InnoDB] Column datatype mismatch for col: latlng
2019-09-29T12:55:17.193263Z 2 [ERROR] [MY-012070] [InnoDB] Column latlng for table: `auser1_wp1`.`wp_wpgmza` mismatches with InnoDB Dictionary
2019-09-29T12:55:17.193296Z 2 [ERROR] [MY-010767] [Server] Error in fixing SE data for auser1_wp1.wp_wpgmza
2019-09-29T12:55:17.223682Z 2 [ERROR] [MY-012064] [InnoDB] Column datatype mismatch for col: center
2019-09-29T12:55:17.223701Z 2 [ERROR] [MY-012070] [InnoDB] Column center for table: `auser1_wp1`.`wp_wpgmza_circles` mismatches with InnoDB Dictionary
2019-09-29T12:55:17.223732Z 2 [ERROR] [MY-010767] [Server] Error in fixing SE data for auser1_wp1.wp_wpgmza_circles
2019-09-29T12:55:17.280781Z 2 [ERROR] [MY-012064] [InnoDB] Column datatype mismatch for col: cornerA
2019-09-29T12:55:17.280798Z 2 [ERROR] [MY-012070] [InnoDB] Column cornerA for table: `auser1_wp1`.`wp_wpgmza_rectangles` mismatches with InnoDB Dictionary
2019-09-29T12:55:17.280828Z 2 [ERROR] [MY-010767] [Server] Error in fixing SE data for auser1_wp1.wp_wpgmza_rectangles
2019-09-29T12:56:45.854785Z 2 [Warning] [MY-010200] [Server] Resolving dependency for the view 'auser2_datawarehouse.all_order_list_w_SKU' failed. View is no more valid to use
2019-09-29T12:56:46.730577Z 0 [ERROR] [MY-010022] [Server] Failed to Populate DD tables.
2019-09-29T12:56:46.730921Z 0 [ERROR] [MY-010119] [Server] Aborting
2019-09-29T12:56:48.850455Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.17) MySQL Community Server - GPL.
2019-09-29T12:57:01.814739Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.17) starting as process 32604
2019-09-29T12:57:01.829920Z 1 [System] [MY-011012] [Server] Starting upgrade of data directory.
2019-09-29T12:57:24.054069Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.17) starting as process 33022
2019-09-29T12:57:26.036458Z 1 [ERROR] [MY-011014] [Server] Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.
2019-09-29T12:57:30.266227Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2019-09-29T12:57:30.266567Z 0 [ERROR] [MY-010119] [Server] Aborting
2019-09-29T12:57:31.642047Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.17) MySQL Community Server - GPL.
 

smtalk

Administrator
Staff member
Joined
Aug 22, 2006
Messages
8,341
Location
LT, EU
Some process might be holding ibdata1 file already and MySQL is unable to read it. Please try checking the process list. If you're unable to get it running, and you run an external license, I'd suggest tickets.directadmin.com.
 

eva2000

Verified User
Joined
Jul 1, 2019
Messages
93
In my /var/lib/mysql/hostname.err log I did found this:
what OSes is is on ? centos ? looks like someone forgot to run mysql_upgrade after upgrading to mysql 8.0 ? or mysql_upgrade failed to run ? did you upgrade to mysql 5.7 from previous mysql version too ?
 
Top