Mailing List ecs-isp@2rosenthals.com Archived Message #537

From: "Massimo S." <ecs-isp@2rosenthals.com> Full Headers
Undecoded message
Subject: Re: [eCS-ISP] mysql upgrade 5.1.73 -> 5.6.51 "allways recovery issue"
Date: Fri, 11 Aug 2023 13:11:11 +0200
To: eCS ISP Mailing List <ecs-isp@2rosenthals.com>



Il 10/08/2023 20:55, Massimo S. ha scritto:


Il 10/08/2023 17:15, Steven Levine ha scritto:
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.

no entries in populog, no eq dump anywhere

massimo

Hi all,

i guess this is not an important issue but each time i start mysqlD
it say that DB has not been:

2023-08-11 13:10:28 19155 [Note] InnoDB: Database was not shutdown normally!
2023-08-11 13:10:28 19155 [Note] InnoDB: Starting crash recovery.

this is not true, since i just closed mysqlD with CTRL-C


massimo

Subscribe: Feed, Digest, Index.
Unsubscribe
Mail to ListMaster