ecs-isp@2rosenthals.com Messaggio archiviato #532

Da: "Massimo S." <ecs-isp@2rosenthals.com> Intestazioni complete
Messaggio non codificato
Oggetto: Re: [eCS-ISP] mysql upgrade 5.1.73 -> 5.6.51
Data: Thu, 10 Aug 2023 11:10:24 +0200
A: eCS ISP Mailing List <ecs-isp@2rosenthals.com>



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


Il 10/08/2023 00:19, Steven Levine ha scritto:
In <list-7611426@2rosenthals.com>, on 08/09/23
    at 12:09 PM, "Massimo S." <ecs-isp@2rosenthals.com> said:

Hi all,

Here's the mysql upgrade procedure that worked for me

==============================
== mysql_upgrade 5.1 -> 5.6 ==
==============================

  - Tested with mysqld
      Ver 5.1.73 for pc-os2-emx on i386 (Source distribution)
    and
      Ver 5.6.51 for OS2 on i386 (Source distribution)

  - The following assumes
      5.6 datadir will be /data/mysql56
      5.1 datadir is /data/mysql51
      innodb_data_home_dir is /data/mysql56-data/innodb
  - Use names that match your setup

  - Open session with current directory set to 5.6 bin directory
    Run binaries from the directory

  - Verify my.cnf is 5.6 compatible
    Edit as needed to protect/hide 5.1 data

  - Create /data/mysql56
  - Create /data/mysql56/mysql
  - Create /data/mysql56/innodb
  - Copy /data/mysql51/mysql to /data/mysql56/mysql
  - Run
      mysqld --console
    The server should start
    There will be warnings
  - Run
      mysql_upgrade
    The server may crash
  - If the server crashes, run
      mysqld --console
    to restart the server
    There will be warnings
    Run
      mysql_upgrade
    to retry the upgrade
    The upgrade should run without errors
    if not get help

  - Copy the rest of the 5.1 databases to /data/mysql56
  - Run
      mysql_upgrade --force
    to upgrade these databases
    The upgrade should run without errors
    If not get help

  - Run
      mysqlcheck --all-databases
    to cross-check upgrade results

  - Check /data/mysql56/mysql_upgrade_info
    It should contain 5.6.51

The logs imply that, at least in my case, only the mysql database needed
unusual modifications.  The log output for all the other databases and
tables reported OK with no additional messages or warnings.

Steven


very good, thank you

what was making exiting my mysql --console

  ;innodb_buffer_pool_size = 512M

after commenting it the console started

i copied all the data from 5.1, than mysqlD started and got running

using mysql_upgrade --force -u myuser -pmypwd i got the upgrade running and it completed (after a crash/exit of mysqld that i had to restart)


if someone is interested in the crash/exit of mysqlD:

2023-08-10 11:06:12 45aa3e40 InnoDB: Error: Fetch of persistent statistics requested for table "mysql"."links" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.

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


massimo

Isriviti: Feed, Riassunto, Indice.
Disiscriviti
Scrivi a ListMaster