Re: MySQL server silently fails to start after upgrading from 5.7.40 to 8.0.32 - RESOLVED

On Saturday, 15 April 2023 17:25:17 BST Mike Clarke wrote:

> After upgrading packages to the the new quarterly release mysql was
> upgraded to 8.0.32 and it fails to start

I restored my mysql5 version of the database and had another attempt at upgrading 
following the description in https://forums.FreeBSD.org/threads/heads-up-mysql-default-version-will-switch-to-8-0.87917/post-597122[1] but still got the error message about the 
Auto-extending innodb_system data file '/var/db/mysql/ibdata1' being a different size than 
specified in the .cnf file.

In the process I'd created a new my.cnf file by copying my.cnf.sample from the upgraded /
usr/local/etc/mysql so I edited my.cnf changing the size for innodb_data_file_path from 
the default 128M to 82M which was the value used before upgrading packages. I was then 
able to start mysql-server without any errors.

But I still see these warnings:

 2023-04-20T08:57:21.863480Z 0 [Warning] [MY-010140] [Server] Could not increase 
number of max_open_files to more than 22500 (request: 32929) 
2023-04-20T08:57:21.863487Z 0 [Warning] [MY-010142] [Server] Changed limits: 
table_open_cache: 11169 (requested 16384) 
2023-04-20T08:57:22.063255Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 
'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with 
strict mode. They will be merged with strict mode in a future release.
Do I need to do anything about them?

-- 
Mike Clarke

--------
[1] https://forums.FreeBSD.org/threads/heads-up-mysql-default-version-will-switch-to-8-0.87917/post-597122