Red Hat Bugzilla – Bug 564107
Log level of Sigar failures: Change from DEBUG to ERROR.
Last modified: 2011-03-08 07:50:46 EST
Description of problem:
I've been trying to add Tomcat 5.5.28 from EWS 1.0.1 on Windows 2003. Tomcat exposes JMX, but the agent fails to send the information. This is what jshaughn identified as the most likely culprit:
2010-02-11 20:52:06,796 DEBUG [InventoryManager.discovery-1] (org.rhq.core.system.ProcessInfo)- Unexpected error occurred while looking up info for [<unknown>] process with pid  - call to getProcExe failed. Did the process die? Cause: org.hyperic.sigar.SigarException: Incorrect function.
"(21:23:19) jshaughn: but really, I think 2000 (minimum), XP (most likely) and Vista are the real targets. Win7 as well, but that's not yet tested."
As Windows 2003 is supported ( http://www.jboss.com/pdf/JON_2.3_datasheet.pdf ), I suggest to log it at ERROR level.
Created attachment 390346 [details]
Btw, Sigar platforms support:
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs.
new = Tracking + FutureFeature + SubBug
making sure we're not missing any bugs in rhq_triage
mazz- should be a quick fix, no?
we used to have this message at a higher log level but the logs got very noisy so we lowered it to DEBUG. It seems this isn't a rare error condition, sometimes sigar just can't see all the processes and in many cases, this actually isn't an error condition, its just the agent doesn't have perms to view them all.
recommend either we close as WONTFIX since we used to have it this way but chose to change it to DEBUG.
As mazz described in his comment this change in logging was made deliberately, and would not have any functional impact on the operation of the Tomcat plugin. Therefore I'm setting this to WONTFIX. If there is a related issue to Tomcat not being manageable on Win2003 then that needs to be raised as a new issue.