| Showing 1-30 of 4100 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 108036 | 2022-07-29 19:50 | 2023-05-23 8:28 | MySQL Server | Analyzing (418 days) | S3 | 8.0.30 | Debian (bullseye) | x86 | Server assertion crash after upgrade on 8.0.30 |
| 90813 | 2018-05-09 20:11 | 2021-07-04 9:18 | MySQL Server | Analyzing (1961 days) | S3 | 5.6.40 | CentOS (7.3) | Any | Timezone not correctly read from host |
| 72062 | 2014-03-17 16:13 | 2016-02-28 20:45 | MySQL Server | Analyzing (3477 days) | S2 | 5.7 | Any | Any | MySQL 5.7 CONFLICTS with MariaDB w/r/t 1900+ range for error codes |
| 112176 | 2023-08-24 14:01 | 2023-08-25 12:31 | MySQL Server | Can't repeat (29 days) | S3 | Any (Parameter not valid window appears) | Any | Unable to run SQL due to parameter not valid | |
| 112148 | 2023-08-23 3:34 | 2023-08-23 12:53 | MySQL Server | Can't repeat (31 days) | S3 | 8.0.34 | Red Hat (Red Hat Enterprise Linux Server 7.7(Maipo)) | x86 (Hygon C86 7375) | Description Failed to upgrade mysql from 8.0.20 to 8.0.34 |
| 111987 | 2023-08-07 11:26 | 2023-08-08 12:25 | MySQL Server | Can't repeat (46 days) | S3 | 5.7.42 | Any | Any | Error filesort result when max_length_for_sort_data is set to a big value |
| 111961 | 2023-08-03 18:21 | 2023-08-03 18:32 | MySQL Server | Can't repeat (51 days) | S3 | 8.0.34 | Windows (Windows Server 2019) | Other (x64) | MySQL 8.0.34 crashing suddenly |
| 111946 | 2023-08-02 15:12 | 2023-08-04 12:12 | MySQL Server | Can't repeat (52 days) | S3 | 5.7 | Debian | Any | Fulltext index not being maintained, nothing shows up in error log or mysqlcheck |
| 111859 | 2023-07-24 8:43 | 2023-07-24 13:16 | MySQL Server | Can't repeat (61 days) | S3 | Any | Any | assertion fails by shutdown trx_sys_close: m_views and trx_sys->mysq | |
| 111442 | 2023-06-15 19:02 | 2023-07-17 12:48 | MySQL Server | Can't repeat (68 days) | S3 | 8.0.32 | Any | Any | misleading startup error message related to GTID configuration |
| 111626 | 2023-06-30 7:09 | 2023-06-30 13:26 | MySQL Server | Can't repeat (85 days) | S3 | 8.0.23-commercial | Any | Any | The MGR configuration is partially incorrect as expected |
| 111420 | 2023-06-14 12:37 | 2023-06-14 13:25 | MySQL Server | Can't repeat (101 days) | S2 | 8.0.32 | Ubuntu | Other | DB instance restarted with AWS RDS database |
| 111382 | 2023-06-13 3:46 | 2023-06-13 12:37 | MySQL Server | Can't repeat (102 days) | S3 | latest | Any (ran number of tables) | Any | got abug |
| 111302 | 2023-06-06 18:35 | 2023-06-07 12:45 | MySQL Server | Can't repeat (108 days) | S3 | 8.0.32 build 2612062 CE (64 bits) | Any | Any | Returns OK in Message |
| 111150 | 2023-05-25 9:54 | 2023-05-25 10:14 | MySQL Server | Can't repeat (121 days) | S3 | Windows | Any | Data Import Error | |
| 111070 | 2023-05-18 8:52 | 2023-05-18 9:34 | MySQL Server | Can't repeat (128 days) | S2 | 8.0.25 | Any | Any | View query failure |
| 111029 | 2023-05-15 12:01 | 2023-05-15 12:29 | MySQL Server | Can't repeat (131 days) | S3 | 8.0.29 | Red Hat (7.6) | x86 | corruption in the InnoDB tablespace |
| 110991 | 2023-05-11 10:23 | 2023-05-11 12:41 | MySQL Server | Can't repeat (135 days) | S2 | 8.0.33 | Ubuntu (20.04.1) | x86 | After server upgrade it does not start |
| 110345 | 2023-03-11 21:50 | 2023-07-18 12:50 | MySQL Server | Can't repeat (156 days) | S2 | 8.0.32 | MacOS (Ventura 13.0.1) | ARM | MySQL crash on MacOS typically when restoring a MySQL 5.7 sql |
| 110676 | 2023-04-13 8:46 | 2023-04-13 11:52 | MySQL Server | Can't repeat (163 days) | S2 | 8.0.32 | Ubuntu (20.04) | x86 | mysqld got signal 11 after update from 8.0.31 to 8.0.32 |
| 110633 | 2023-04-07 5:20 | 2023-04-07 11:55 | MySQL Server | Can't repeat (169 days) | S3 | 8.0.32 | CentOS | Any | Orphaned full-text indexes |
| 110598 | 2023-04-04 5:40 | 2023-04-04 13:11 | MySQL Server | Can't repeat (172 days) | S3 | 8.0.30 | Windows (Windows Server 2016 Datacenter) | x86 (Intel Xeon Silver 4216) | [ERROR] [MY-013183] [InnoDB] Assertion failure: fsp0fsp.cc:2152:inode thread |
| 110343 | 2023-03-10 22:00 | 2023-03-14 13:07 | MySQL Server | Can't repeat (193 days) | S3 | 8.0.32-1.el8 | Linux (Official MySQL Docker image) | x86 | Reproducible crash with assertion failure when updating |
| 109542 | 2023-01-06 1:22 | 2023-03-14 12:46 | MySQL Server | Can't repeat (194 days) | S2 | 8.0.30 | Linux | Any | Multiple different-looking crashes after upgrade to 8.0.30 |
| 109289 | 2022-12-06 8:20 | 2023-03-06 13:48 | MySQL Server | Can't repeat (201 days) | S3 | 8.0.30, 8.0.32 | Windows (Server 2019) | Any | MySQL 8.0.32 corrupted table causing MySQL to crash |
| 110269 | 2023-03-03 13:28 | 2023-03-03 15:05 | MySQL Server | Can't repeat (204 days) | S3 | 8.0.30 | Ubuntu (Rel 20.04.2) | Any (Intel Xeon E5620) | Server crashed on ALTER TABLE. Now crashes on SELECT. |
| 110014 | 2023-02-10 1:29 | 2023-02-10 13:34 | MySQL Server | Can't repeat (225 days) | S3 | 5.7.38 | CentOS | x86 | Crash during pquery: process_str_arg & my_vsnprintf_ex |
| 109813 | 2023-01-27 6:50 | 2023-01-27 8:01 | MySQL Server | Can't repeat (239 days) | S3 | 5.6 | Windows | Any | opening error |
| 109301 | 2022-12-06 23:05 | 2022-12-08 4:36 | MySQL Server | Can't repeat (289 days) | S2 | 8.0.31 | Fedora | Any | MySQL 5.7 -> 8.0.31 Page old data size XXX new data size YYY error |
| 109320 | 2022-12-08 13:19 | 2023-01-05 13:20 | MySQL Server | Can't repeat (289 days) | S3 | 8.0.31 | CentOS (CentOS Linux release 7.9.2009 (Core)) | x86 (Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz) | mysql freeze on SHOW GLOBAL STATUS |
| Showing 1-30 of 4100 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
