Description of problem:
The JON Agent (version 3.0.1-GA) generates the following Warning message:
2011-04-07 14:32:08,132 WARN [ResourceDiscoveryComponent.invoker.daemon-21] (org.rhq.plugins.apache.ApacheServerDiscoveryComponent)- Discovery of Apache process [process: pid=, name=[httpd], ppid=] failed: Executable path (./httpd) is not absolute.Please restart Apache specifying an absolute path for the executable.
The default EWS Apache instance, <EWS_HOME>/httpd/sbin/apachectl uses a relative not an absolute path for the variable HTTPD. So the agent cannot find it.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
While after unzipping the EWS installation ZIP, the apachectl script does contain the relative path, the path gets replaced by a full path after completing the installations steps:
namely the step 3.13.
Debbie, how did you install your EWS so that I can try and replicate this?
Step 3.13 was not performed. Which would explain why the path was not absolute. Seems like this bug can be closed as WORKSFORME with an explanation that step 3.13 of the EWS installation guide must be performed in order for the Apache instance of EWS to be discoverable.
As Larry outlined above, this is not really a bug. Nevertheless, I improved the warning we output to logs so that it is more clear what the symptoms might be.
We ARE able to detect the full path of the executable even if httpd was started with a relative path as long as the user running the agent has enough privs to read the commadline params of the httpd process.
BZ 697585 - A better warning message if an absolute path of httpd
executable can't be established + a little bit of paranoia when trying
to figure out the absolute path.
Verified on build#18 in rhq-release-gwt-locales branch.
Started the default EWS Apache instance <EWS_HOME>/httpd/sbin/apachectl (without completing the installations step 3.13)
Verified that the EWS apache instance is discovered and shows the full executable path as "/install/ews/jboss-ews-1.0/httpd/sbin/httpd" in connection settings.
marking VERIFIED JON 3 bugs to CLOSED/CURRENTRELEASE
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE