Showing 1-30 of 52 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
65878 | 2012-07-11 19:33 | 2012-07-11 19:46 | Instance Manager | Closed (4279 days) | S2 | Windows (windows 7) | Any | Splitter Distance | |
10229 | 2005-04-28 7:47 | 2005-06-14 21:01 | Instance Manager | Closed (6863 days) | S3 | Any | IM's show instance status never displays version | ||
14107 | 2005-10-18 1:34 | 2005-10-21 0:13 | Instance Manager | Closed (6734 days) | S3 | Any | all IM tests fail on QNX | ||
14103 | 2005-10-18 1:07 | 2005-10-28 11:01 | Instance Manager | Closed (6727 days) | S3 | Other (SCO) | Any | IM tests fail on SCO | |
19044 | 2006-04-12 11:01 | 2007-01-16 20:53 | Instance Manager | Closed (6282 days) | S3 | 5.0 | Windows (Windows) | Any | IM aborts on exit |
22511 | 2006-09-20 8:54 | 2007-03-08 3:19 | Instance Manager | Closed (6231 days) | S3 | 5.0 | UNIX | Any | IM does not remove angel-pid-file on clean shutdown |
20716 | 2006-06-27 9:11 | 2006-08-14 21:20 | Instance Manager | Closed (6437 days) | S3 | 5.0 | Any | SHOW INSTANCES statement causes races in IM tests | |
20622 | 2006-06-22 10:05 | 2006-07-06 22:43 | Instance Manager | Closed (6476 days) | S1 | 5.0 | Linux (Linux) | Any | Buffer overwrite in instance manager causes im crash |
12813 | 2005-08-25 19:31 | 2006-02-28 2:48 | Instance Manager | Closed (6604 days) | S3 | 5.0 | Any | Instance Manager: START/STOP INSTANCE commands accept a list as argument | |
14106 | 2005-10-18 1:29 | 2006-05-24 19:26 | Instance Manager | Closed (6519 days) | S3 | 5.0 | Any | IM: im_life_cycle and im_utils tests fail on FreeBSD | |
12674 | 2005-08-19 12:38 | 2006-03-04 0:25 | Instance Manager | Closed (6600 days) | S3 | 5.0 | Any | Instance Manager: IM doesn't handle client connections correctly | |
12673 | 2005-08-19 12:38 | 2006-08-17 10:54 | Instance Manager | Closed (6434 days) | S3 | 5.0 | Linux (Linux) | Any | Instance Manager: allows to stop the instance many times |
22379 | 2006-09-15 7:44 | 2006-10-04 19:22 | Instance Manager | Closed (6386 days) | S1 | 5.0 + 5.1 | Linux (Linux) | Any | im_daemon_life_cycle.test fails on merge of 5.1 -> 5.1-engines |
14537 | 2005-11-01 8:23 | 2005-11-09 2:59 | Instance Manager | Closed (6715 days) | S1 | 5.0.15 | Windows (Windows 2003) | Any | Instanse manager crashes with 'access violation' when started on Windows |
14388 | 2005-10-27 11:51 | 2005-10-31 18:53 | Instance Manager | Closed (6724 days) | S1 | 5.0.15-GA | Linux (Suse Linux 9.3) | Any | IM eats 99% CPU |
12751 | 2005-08-23 10:34 | 2006-10-04 19:32 | Instance Manager | Closed (6386 days) | S3 | 5.0.16-BK, 5.0.11 | Linux (Linux) | Any | Instance Manager: client hangs after start instance; kill mysqlmanager; show ... |
14723 | 2005-11-07 22:14 | 2005-11-20 3:38 | Instance Manager | Closed (6704 days) | S1 | 5.0.16-snapshot (2005-11-05) | Linux (linux (RH 9, RHEL 4)) | Any | Dumping of stored functions seems to cause corruption in the function body |
15980 | 2005-12-26 2:32 | 2006-04-09 4:41 | Instance Manager | Closed (6564 days) | S3 | 5.0.17 | Any (any) | Any | net_read_timeout set too low |
15934 | 2005-12-22 11:55 | 2006-11-09 21:31 | Instance Manager | Closed (6350 days) | S3 | 5.0.18 | Linux (Linux (RHEL4, x86_64)) | Any | im_daemon_life_cycle fails sporadically |
18027 | 2006-03-07 12:48 | 2006-08-31 18:27 | Instance Manager | Closed (6420 days) | S3 | 5.0.19 | Solaris (Solaris 9 (x86) + others) | Any | IM: Server_ID differs |
18033 | 2006-03-07 13:50 | 2006-08-31 18:31 | Instance Manager | Closed (6420 days) | S3 | 5.0.19 | HP/UX (HP-UX + FreeBSD) | Any | IM: Server_ID not reported |
18023 | 2006-03-07 12:22 | 2006-06-21 10:26 | Instance Manager | Closed (6491 days) | S1 | 5.0.19 + earlier 5.0 | sol10-amd64-a, OpenBSD + others | Any | IM: instance can be started several times; monitor interval must be > 2sec |
19391 | 2006-04-27 1:03 | 2006-07-07 20:12 | Instance Manager | Closed (6475 days) | S2 | 5.0.21 | OpenServer 6, Linux PPC | Any | IM fails to start after two executions |
19368 | 2006-04-26 10:04 | 2006-10-25 18:57 | Instance Manager | Closed (6365 days) | S2 | 5.0.21 | Any (all) | Any | Failure in "flush_instances" causes assert in Thread_registry |
19362 | 2006-04-26 7:06 | 2006-05-10 16:31 | Instance Manager | Closed (6533 days) | S2 | 5.0.21 | Any (all) | Any | im_daemon_lifecycle fails when built from source distribution |
21331 | 2006-07-28 16:06 | 2006-08-31 18:32 | Instance Manager | Closed (6420 days) | S3 | 5.0.21 and up | Any (Some Unix (see text)) | Any | Instance Manager: Connect problems in tests |
21365 | 2006-07-31 14:34 | 2006-08-18 13:42 | Instance Manager | Closed (6433 days) | S3 | 5.0.24 | Some Unix (see text) | Any | IM: Second instance in un-expected status |
18020 | 2006-03-07 11:42 | 2006-08-31 18:30 | Instance Manager | Closed (6420 days) | S3 | 5.0.24 and earlier | Some Unix (see text) | Any | IM connect problem |
17485 | 2006-02-16 16:54 | 2006-08-30 20:23 | Instance Manager | Closed (6421 days) | S2 | 5.0.24-BK, 5.0.18 | Linux (SUSE Linux 10.0) | Any | Instance Manager: mysql client crashes when connecting to the IM |
21783 | 2006-08-22 13:35 | 2007-04-06 14:12 | Instance Manager | Closed (6202 days) | S3 | 5.0.25 | Linux (Linux) | Any | Instance Manager does not exit on fatal error |
Showing 1-30 of 52 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |