#4470 [HHQ-4261] Zimbra Stats process inconsistently requires Conf

[Hyperic Team]

http://jira.hyperic.com/browse/HHQ-4261
Zimbra Stats process inconsistently requires Configuration and has no Collection Interval for Availability.

After installing a hq-agent on a Zimbra server, the Auto-Group for Zimbra 6.0.x Stats Process shows as gray, not configured so it is not collecting. Drilling into the auto-group, the members show that two are available and 10 are gray.

Only these two are set as available:


 1. zmstat-fd-real.pid


 2. zmstat-fd.pid are availble.

These 10 are set as not configured:


 1. zmstat-allprocs.pid


 2. zmstat-convertd.pid


 3. zmstat-cpu.pid


 4. zmstat-df.pid


 5. zmstat-io-x.pid


 6. zmstat-io.pid


 7. zmstat-mtaqueue.pid


 8. zmstat-mysql.pid


 9. zmstat-proc.pid


 10. zmstat-vm.pid

Clicking on one of the not configured stat processes, the message is displayed:


'This resource is turned off or has not been configured properly.


The problem is: Invalid configuration: Error retrieving value: Failed to invoke getProcMem[Pid.PidFile.eq=/opt/zimbra/zmstat/pid/zmstat-mysql.pid]: Query did not match any processes: Pid.PidFile.eq=/opt/zimbra/zmstat/pid/zmstat-mysql.pid


Please turn on the server, or fix its Configuration Properties.'

It is necessary to click Configuration Properties and without changing anything, click the OK button. This will result in 'Your changes have been saved.'

It should be that the 10 stat processes are enabled by default and no configuration is necessary.

Looking at the Metric Data, it shows that for each of these 10 stat processes, the Collection Interval for Availability is set to NONE. The availability should be set to some default like 5 minutes.

There should be consistency for all the stat processes that they are all configured the same and have the same default collection interval.

Expected Result:


1. All stat processes are enabled by default and no configuration is neccessary especially when no change to configuration properties is made.


2. Collection Interval for Availability is set by default to collect availability.

Actual Result:


1. It shows stat processes are not configured and require user to look at configuration properties and click OK without making any changes.


2. The availability is displayed as gray, not configured so not collecting availability.

Steps to Reproduce:


1. Install hq-agent on Zimbra server


2. Log into Hyperic


3. Add Zimbra platform to Inventory from Auto-discovery


4. Allow time for availability and metrics to collect


5. Select Zimbra server from within Platform Services Health


6. Look at Zimbra 6.0.x Stats Process


7. Note the availability shows as gray; not configured so not collecting availability


8. Select Zimbra 6.0.x Stats process from within Services


9. Note reported status of individual stat processes (2 available and 10 gray)


10. Select a stat process that is gray (i.e., zmstat-allprocs.pid)


11. Note the message not configured


12. Click the Configuration Properties


13. Without making any changed, click the OK button


14. Note the Configuration Properties have been saved


15. Click on the Monitor tab


16. Select Metric Data


17. Note the Collection Interval for Availability is set to NONE

Work around:


None

Additional Information:


This was seen after installing and starting the hq-agent but Zimbra stats were not running


Started Zimbra stats and restarted hq-agent