From nobody Thu Apr 20 11:09:20 2023 X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Q2FKt5jFwz46ftY for ; Thu, 20 Apr 2023 11:09:38 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from cp160176.hpdns.net (cp160176.hpdns.net [91.238.160.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q2FKs43xTz3wvd for ; Thu, 20 Apr 2023 11:09:37 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=milibyte.co.uk header.s=default header.b=XVTsV0Te; spf=pass (mx1.freebsd.org: domain of jmc-freebsd2@milibyte.co.uk designates 91.238.160.176 as permitted sender) smtp.mailfrom=jmc-freebsd2@milibyte.co.uk; dmarc=none DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=milibyte.co.uk; s=default; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Date:Subject:To:From:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=kyFCY525No8HhnL+WN62ot6K8RZfNEsCSfUH7JfiN+s=; b=XVTsV0TeX4QrM0awCvRpkm+kmz unTWUj5X9sJHPdbRky/VJCz0k8SI2xKHElH90Tlg359h+pENFEHAxWAB5KvbI/oY2eOvQbOz4ND4V UJJ8HTpXZqsGxuXmvCDwzTKz9vStG+tgFec87+gdRTkia8a/M9uDAPy733Pr3UpxyIGRE4vwCj9Hs c2aP9H/b+qKlTSiAy8q2AW50HOMQQUkMOsYTFaj0KJqcKdPdrxCUa/ru13EzpFzGXGos2N6+mB9CX cz3j+RVJFFrS/HiR8QlRWSa6REBToRnu1/r/xWjAFdszaEZA2UI0VaV2Iv33diLd4296nRJ5q0MiQ dlinJJOg==; Received: from [149.86.189.206] (port=22061 helo=curlew.milibyte.co.uk) by cp160176.hpdns.net with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1ppSAE-001P76-1X for freebsd-questions@freebsd.org; Thu, 20 Apr 2023 12:09:20 +0100 Received: from [127.0.0.1] (helo=curlew.localnet) by curlew.milibyte.co.uk with esmtp (Exim 4.95) (envelope-from ) id 1ppSAD-00014i-2B for freebsd-questions@freebsd.org; Thu, 20 Apr 2023 12:09:20 +0100 From: Mike Clarke To: freebsd-questions@freebsd.org Subject: Re: MySQL server silently fails to start after upgrading from 5.7.40 to 8.0.32 - RESOLVED Date: Thu, 20 Apr 2023 12:09:20 +0100 Message-ID: <3951000.p4y8TspHLy@curlew> In-Reply-To: <4381878.Iv3B0QcHgC@curlew> References: <4381878.Iv3B0QcHgC@curlew> List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="nextPart2868068.SSXfckUlLJ" Content-Transfer-Encoding: 7Bit X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: jmc-freebsd2@milibyte.co.uk X-SA-Exim-Scanned: No (on curlew.milibyte.co.uk); SAEximRunCond expanded to false X-YourOrg-MailScanner-Information: Please contact the ISP for more information X-YourOrg-MailScanner-ID: 1ppSAE-001P76-1X X-YourOrg-MailScanner: Found to be clean X-YourOrg-MailScanner-SpamCheck: X-YourOrg-MailScanner-From: jmc-freebsd2@milibyte.co.uk X-Spam-Status: No X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cp160176.hpdns.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - milibyte.co.uk X-Get-Message-Sender-Via: cp160176.hpdns.net: authenticated_id: mailpool@milibyte.co.uk X-Authenticated-Sender: cp160176.hpdns.net: mailpool@milibyte.co.uk X-Source: X-Source-Args: X-Source-Dir: X-Spamd-Result: default: False [-1.34 / 15.00]; URI_COUNT_ODD(1.00)[5]; NEURAL_HAM_SHORT(-0.99)[-0.990]; NEURAL_HAM_MEDIUM(-0.99)[-0.989]; NEURAL_HAM_LONG(-0.86)[-0.858]; CTE_CASE(0.50)[]; MID_RHS_NOT_FQDN(0.50)[]; R_DKIM_ALLOW(-0.20)[milibyte.co.uk:s=default]; R_SPF_ALLOW(-0.20)[+a]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[milibyte.co.uk]; FROM_HAS_DN(0.00)[]; HAS_X_GMSV(0.00)[mailpool@milibyte.co.uk]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-questions@freebsd.org]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_NONE(0.00)[]; HAS_X_SOURCE(0.00)[]; HAS_X_AS(0.00)[mailpool@milibyte.co.uk]; DKIM_TRACE(0.00)[milibyte.co.uk:+]; FROM_EQ_ENVFROM(0.00)[]; HAS_X_ANTIABUSE(0.00)[]; ASN(0.00)[asn:52148, ipnet:91.238.160.0/22, country:GB]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4Q2FKs43xTz3wvd X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N 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"

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 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

--nextPart2868068.SSXfckUlLJ--