Bug 48792 - httpd util apachectl returns wrong status information
Summary: httpd util apachectl returns wrong status information
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: All (show other bugs)
Version: 2.0.63
Hardware: PC Linux
: P2 enhancement (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate
Depends on:
Blocks:
 
Reported: 2010-02-22 06:47 UTC by Kevin Q
Modified: 2018-11-07 21:09 UTC (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Q 2010-02-22 06:47:10 UTC
We run more than one version of apache httpd on my os.
When calling 
$ ~/apache2063/bin/apachectl status
$ ~/apache2059/bin/apachectl status
under different local installed version(2.0.63/2.0.59),
but returns same information about 2.2.12(which default installed on my system).

We think this is a bug because
$ ~/apache2063/bin/apachectl start/stop/restart
will control only local version of httpd
but 
$ ~/apache2063/bin/apachectl status
returns information of system version of httpd,
isn't it strange?

We tested 2.2.x have the same problem.
Comment 1 Eric Covener 2010-02-22 12:21:45 UTC
Changing to enhancement, apachectl doesn't try too hard to figure out what host/port server-status might be accessable on.  The manual suggests setting the URL to be queried if the default doesn't work out for you.
Comment 2 William A. Rowe Jr. 2018-11-07 21:09:58 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.