Date: Thu, 20 Apr 2023 12:09:20 +0100 From: Mike Clarke <jmc-freebsd2@milibyte.co.uk> To: freebsd-questions@freebsd.org Subject: Re: MySQL server silently fails to start after upgrading from 5.7.40 to 8.0.32 - RESOLVED Message-ID: <3951000.p4y8TspHLy@curlew> In-Reply-To: <4381878.Iv3B0QcHgC@curlew> References: <4381878.Iv3B0QcHgC@curlew>
next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format. --nextPart2868068.SSXfckUlLJ Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" 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 --nextPart2868068.SSXfckUlLJ Content-Transfer-Encoding: 7Bit Content-Type: text/html; charset="UTF-8" <html> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> </head> <body><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">On Saturday, 15 April 2023 17:25:17 BST Mike Clarke wrote:</p> <br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> After upgrading packages to the the new quarterly release mysql was</p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> upgraded to 8.0.32 and it fails to start</p> <br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">I restored my mysql5 version of the database and had another attempt at upgrading following the description in <a href="https://forums.FreeBSD.org/threads/heads-up-mysql-default-version-will-switch-to-8-0.87917/post-597122">https://forums.FreeBSD.org/threads/heads-up-mysql-default-version-will-switch-to-8-0.87917/post-597122</a> 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.</p> <br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">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.</p> <br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">But I still see these warnings:</p> <br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"> <span style="color:#000000;"><span style="background-color:#ffffff;"><span style="font-family:monospace;">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) </span></span></span><br />2023-04-20T08:57:21.863487Z 0 [Warning] [MY-010142] [Server] Changed limits: table_open_cache: 11169 (requested 16384) <br />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.</p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">Do I need to do anything about them?</p> <br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">-- </p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">Mike Clarke</p> </body> </html> --nextPart2868068.SSXfckUlLJ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3951000.p4y8TspHLy>