From: "Steven Levine" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTPS id 7601659 for ecs-isp@2rosenthals.com; Tue, 08 Aug 2023 02:37:55 -0400 Received: from [192.168.200.201] (port=51096 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtp (Exim 4.96) (envelope-from ) id 1qTGLo-0003gb-1V for ecs-isp@2rosenthals.com; Tue, 08 Aug 2023 02:37:52 -0400 Received: from mta-202b.earthlink-vadesecure.net ([51.81.232.241]:42395 helo=mta-202a.earthlink-vadesecure.net) by mail2.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1qTGLl-0005qt-1i for ecs-isp@2rosenthals.com; Tue, 08 Aug 2023 02:37:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; bh=VVhBqh+3xJ/rCwyGmHVvjn39HOL0YGMnegPoEb WcNYI=; c=relaxed/relaxed; d=earthlink.net; h=from:reply-to:subject: date:to:cc:resent-date:resent-from:resent-to:resent-cc:in-reply-to: references:list-id:list-help:list-unsubscribe:list-subscribe:list-post: list-owner:list-archive; q=dns/txt; s=dk12062016; t=1691476668; x=1692081468; b=l19EYwllX2laOFdoaAeL3jIrsMW8BxTTCE1mFV54gmkN3eAqcEZuT8V 7Gnjy6JWQHEqMrEwSDZho42iYg+x4kJ/Z7AW5UdLPjAVG7gY/03AeAMHE8y6Uda0mUN7Oby CkW7VXvg/gtdJqgHhufOZZs0Lb1FBkwGVG6vsvFSl/WUTXZ+xnf5c23mbD3sDk8UPdHn45c YlewKwLLAZrDWH2Tn9cCmuNAlu5ERvGH/v6PrH0MBG0ygnuhuhVhx4zO7e8DVgJeJ2D2TNG 2R+DgqjuKiXwguqgb3aaufKZRKASsEKgF2DpFpChgVh3WogqW4adWgJ+7ljQg+Llf7Jk2kS /7w== Received: from slamain ([108.193.255.150]) by vsel2nmtao02p.internal.vadesecure.com with ngmta id dc215c1b-177955115c6b5135; Tue, 08 Aug 2023 06:37:48 +0000 Message-ID: <64d1d374.2.mr2ice.fgrirsq@earthlink.net> Date: Mon, 07 Aug 2023 22:32:36 -0700 To: "eCS ISP Mailing List" In-Reply-To: Subject: Re: [eCS-ISP] mysql upgrade 5.1.73 -> 5.6.51 X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v3.00.11.24/60 In , on 08/01/23 at 01:21 PM, "Massimo S." said: >about 5.6.51 it don't start here >i'm going to open a ticket A few comments on ticket #777. I got sufficiently curious to do some local testing to see what failures might occur using my databases. I was able to trigger some failures, but not your failure. I suspect the mysql_upgrade is sensitive to the data being upgraded and v5.1 to v5.6 is a big jump, so let's backup and locate the source of the failure. Populate your v5.6 data directory tree with just the mysql subdirectory. Run mysqld --console to make sure the server will start. Then run mysql-upgrade. If this works, copy another v5.1 database to the v5.6 data directory and run mysql_upgrade --force. Repeat this until you find which database is the problem. FWIW, one of the failures I got was: 2023-08-07 23:09:11 6198 [ERROR] Incorrect definition of table mysql.proc: expected column 'comment' at position 15 to have type text, found type char(64). followed by a LIBC PANIC. I have to assume that I ran into this when I upgrade these databases to v5.6, but I did not keep notes of what I did the get past it. Most likely, I used mysql_install_db.pl to populate the mysql system tables and used mysql_upgrade for the rest. It's getting late here, so I'm done for now. Tomorrow, I will do some mysqlcheck runs to make sure the v5.1 databases have no issues. If we cannot fix your v5.1 databases to work with mysql, the alternative will be to dump and reload. I've used this method in the past when the upgrade will not cooperate. Steven -- ---------------------------------------------------------------------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------