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 (4300 days) | S2 | Windows (windows 7) | Any | Splitter Distance | |
59940 | 2011-02-04 10:17 | 2014-10-24 2:01 | Instance Manager | Closed (4799 days) | S3 | 5.1.50, 5.1.53 | Linux | Any | mysqlmanager can't startup |
33472 | 2007-12-21 21:32 | 2011-02-16 23:43 | Instance Manager | Closed (5373 days) | S3 | mysql-azalea, 6.0.4-alpha | Any (all Unix + Linux) | Any | Instance Manager ("mysqlmanager") still shows up in the start/stop script |
35682 | 2008-03-30 13:33 | 2008-06-13 15:11 | Instance Manager | Closed (5789 days) | S3 | 5.1.23 | Windows (Vista X64) | Any | MySQL Service created on Vista x64 |
28030 | 2007-04-23 17:44 | 2007-08-02 3:37 | Instance Manager | Closed (6105 days) | S1 | 5.1 | Any | Any | test im_instance_conf fails with an assert |
28012 | 2007-04-22 9:10 | 2007-08-02 3:40 | Instance Manager | Closed (6105 days) | S3 | 5.1 BK | Windows | Any | Patch : IM crashes instead of reporting an error when mysqldpath is bad |
21783 | 2006-08-22 13:35 | 2007-04-06 14:12 | Instance Manager | Closed (6223 days) | S3 | 5.0.25 | Linux (Linux) | Any | Instance Manager does not exit on fatal error |
22511 | 2006-09-20 8:54 | 2007-03-08 3:19 | Instance Manager | Closed (6252 days) | S3 | 5.0 | UNIX | Any | IM does not remove angel-pid-file on clean shutdown |
24415 | 2006-11-18 20:26 | 2007-03-07 21:57 | Instance Manager | Closed (6253 days) | S3 | 5.0.32 | Linux (linux (debian)) | Any | Instance manager test im_daemon_life_cycle fails randomly . |
19044 | 2006-04-12 11:01 | 2007-01-16 20:53 | Instance Manager | Closed (6303 days) | S3 | 5.0 | Windows (Windows) | Any | IM aborts on exit |
23476 | 2006-10-19 19:01 | 2007-01-16 20:45 | Instance Manager | Closed (6303 days) | S1 | 5.1.12 BK | Any | DROP INSTANCE does not work | |
23215 | 2006-10-12 13:41 | 2007-01-16 20:49 | Instance Manager | Closed (6303 days) | S2 | 5.1.12 BK | Linux (Linux) | Any | STOP INSTANCE takes too much time |
22306 | 2006-09-13 12:48 | 2007-01-16 20:51 | Instance Manager | Closed (6303 days) | S3 | 5.1 | Any | STOP INSTANCE can not be applied for instances in Crashed, Failed and Abandoned | |
22242 | 2006-09-11 18:23 | 2006-11-30 20:13 | Instance Manager | Closed (6350 days) | S2 | 5.1.12 | Any | Instance Manager: option-parsing errors | |
22494 | 2006-09-19 20:22 | 2006-11-11 3:14 | Instance Manager | Closed (6369 days) | S3 | 5.1.12 | Any | Instance Manager: Inconsistent error message wording | |
15934 | 2005-12-22 11:55 | 2006-11-09 21:31 | Instance Manager | Closed (6371 days) | S3 | 5.0.18 | Linux (Linux (RHEL4, x86_64)) | Any | im_daemon_life_cycle fails sporadically |
17486 | 2006-02-16 17:10 | 2006-11-07 18:59 | Instance Manager | Closed (6373 days) | S3 | 5.1.6 | Linux (SUSE Linux 10.0) | Any | IM: race condition on exit |
22472 | 2006-09-19 10:00 | 2006-10-26 3:34 | Instance Manager | Closed (6385 days) | S3 | 5.1 | Windows (Windows) | Any | IM: --socket option should be removed from Windows version |
19368 | 2006-04-26 10:04 | 2006-10-25 18:57 | Instance Manager | Closed (6386 days) | S2 | 5.0.21 | Any (all) | Any | Failure in "flush_instances" causes assert in Thread_registry |
12751 | 2005-08-23 10:34 | 2006-10-04 19:32 | Instance Manager | Closed (6407 days) | S3 | 5.0.16-BK, 5.0.11 | Linux (Linux) | Any | Instance Manager: client hangs after start instance; kill mysqlmanager; show ... |
22379 | 2006-09-15 7:44 | 2006-10-04 19:22 | Instance Manager | Closed (6407 days) | S1 | 5.0 + 5.1 | Linux (Linux) | Any | im_daemon_life_cycle.test fails on merge of 5.1 -> 5.1-engines |
17588 | 2006-02-20 17:11 | 2006-09-14 19:36 | Instance Manager | Closed (6427 days) | S3 | 5.1.7-beta | Other (SCO OSR 6) | Any | Problem with "drop database" in IM tests on SCO. |
18020 | 2006-03-07 11:42 | 2006-08-31 18:30 | Instance Manager | Closed (6441 days) | S3 | 5.0.24 and earlier | Some Unix (see text) | Any | IM connect problem |
18027 | 2006-03-07 12:48 | 2006-08-31 18:27 | Instance Manager | Closed (6441 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 (6441 days) | S3 | 5.0.19 | HP/UX (HP-UX + FreeBSD) | Any | IM: Server_ID not reported |
21331 | 2006-07-28 16:06 | 2006-08-31 18:32 | Instance Manager | Closed (6441 days) | S3 | 5.0.21 and up | Any (Some Unix (see text)) | Any | Instance Manager: Connect problems in tests |
17485 | 2006-02-16 16:54 | 2006-08-30 20:23 | Instance Manager | Closed (6442 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 |
21247 | 2006-07-24 7:36 | 2006-08-30 20:09 | Instance Manager | Closed (6442 days) | S2 | 5.1.12 | Linux (Linux) | Any | Instance Manager: im_instance_conf.imtest fails on trees with test-1 in name |
21365 | 2006-07-31 14:34 | 2006-08-18 13:42 | Instance Manager | Closed (6454 days) | S3 | 5.0.24 | Some Unix (see text) | Any | IM: Second instance in un-expected status |
12673 | 2005-08-19 12:38 | 2006-08-17 10:54 | Instance Manager | Closed (6455 days) | S3 | 5.0 | Linux (Linux) | Any | Instance Manager: allows to stop the instance many times |
Showing 1-30 of 52 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |