From: "Steven Levine" <ecs-isp@2rosenthals.com>
Message-ID: <64d4ff01.15.mr2ice.fgrirsq@earthlink.net>
Date: Thu, 10 Aug 2023 08:15:13 -0700
To: "eCS ISP Mailing List" <ecs-isp@2rosenthals.com>
In-Reply-To: <list-7640765@2rosenthals.com>
Subject: Re: [eCS-ISP] mysql upgrade 5.1.73 -> 5.6.51

In <list-7640765@2rosenthals.com>, on 08/10/23
   at 11:10 AM, "Massimo S." <ecs-isp@2rosenthals.com> said:

Hi Massimo,

>if someone is interested in the crash/exit of mysqlD:

>LIBC PANIC!!
>fmutex deadlock: Recursive mutex!
>0x3c838180: Owner=0x0d8b0017 Self=0x0d8b0017 fs=0x3 flags=0x0
>hev=0x00016234
>             Desc="pthread_mutex_t"
>pid=0x0d8b ppid=0x0c9d tid=0x0017 slot=0x0097 pri=0x0200 mc=0x0000
>ps=0x0010 D:\MYSQL\BIN\MYSQLD.EXE

You have an exceptq report too.  I suspect it's similar to the one
generated here.

It turns out that I encountered the same upgrade failure back in March
which is when I upgraded these databases.  I probably retried the upgrade
and did not think too much of it when the retry worked.  This explains the
lack of useful notes.  However, my exceptq report archives include the
report for this mysql failure.

I also ran into the now expected innodb issues.  This set of databases ran
with skip-innodb and 5.6 no longer allows this.

Glad you got it working.

Steven

-- 
----------------------------------------------------------------------
"Steven Levine" <steve53@earthlink.net>  Warp/DIY/BlueLion etc.
www.scoug.com www.arcanoae.com www.warpcave.com
----------------------------------------------------------------------