MySQL Bugs: #38709: Monitor cannot clear bad disk rules

Bug #38709	Monitor cannot clear bad disk rules
Submitted:	11 Aug 2008 8:28	Modified:	30 Jan 2009 18:01
Reporter:	Jonathon Coombes	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Advisors/Rules	Severity:	S2 (Serious)
Version:	1.3.2.9096	OS:	Any
Assigned to:	Darren Oldag	CPU Architecture:	Any
Tags:	disk, rules

Description:
When creating a rule with the os:disk:fs_used data item, if the instance is not a valid mount point then the agent reports the error:

2008-08-11 17:57:00: (critical) disk-get failed for all: 2 

The above instance was for 'all', and similar results for instance 'disk' occur.

The issue is that upon editing the rule, or even deleting the rule, the agent still shows the above error type. Restarted both the agent and the monitoring service, but neither seem to get rid of the error.

How to repeat:
Create a custom rule using the os:disk:fs_used data item and assign and instance such as 'all' or 'disk' instead of a valid mount point and schedule it. 

Then try and edit or remove the rule and have a new one work without giving the error message in the log.

Verified as described on Mac OS 10.5.4 using 1.3.2.9096

This is fixed in Monitor 2.0

Verified fixed in build 2.0.4.7141.

An entry was added to the 2.0.4 changelog:

An error generated by a rule failed to clear.

When a rule was created with the os:disk:fs_used data item, if the instance was not a valid mount point then the Service Agent reported the error:

2008-08-11 17:57:00: (critical) disk-get failed for all: 2
Note the above instance was for “all”, and similar results occurred for instance “disk”.

The issue was that upon editing the rule, or even deleting the rule, the agent still showed the above error type. Restarting the agent and the monitoring service failed to remove the error.