From nobody Mon Apr 17 12:32:01 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 4Q0RJM5Vt1z45q2J for ; Mon, 17 Apr 2023 12:32:03 +0000 (UTC) (envelope-from johnl@iecc.com) Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "gal.iecc.com", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q0RJM06Htz3k2l for ; Mon, 17 Apr 2023 12:32:02 +0000 (UTC) (envelope-from johnl@iecc.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=iecc.com header.s=1835d.643d3c41.k2304 header.b=s8ZN4DuP; spf=pass (mx1.freebsd.org: domain of johnl@iecc.com designates 2001:470:1f07:1126:0:43:6f73:7461 as permitted sender) smtp.mailfrom=johnl@iecc.com; dmarc=pass (policy=none) header.from=iecc.com Received: (qmail 99167 invoked by uid 100); 17 Apr 2023 12:32:01 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:cleverness; s=1835d.643d3c41.k2304; i=johnl@user.iecc.com; bh=uoIK9Af5ZyTBPSoxHc2w3ntUQf0Hgs4+T7Yy61NPfmg=; b=s8ZN4DuPWCR13WHX7lIz43c9bIkat8jwi3zMGST4n1QdSJpQON8NDgGjT64bXQshtnO6B7DXQYf4KqLgle9kpvWvTCQQrSYBaGMJDCFwdYN682zY4LaOXJ5iokcLacIEtZExwKxkwRWP82OSkMCLpfRyVtHv4PzU4u08hKfFrJfvnLbxNDzrKot8PjhC482qv+QiJsBoSCBmwV29SXY6rRI6hg6QwUeM+hzpOk58L5W0ATvS6uNE0vygyU4bfjGsWkeUb0eK6zSTalrQhIbn45v/UuJukY1BoqvuxtNKI0X1UG+Kp8jhPBYKL8KLpTxBXK31ZOnHA0QfYaWpQWYoyg== Date: 17 Apr 2023 08:32:01 -0400 Message-ID: <7be4c94a-f0d8-5fa2-587e-243a556f8029@iecc.com> From: "John Levine" To: freebsd-questions@freebsd.org Subject: Re: mysql8.0 upgrade crashes Cleverness: None detected 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/mixed; boundary="3168237118-1876648340-1681734721=:98456" X-Spamd-Result: default: False [-3.70 / 15.00]; FAKE_REPLY(1.00)[]; CTYPE_MIXED_BOGUS(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[iecc.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; DMARC_POLICY_ALLOW(-0.50)[iecc.com,none]; RCVD_IN_DNSWL_MED(-0.20)[2001:470:1f07:1126:0:43:6f73:7461:from]; R_SPF_ALLOW(-0.20)[+ip6:2001:470:1f07:1126::/64]; R_DKIM_ALLOW(-0.20)[iecc.com:s=1835d.643d3c41.k2304]; MIME_GOOD(-0.10)[multipart/mixed,text/plain]; MLMMJ_DEST(0.00)[freebsd-questions@freebsd.org]; RCVD_COUNT_ZERO(0.00)[0]; MIME_TRACE(0.00)[0:+,1:+]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[iecc.com:+]; FROM_HAS_DN(0.00)[]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4Q0RJM06Htz3k2l X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --3168237118-1876648340-1681734721=:98456 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE I have done the 5.7 to 8.0 upgrade on other systems without trouble, and th= e MySQL docs explain how to do it. Of course I do a zfs snapshot before th= e upgrade, but it normally works. Something is strange here but I do not kn= ow what. Please consider the environment before reading this message. John Levine, johnl@taugh.com > On Apr 17, 2023, at 02:33, Dan Mahoney wrote: > > =EF=BB=BF > >> On Apr 16, 2023, at 8:12 PM, John Levine wrote: >> >> I'm trying to upgrade my fbsd 13.1 system from MySQL 5.7 to 8.0. So I >> shut down 5.7 cleanly, install the 8.0 package, start if up, and it >> consistently crashes somwehere in the upgrade process. I don't think >> there is anything very odd about my setup other than perhaps I set it >> to put each innodb database in a separate directory. >> >> I realize I could dump everything, install 8.0 from scratch, and >> restore it all, but I have a lot of databases and that would be >> painful so it would be really nice if I could get the upgrade to work. >> >> R's, >> John > > In the postgres world, we=E2=80=99re used to getting warnings from pkg ab= out having to do a full dump and restore every time we make a major version= jump. Maybe that=E2=80=99s advised here. > > -Dan > >> >> 2023-04-16T18:46:12.6NZ mysqld_safe Logging to '/var/mysql/gal.iecc.com.= err'. >> 2023-04-16T18:46:12.6NZ mysqld_safe Starting mysqld daemon with database= s from /var/mysql >> 2023-04-16T18:46:12.933341Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DA= TE', '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 re= lease. >> 2023-04-16T18:46:12.936708Z 0 [System] [MY-010116] [Server] /usr/local/l= ibexec/mysqld (mysqld 8.0.32) starting as process 18731 >> 2023-04-16T18:46:12.961932Z 1 [System] [MY-011012] [Server] Starting upg= rade of data directory. >> 2023-04-16T18:46:12.962004Z 1 [System] [MY-013576] [InnoDB] InnoDB initi= alization has started. >> 2023-04-16T18:46:24.136645Z 1 [System] [MY-013577] [InnoDB] InnoDB initi= alization has ended. >> 2023-04-16T18:46:28Z UTC - mysqld got signal 11 ; >> Most likely, you have hit a bug, but this error can also be caused by ma= lfunctioning hardware. >> Thread pointer: 0x81715e800 >> Attempting backtrace. You can use the following information to find out >> where mysqld died. If you see no messages after this, something went >> terribly wrong... >> [0x2371c88] +0x0 >> [0x2371dcb] +0x0 >> [0x8036d3580] _pthread_sigmask+0x540 >> [0x8036d2b3f] _pthread_setschedparam+0x82f >> [0x7ffffffff2d3] +0x82f >> [0x30aa132] +0x82f >> [0x30a8a8d] +0x82f >> [0x2f73f62] +0x82f >> [0x30b1bd9] +0x82f >> [0x2ed1107] +0x82f >> [0x2ecd314] +0x82f >> [0x2ecdf04] +0x82f >> [0x2ec8128] +0x82f >> [0x1fc4ba5] +0x82f >> [0x330b322] +0x82f >> [0x8036c983a] _pthread_create+0x8ca >> [0x0] +0x8ca >> stack_bottom =3D 7fffdc0dceb8 thread_stack 0x100000 >> 0x2ef49be <_Z19my_print_stacktracePKhm+0x10e> at /usr/local/libexec/mysq= ld >> 0x2371c88 <_Z18print_fatal_signali+0x268> at /usr/local/libexec/mysqld >> 0x2371dcb at /usr/local/libexec/mysqld >> 0x8036d3580 at /lib/libthr.so.3 >> 0x8036d2b3f at /lib/libthr.so.3 >> 0x7ffffffff2d3 at ??? >> 0x30aa132 <_Z15dict_load_tablePKcb17dict_err_ignore_tPKNSt3__112basic_st= ringIcNS2_11char_traitsIcEENS2_9allocatorIcEEEE+0x17c2> at /usr/local/libex= ec/mysqld >> 0x30a8a8d <_Z15dict_load_tablePKcb17dict_err_ignore_tPKNSt3__112basic_st= ringIcNS2_11char_traitsIcEENS2_9allocatorIcEEEE+0x11d> at /usr/local/libexe= c/mysqld >> 0x2f73f62 <_Z23dict_table_open_on_namePKcbb17dict_err_ignore_t+0x272> at= /usr/local/libexec/mysqld >> 0x30b1bd9 <_Z16dd_upgrade_tableP3THDPKcS2_PN2dd5TableEP5TABLE+0x129> at = /usr/local/libexec/mysqld >> 0x2ed1107 <_ZN20malloc_unordered_setINSt3__112basic_stringIcNS0_11char_t= raitsIcEENS0_9allocatorIcEEEENS0_4hashIS6_EENS0_8equal_toIS6_EEEC2Ej+0x7c7>= at /usr/local/libexec/mysqld >> 0x2ecd314 <_ZN2dd10upgrade_5726migrate_plugin_table_to_ddEP3THD+0x2554> = at /usr/local/libexec/mysqld >> 0x2ecdf04 <_ZN2dd10upgrade_5721migrate_all_frm_to_ddEP3THDPKcb+0x7c4> at= /usr/local/libexec/mysqld >> 0x2ec8128 <_ZN2dd10upgrade_5720fill_dd_and_finalizeEP3THD+0x118> at /usr= /local/libexec/mysqld >> 0x1fc4ba5 <_ZN9bootstrap20run_bootstrap_threadEPKcP10MYSQL_FILEPFbP3THDE= 16enum_thread_type+0x5a5> at /usr/local/libexec/mysqld >> 0x330b322 <_Z19pfs_spawn_thread_vcjjP16my_thread_handlePKP12pthread_attr= PFPvS5_ES5_+0x2a2> at /usr/local/libexec/mysqld >> >> Trying to get some variables. >> Some pointers may be invalid and cause the dump to abort. >> Query (0): >> Connection ID (thread ID): 2 >> Status: NOT_KILLED >> >> The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html conta= ins >> information that should help you find out what is causing the crash. >> 2023-04-16T18:46:29.6NZ mysqld_safe mysqld from pid file /var/mysql/gal.= iecc.com.pid ended > --3168237118-1876648340-1681734721=:98456--