Bug #112657 | MySQL 5.7.35-log reports "Got an error reading communication packets" | ||
---|---|---|---|
Submitted: | 8 Oct 2023 10:02 | Modified: | 11 Oct 2023 7:30 |
Reporter: | William Ding | Email Updates: | |
Status: | Unsupported | Impact on me: | |
Category: | MySQL Server: DML | Severity: | S2 (Serious) |
Version: | 5.7.35-log | OS: | Other (4.19.90-17.ky10.x86_64) |
Assigned to: | CPU Architecture: | x86 |
[8 Oct 2023 10:02]
William Ding
[9 Oct 2023 10:44]
MySQL Verification Team
Hi Mr. Ding, Thank you for your bug report. However, version 5.7 is not in maintenance since October 1st. Hence, if you can repeat the bug with latest 8.0 or latest 8.1, please let us know. If you do manage to repeat the bug as reported, send us the entire test case, which would include all the rows from that table, which produces the protocol error with that very long query. Unsupported.
[11 Oct 2023 6:15]
William Ding
Thank you for your reply. First of all, I did't repeat the bug with 8.0 or 8.1. However, I can always repeat the bug with 5.7.35-log. The entire test case: CREATE DATABASE /*!32312 IF NOT EXISTS*/ `testdb` /*!40100 DEFAULT CHARACTER SET utf8 */; USE `testdb`; -- -- Table structure for table `author` -- DROP TABLE IF EXISTS `author`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `author` ( `id` int(11) NOT NULL, `province` char(200) DEFAULT NULL, `city` varchar(200) DEFAULT NULL, `district` binary(200) DEFAULT NULL, `town` varbinary(200) DEFAULT NULL, `firstname` tinyblob, `lastname` tinytext, `address` blob, `description` text, `company` mediumblob, `department` mediumtext, `article` longblob, `brief` longtext, PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `author` -- INSERT INTO `author` VALUES (2,'4AE3C3A4EDAE892EF40FBD76876E14B1','D4F944E38B4E3786BD27B7526F192F4E',0x3537463231303230463135434345333731413545343243303641464534413241000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000,0x3530353143303138333131464131384143353439433336353730333641364631,0x3730413831463142414536434330364339354342354435434332413135434338,'15BBBCC9E64A82CB486D639A2C8B77F1',0x3646333931343534454444444637344146323543333832464139434638444534,'6C9A609A70C3DFF1C4FA83F607AA8EC6',0x3438354245343133333941443045303836324232313934333435393137454144,'783FEAA9412BE51EBFB8D86362A71127',0x3433443845343630333145383730314146364237463438384131353935443842,'0D33814A23111FD1E6773BB617C8793A0D33814A23111FD1E6773BB617C8793A0D33814A23111FD1E6773BB617C8793A0D33814A23111FD1E6773BB617C8793A0D33814A23111FD1E6773BB617C8793A0D33814A23111FD1E6773BB617C8793A0D33814A23111FD1E6773BB617C8793A0D33814A23111FD1E6773BB617C8793A0D33814A23111FD1E6773BB617C8793A0D33814A23111FD1E6773BB617C8793A0D33814A23111FD1E6773BB617C8793A0D33814A23111FD1E6773BB617C8793A0D33814A23111FD1E6773BB617C8793A0D33814A23111FD1E6773BB617C8793A0D33814A23111FD1E6773BB617C8793AC62BF63A341EFB80121995EE4DE917DE'); -- END After excuting above-mentioned SQL statements, excute DML serveral times. Then the bug will repeat.
[11 Oct 2023 7:30]
William Ding
Temporarily,I could't upload the sm4 plugin, shall I post some other information to help to find the reason of crash?
[11 Oct 2023 9:35]
MySQL Verification Team
Hi Mr. Ding, Version 5.7 is no longer supported. Hence, you can report bugs in 8.0 and 8.1. Thank you.