« Show Previous 30 Entries | Showing 31-60 of 1803 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
97387 | 2019-10-26 1:25 | 2021-05-30 9:38 | MySQL Server | Can't repeat (1033 days) | S1 | 8.0.17 | CentOS (7.7) | Any | mysql innodb cluster crash, mysql restart failed |
103715 | 2021-05-17 4:09 | 2021-05-17 8:05 | MySQL Server | Can't repeat (1046 days) | S3 | Any | Any | MySQL restart due to the bug,it is about my_hash_insert issue | |
103660 | 2021-05-11 14:18 | 2021-05-11 14:26 | MySQL Server | Can't repeat (1052 days) | S2 | 5.6.51 | Debian (9) | x86 | Sporadic crashes with signal 11 |
103260 | 2021-04-09 4:21 | 2021-04-20 23:32 | MySQL Server | Can't repeat (1073 days) | S3 | 8.0.21 | Red Hat (7.9) | Any | Unable to restart mysql server |
102341 | 2021-01-22 8:45 | 2021-01-22 15:28 | MySQL Server | Can't repeat (1161 days) | S3 | 5.7.18 | CentOS (6.6) | Any | Why handle_fatal_signal redirect stderr to binlog index file? |
100732 | 2020-09-03 16:16 | 2020-09-04 5:37 | MySQL Server | Can't repeat (1301 days) | S2 | 5.7.24 | SUSE | x86 | BIGINT UNSIGNED arithmetic operations return wrong value |
100148 | 2020-07-08 3:07 | 2020-08-10 12:22 | MySQL Server | Can't repeat (1326 days) | S2 | 8.0.18 | Red Hat | x86 | During a parallel read operation, the rollback of a table load operation causes |
100416 | 2020-08-04 1:53 | 2021-06-15 14:18 | MySQL Server | Can't repeat (1326 days) | S3 | 8.0.19 | Red Hat (7.6) | x86 | UTC - mysqld got signal 11 |
100468 | 2020-08-08 17:23 | 2020-08-09 11:35 | MySQL Server | Can't repeat (1327 days) | S2 | 8.0 | Linux | Any | inconcistent records in role_edges block mysqld to start |
99679 | 2020-05-25 2:32 | 2020-05-26 9:14 | MySQL Server | Can't repeat (1402 days) | S3 | 8.0.18 | Any | Any | stop group_replication will assert |
99183 | 2020-04-05 16:01 | 2020-05-07 12:37 | MySQL Server | Can't repeat (1421 days) | S3 | 8.0.19 | Any | Any | Comparison on FLOAT(9, 9) gives an incorrect result |
96286 | 2019-07-23 9:39 | 2020-04-14 12:06 | MySQL Server | Can't repeat (1444 days) | S1 | 5.7.19 | Any | Any | mysql server crash when doning buf flushing |
99234 | 2020-04-12 2:57 | 2021-02-18 13:18 | MySQL Server | Can't repeat (1444 days) | S1 | 8.0.19 | Ubuntu (18.04) | Any (amd64) | Crash on a specific query after upgrading to 8.0.19 |
98294 | 2020-01-20 10:37 | 2021-04-29 19:04 | MySQL Server | Can't repeat (1494 days) | S2 | MySQL 5.7.28 | Ubuntu (16.04 LTS OS) | Any | mysqld got signal 6 ; |
98547 | 2020-02-11 7:18 | 2020-02-18 13:26 | MySQL Server | Can't repeat (1500 days) | S3 | 8.0.19 | CentOS | Other (x64) | Strange SUM value with GROUP BY |
98490 | 2020-02-05 7:15 | 2020-02-05 20:23 | MySQL Server | Can't repeat (1513 days) | S3 | mysqld 8.0.18 | Windows (Windows 2012 64 Bit) | Any | Unable to start Mysql 8 service |
97983 | 2019-12-13 9:37 | 2019-12-16 13:50 | MySQL Server | Can't repeat (1564 days) | S3 | mysqld 5.7.26 | Linux | Any | InnoDB: Assertion failure in thread 139707135178496 in file fsp0fsp.cc line 2112 |
97941 | 2019-12-10 11:19 | 2019-12-10 14:19 | MySQL Server | Can't repeat (1570 days) | S3 | 5.6.29/5.7.25 | Any | Any | not in (null) returns wrong result |
97823 | 2019-11-28 7:05 | 2019-12-06 3:10 | MySQL Server | Can't repeat (1574 days) | S3 | 5.7.27 | CentOS (CentOS release 6.10 (Final)) | x86 (64-bit) | InnoDB: Failing assertion: UT_LIST_GET_LEN(rseg->update_undo_list) == 0 |
96384 | 2019-07-31 10:39 | 2021-01-27 13:21 | MySQL Server | Can't repeat (1648 days) | S2 | 5.7.26 | Ubuntu (16.04.6) | Any | MySQL Crash with Assertion failure in file trx0trx.ic |
93504 | 2018-12-06 11:22 | 2019-08-02 18:05 | MySQL Server | Can't repeat (1700 days) | S6 | 8.0.13 | Any | Any | Assertion failed: (false), function check_icu_status |
95883 | 2019-06-19 14:24 | 2019-07-22 11:49 | MySQL Server | Can't repeat (1711 days) | S3 | Windows (windows server 2012r2) | Any | server crash very day | |
78673 | 2015-10-01 15:05 | 2019-06-30 14:51 | MySQL Server | Can't repeat (1733 days) | S1 | Ubuntu | Any | mysql won't start - has suffered Innodb crash | |
95679 | 2019-06-07 6:50 | 2019-06-07 14:35 | MySQL Server | Can't repeat (1756 days) | S3 | MacOS | Any | Error in Starting MySQL on Mac | |
95512 | 2019-05-24 1:16 | 2019-05-24 21:01 | MySQL Server | Can't repeat (1770 days) | S2 | 8.0.16 | Windows | x86 | Really odd bug. Incorrect error of datetime |
94741 | 2019-03-22 5:26 | 2019-05-02 13:21 | MySQL Server | Can't repeat (1792 days) | S3 | 5.7.18 | CentOS (7.4) | x86 (2vCPU x 4GB RAM) | SQL mode error catching the wrong updated column |
78218 | 2015-08-26 8:27 | 2019-04-24 20:16 | MySQL Server | Can't repeat (1800 days) | S1 | 5.5.43 | CentOS (32bit) | Any | The database engine restarts due to internal failure. Got error: 2013: Lost con. |
93715 | 2018-12-21 10:26 | 2019-04-23 13:29 | MySQL Server | Can't repeat (1801 days) | S2 | 5.7.24 | Windows | x86 | MySQL Server Crash (Access Violation) whilst reading from Information_schema |
95073 | 2019-04-22 11:41 | 2019-04-22 13:46 | MySQL Server | Can't repeat (1802 days) | S2 | 5.7.23 | CentOS (CentOS release 6.8 (Final)) | x86 | show create statement result in mysql crash |
94098 | 2019-01-28 11:35 | 2019-01-28 13:38 | MySQL Server | Can't repeat (1886 days) | S1 | 5.7.13-6-log | Ubuntu | x86 | InnoDB: Assertion failure in thread 139641453184768 in file trx0trx.ic line 213 |
« Show Previous 30 Entries | Showing 31-60 of 1803 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |