« Show Previous 30 Entries | Showing 31-52 of 52 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
35682 | 2008-03-30 13:33 | 2008-06-13 15:11 | Instance Manager | Closed (5793 days) | S3 | 5.1.23 | Windows (Vista X64) | Any | MySQL Service created on Vista x64 |
59940 | 2011-02-04 10:17 | 2014-10-24 2:01 | Instance Manager | Closed (4803 days) | S3 | 5.1.50, 5.1.53 | Linux | Any | mysqlmanager can't startup |
14164 | 2005-10-20 0:40 | 2005-10-27 0:22 | Instance Manager | Closed (6753 days) | S3 | mysql-5.0 | MacOS (Mac OS X (Darwin 8.2.0 kernel)) | Any | IM tests fail on MacOS X (powermacg5) |
10957 | 2005-05-30 11:38 | 2005-08-24 17:34 | Instance Manager | Closed (6817 days) | S3 | 5.0.x | Linux (Suse Linux) | Any | stop instance, issued after flush instances causes IM to crash |
11200 | 2005-06-09 12:07 | 2005-07-13 19:24 | Instance Manager | Closed (6859 days) | S3 | 5.0.7 | Linux (Suse Linux) | Any | show instance options returns garbage instead of log options |
12673 | 2005-08-19 12:38 | 2006-08-17 10:54 | Instance Manager | Closed (6459 days) | S3 | 5.0 | Linux (Linux) | Any | Instance Manager: allows to stop the instance many times |
12674 | 2005-08-19 12:38 | 2006-03-04 0:25 | Instance Manager | Closed (6625 days) | S3 | 5.0 | Any | Instance Manager: IM doesn't handle client connections correctly | |
12751 | 2005-08-23 10:34 | 2006-10-04 19:32 | Instance Manager | Closed (6411 days) | S3 | 5.0.16-BK, 5.0.11 | Linux (Linux) | Any | Instance Manager: client hangs after start instance; kill mysqlmanager; show ... |
12813 | 2005-08-25 19:31 | 2006-02-28 2:48 | Instance Manager | Closed (6629 days) | S3 | 5.0 | Any | Instance Manager: START/STOP INSTANCE commands accept a list as argument | |
14103 | 2005-10-18 1:07 | 2005-10-28 11:01 | Instance Manager | Closed (6752 days) | S3 | Other (SCO) | Any | IM tests fail on SCO | |
14106 | 2005-10-18 1:29 | 2006-05-24 19:26 | Instance Manager | Closed (6544 days) | S3 | 5.0 | Any | IM: im_life_cycle and im_utils tests fail on FreeBSD | |
14107 | 2005-10-18 1:34 | 2005-10-21 0:13 | Instance Manager | Closed (6759 days) | S3 | Any | all IM tests fail on QNX | ||
10229 | 2005-04-28 7:47 | 2005-06-14 21:01 | Instance Manager | Closed (6888 days) | S3 | Any | IM's show instance status never displays version | ||
15934 | 2005-12-22 11:55 | 2006-11-09 21:31 | Instance Manager | Closed (6375 days) | S3 | 5.0.18 | Linux (Linux (RHEL4, x86_64)) | Any | im_daemon_life_cycle fails sporadically |
15980 | 2005-12-26 2:32 | 2006-04-09 4:41 | Instance Manager | Closed (6589 days) | S3 | 5.0.17 | Any (any) | Any | net_read_timeout set too low |
17486 | 2006-02-16 17:10 | 2006-11-07 18:59 | Instance Manager | Closed (6377 days) | S3 | 5.1.6 | Linux (SUSE Linux 10.0) | Any | IM: race condition on exit |
17588 | 2006-02-20 17:11 | 2006-09-14 19:36 | Instance Manager | Closed (6431 days) | S3 | 5.1.7-beta | Other (SCO OSR 6) | Any | Problem with "drop database" in IM tests on SCO. |
17953 | 2006-03-06 8:29 | 2006-04-11 17:51 | Instance Manager | Closed (6587 days) | S3 | 5.1 | Unix | Any | Use my.cnf to enable the IM instead of having to hack the init.script |
18020 | 2006-03-07 11:42 | 2006-08-31 18:30 | Instance Manager | Closed (6445 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 (6445 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 (6445 days) | S3 | 5.0.19 | HP/UX (HP-UX + FreeBSD) | Any | IM: Server_ID not reported |
18528 | 2006-03-27 4:53 | 2006-05-31 12:06 | Instance Manager | Closed (6537 days) | S3 | 5.1 | Linux (Linux, FC4 AMD64) | Any | mysql instance manager doesn't report changes to instance |
« Show Previous 30 Entries | Showing 31-52 of 52 (Edit, Save, CSV, Feed) |