From: "Massimo S." Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTPS id 7640753 for ecs-isp@2rosenthals.com; Thu, 10 Aug 2023 05:08:13 -0400 Received: from [192.168.200.201] (port=40457 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtp (Exim 4.96) (envelope-from ) id 1qU1eM-0007Mo-2T for ecs-isp@2rosenthals.com; Thu, 10 Aug 2023 05:08:11 -0400 Received: from mail2.quasarbbs.net ([80.86.52.115]:10128) by mail2.2rosenthals.com with esmtp (Exim 4.96) (envelope-from ) id 1qU1eE-0001yY-23 for ecs-isp@2rosenthals.com; Thu, 10 Aug 2023 05:08:03 -0400 X-SASI-Hits: BODY_SIZE_3000_3999 0.000000, BODY_SIZE_5000_LESS 0.000000, BODY_SIZE_7000_LESS 0.000000, CTE_8BIT 0.000000, HTML_00_01 0.050000, HTML_00_10 0.050000, IN_REP_TO 0.000000, LEGITIMATE_SIGNS 0.000000, MSGID_SAMEAS_FROM_HEX_844412 0.100000, MSG_THREAD 0.000000, NO_URI_HTTPS 0.000000, REFERENCES 0.000000, REPLYTO_SAMEAS_FROM 0.000000, SENDER_NO_AUTH 0.000000, SUSP_DH_NEG 0.000000, TO_IN_SUBJECT 0.500000, URI_ENDS_IN_HTML 0.000000, URI_WITH_PATH_ONLY 0.000000, __ANY_URI 0.000000, __BODY_NO_MAILTO 0.000000, __BOUNCE_CHALLENGE_SUBJ 0.000000, __BOUNCE_NDR_SUBJ_EXEMPT 0.000000, __CP_URI_IN_BODY 0.000000, __CT 0.000000, __CTE 0.000000, __CT_TEXT_PLAIN 0.000000, __DQ_NEG_DOMAIN 0.000000, __DQ_NEG_HEUR 0.000000, __DQ_NEG_IP 0.000000, __FORWARDED_MSG 0.000000, __FRAUD_MONEY_BIG_COIN 0.000000, __FRAUD_MONEY_BIG_COIN_DIG 0.000000, __FROM_DOMAIN_NOT_IN_BODY 0.000000, __FROM_NAME_NOT_IN_ADDR 0.000000, __FROM_NAME_NOT_IN_BODY 0.000000, __FUR_HEADER 0.000000, __HAS_FROM 0.000000, __HAS_MSGID 0.000000, __HAS_REFERENCES 0.000000, __HAS_REPLYTO 0.000000, __HEADER_ORDER_FROM 0.000000, __INVOICE_MULTILINGUAL 0.000000, __IN_REP_TO 0.000000, __MAIL_CHAIN 0.000000, __MIME_BOUND_CHARSET 0.000000, __MIME_TEXT_ONLY 0.000000, __MIME_TEXT_P 0.000000, __MIME_TEXT_P1 0.000000, __MIME_VERSION 0.000000, __MOZILLA_USER_AGENT 0.000000, __MSGID_HEX_844412 0.000000, __MULTIPLE_URI_TEXT 0.000000, __NO_HTML_TAG_RAW 0.000000, __PHISH_PHRASE1_B 0.000000, __PHISH_SPEAR_SUBJ_PREDICATE 0.000000, __REFERENCES 0.000000, __REPLYTO_SAMEAS_FROM_ACC 0.000000, __REPLYTO_SAMEAS_FROM_ADDY 0.000000, __REPLYTO_SAMEAS_FROM_DOMAIN 0.000000, __SANE_MSGID 0.000000, __SCAN_D_NEG 0.000000, __SCAN_D_NEG2 0.000000, __SCAN_D_NEG_HEUR 0.000000, __SCAN_D_NEG_HEUR2 0.000000, __SUBJ_ALPHA_NEGATE 0.000000, __SUBJ_REPLY 0.000000, __TO_IN_SUBJECT 0.000000, __TO_MALFORMED_2 0.000000, __TO_NAME 0.000000, __TO_NAME_DIFF_FROM_ACC 0.000000, __TO_REAL_NAMES 0.000000, __URI_IN_BODY 0.000000, __URI_MAILTO 0.000000, __URI_NOT_IMG 0.000000, __URI_NO_WWW 0.000000, __URI_NS 0.000000, __URI_WITH_PATH 0.000000, __USER_AGENT 0.000000 X-SASI-Probability: 10% X-SASI-RCODE: 200 X-SASI-Version: Antispam-Engine: 5.1.1, AntispamData: 2023.8.10.84217 X-SASI-Hits: BODY_SIZE_3000_3999 0.000000, BODY_SIZE_5000_LESS 0.000000, BODY_SIZE_7000_LESS 0.000000, CTE_8BIT 0.000000, HTML_00_01 0.050000, HTML_00_10 0.050000, IN_REP_TO 0.000000, LEGITIMATE_SIGNS 0.000000, MSGID_SAMEAS_FROM_HEX_844412 0.100000, MSG_THREAD 0.000000, NO_URI_HTTPS 0.000000, REFERENCES 0.000000, REPLYTO_SAMEAS_FROM 0.000000, SUSP_DH_NEG 0.000000, TO_IN_SUBJECT 0.500000, URI_ENDS_IN_HTML 0.000000, URI_WITH_PATH_ONLY 0.000000, __ANY_URI 0.000000, __AUTH_RES_PASS 0.000000, __BODY_NO_MAILTO 0.000000, __BOUNCE_CHALLENGE_SUBJ 0.000000, __BOUNCE_NDR_SUBJ_EXEMPT 0.000000, __CP_URI_IN_BODY 0.000000, __CT 0.000000, __CTE 0.000000, __CT_TEXT_PLAIN 0.000000, __DQ_NEG_DOMAIN 0.000000, __DQ_NEG_HEUR 0.000000, __DQ_NEG_IP 0.000000, __FORWARDED_MSG 0.000000, __FRAUD_MONEY_BIG_COIN 0.000000, __FRAUD_MONEY_BIG_COIN_DIG 0.000000, __FROM_DOMAIN_NOT_IN_BODY 0.000000, __FROM_NAME_NOT_IN_ADDR 0.000000, __FROM_NAME_NOT_IN_BODY 0.000000, __FUR_HEADER 0.000000, __HAS_FROM 0.000000, __HAS_MSGID 0.000000, __HAS_REFERENCES 0.000000, __HAS_REPLYTO 0.000000, __HEADER_ORDER_FROM 0.000000, __INVOICE_MULTILINGUAL 0.000000, __IN_REP_TO 0.000000, __MAIL_CHAIN 0.000000, __MIME_BOUND_CHARSET 0.000000, __MIME_TEXT_ONLY 0.000000, __MIME_TEXT_P 0.000000, __MIME_TEXT_P1 0.000000, __MIME_VERSION 0.000000, __MOZILLA_USER_AGENT 0.000000, __MSGID_HEX_844412 0.000000, __MULTIPLE_URI_TEXT 0.000000, __NO_HTML_TAG_RAW 0.000000, __PHISH_PHRASE1_B 0.000000, __PHISH_SPEAR_SUBJ_PREDICATE 0.000000, __REFERENCES 0.000000, __REPLYTO_SAMEAS_FROM_ACC 0.000000, __REPLYTO_SAMEAS_FROM_ADDY 0.000000, __REPLYTO_SAMEAS_FROM_DOMAIN 0.000000, __SANE_MSGID 0.000000, __SCAN_D_NEG 0.000000, __SCAN_D_NEG2 0.000000, __SCAN_D_NEG_HEUR 0.000000, __SCAN_D_NEG_HEUR2 0.000000, __SUBJ_ALPHA_NEGATE 0.000000, __SUBJ_REPLY 0.000000, __TO_IN_SUBJECT 0.000000, __TO_MALFORMED_2 0.000000, __TO_NAME 0.000000, __TO_NAME_DIFF_FROM_ACC 0.000000, __TO_REAL_NAMES 0.000000, __URI_IN_BODY 0.000000, __URI_MAILTO 0.000000, __URI_NOT_IMG 0.000000, __URI_NO_WWW 0.000000, __URI_NS 0.000000, __URI_WITH_PATH 0.000000, __USER_AGENT 0.000000 X-SASI-Probability: 10% X-SASI-RCODE: 200 X-SASI-Version: Antispam-Engine: 5.1.1, AntispamData: 2023.8.10.84217 Received: from [192.168.10.199] (dtp [192.168.10.199]) by srv2 (Weasel v2.849) for ; Thu, 10 Aug 2023 11:08:03 Reply-To: ml@ecomstation.it Subject: Re: [eCS-ISP] mysql upgrade 5.1.73 -> 5.6.51 To: eCS ISP Mailing List References: Organization: eComStation dot it Message-ID: <06f153aa-e249-a899-8f23-6de45dcbae60@ecomstation.it> Date: Thu, 10 Aug 2023 11:08:00 +0200 User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; it-IT; rv:1.7.13) Gecko/20060424 Thunderbird/1.0.8 Mnenhy/0.7.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=iso-8859-15; format=flowed Content-Language: it-IT Content-Transfer-Encoding: 8bit Il 10/08/2023 11:04, Massimo S. ha scritto: > > > Il 10/08/2023 10:59, Massimo S. ha scritto: >> >> >> Il 10/08/2023 00:19, Steven Levine ha scritto: >>> In , on 08/09/23 >>>     at 12:09 PM, "Massimo S." 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) >> >> but mysqlD show a lot of warnings like these: >> >> 2023-08-10 10:50:32 3234 [Warning] InnoDB: Cannot open table rcube2/session from the internal data >> dictionary of InnoDB though the .frm file for the table exists. See >> http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem. >> >> 2023-08-10 10:50:32 3234 [Warning] InnoDB: Cannot open table rcube2/system from the internal data dictionary >> of InnoDB though the .frm file for the table exists. See >> http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem. >> >> >> about the innodb buffer pool size this could give performance issues? >> >> thanks >> >> massimo > > sorry, i forgot this > > i get a number of these (not on all DBs): > > rcube2.session > Error    : Table 'rcube2.session' doesn't exist > status   : Operation failed > > rcube2.system > Error    : Table 'rcube2.session' doesn't exist > status   : Operation failed > > > are my 5 DBs that show this error upgraded for real? > > > massimo ignore this post, i had the issue since i didn't copied the innodb files on the \data dir i cleared everything, restarted from zero and now it completed correctly good massimo