| Bug #46667 | Not able to change frequency on rule 'MySQL Agent Not Reachable' | ||
|---|---|---|---|
| Submitted: | 12 Aug 2009 5:12 | Modified: | 1 Mar 2010 13:34 |
| Reporter: | Roel Van de Paar | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Enterprise Monitor: Advisors/Rules | Severity: | S3 (Non-critical) |
| Version: | 2.1.0.1079,2.1.0.1080 | OS: | Any |
| Assigned to: | Josh Sled | CPU Architecture: | Any |
[12 Aug 2009 5:13]
Roel Van de Paar
Also see bug #28589
[12 Aug 2009 5:19]
Roel Van de Paar
Verifying as D2 I can reproduce this on Ubuntu 9.04 running MEM 2.1.0.1080. Customer was running 2.1.0.1079
[12 Aug 2009 5:21]
Roel Van de Paar
'MySQL Server Not Reachable' is the only heat chart rule affected. Others are fine when changed.
[12 Aug 2009 6:14]
Roel Van de Paar
s/'bug #46535'/'bug #42932'/ in the original description and the IRC.
[18 Jan 2010 2:05]
Roel Van de Paar
Any updates on when MySQL Enterprise Monitor will be generating an error for this?
[10 Feb 2010 18:01]
Enterprise Tools JIRA Robot
Josh Sled writes: revno: 7888 revision-id: jsled@asynchronous.org-20100210175948-kghspx1456pck80j parent: jsled@asynchronous.org-20100210150538-crg8ow3b235nmrqf committer: Josh Sled <jsled@asynchronous.org> branch nick: local timestamp: Wed 2010-02-10 12:59:48 -0500 message: EM-3515: make changing the frequency of the special rule's schedule Exceptional, then trap that Exception when we try to do so in the app layer, and present a warning to the user.
[10 Feb 2010 19:08]
Enterprise Tools JIRA Robot
Keith Russell writes: Patch installed in versions => 2.2.0.1614.
[10 Feb 2010 19:36]
Enterprise Tools JIRA Robot
Keith Russell writes: Last AIB comment should say, patch installed in versions => 2.2.0.1616
[16 Feb 2010 15:32]
Enterprise Tools JIRA Robot
Marcos Palacios writes: Verified fixed in Monitor build 2.2.0.1616.
[1 Mar 2010 13:34]
MC Brown
A note has been added to the 2.2.0 changelog: The schedule for the <guilabel>MySQL Agent Not Reachable</guilabel> rule cannot be modified. This is to ensure that problems communicating with the agent are identified immediately. If you attempt to modify the scheduling an error will be reported.

Description: Report from the customer: --- I cannot change the frequency. I do not get an error. I change the frequency from 'Mysql Agent not Reachable' to 5 minutes for all servers. I mark one server or all and click on edit. I change the frequency to 5 minutes and click update (use default frequency is not marked). The page refreshes and in the column the frequency time is not changed. --- Logging bug as per IRC w/ jsled. How to repeat: Install 2.1.0.1080, monitor > advisors > tick 'MySQL Agent Not Reachable' > edit > Change to 5 minutes > Update > refresh Suggested fix: Either fix/allow to change the frequency, or give a clearer error message ('not allowed'). Also see bug #46535