Bug 626227 - process scan returns command line for basename
Summary: process scan returns command line for basename
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: RHQ Project
Classification: Other
Component: Agent
Version: 3.0.0
Hardware: powerpc
OS: Other
low
low
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-22 20:43 UTC by Thilo Solbrig
Modified: 2014-06-27 20:26 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-27 20:26:07 UTC
Embargoed:


Attachments (Terms of Use)

Description Thilo Solbrig 2010-08-22 20:43:37 UTC
Description of problem:
process-scan query of rhq-plugin.xml is defined as "process|basename|match=^oracle.*" Process scan correctly returns "oracle" processes on Linux, which's basenames are ora_pmon_..., ora_smon_... and so on. Same plugin run on AIX 6.1 doesn't recognize any "oracle" processes. Changing process-scan query to "process|basename|match=^ora.*" on AIX 6.1 returns ora_pmon_..., ora_smon_... and so on. "ps -eo comm,args" correctly returns "oracle ora_..." pairs as well on Linux as on AIX. 

Version-Release number of selected component (if applicable):
Agent 3.0.0

How reproducible:
Try process-scan query "process|basename|match=^oracle.*" on AIX 6.1

Steps to Reproduce:
1.
2.
3.
  
Actual results:
Process-scan query "process|basename|match=^oracle.*" recognizes Oracle processes on Linux but not on AIX. Process-scan query "process|basename|match=^ora.*" does, probably due to command line pattern of ora_...

Expected results:
Process-scan query "process|basename|match=^oracle.*" to recognize Oracle processes as well on Linux as on AIX.

Additional info:

Comment 1 Jay Shaughnessy 2014-06-27 20:26:07 UTC
This was never changed. Not sure if the AIX issue went away but closing as out of date.  Community submission welcome for new, better pattern if someone wants to re-open.


Note You need to log in before you can comment on or make changes to this bug.