Apache status not working after customizing port

What method was used to customize the Apache listening port?

Does the status show when checked via command-line (via root access on the same system)?

Code:

# lynx -dump http://127.0.0.1/whm-server-status
# lynx -dump http://127.0.0.1:81/whm-server-status

 

Thank you for the information; I was able to confirm the symptom while researching. For reference and tracking purposes, this issue has been assigned the following internal case ID number: #26350

The described change should not be necessary, at least not in that file (not in "httpd.conf"). As a temporary fix or workaround, I would look at the following two files where the status URL is defined:

Code:

/etc/init.d/httpd
/usr/local/apache/bin/apachectl

As an example, here is what the stock-default entry is (as obtained via CLI output from "grep"):

Code:

# grep -i "^statusurl" /etc/init.d/httpd
STATUSURL="http://localhost/whm-server-status"

# grep -i "^statusurl" /usr/local/apache/bin/apachectl
STATUSURL="http://localhost/whm-server-status"

If needing to retain an edit to the above two files I recommend using one of the built-in hooks to execute a custom script or other custom commands that reapply the change or apply a patch. Here is our documentation regarding script hooks, for both cPanel/WHM and information specific to EasyApache:
cPanel/WHM Script Hooks
EasyApache Hook Scripts
Here are a few examples that could be created and used as noted in the documentation:

Code:

/scripts/preupcp
/scripts/postupcp
/scripts/preeasyapache
/scripts/posteasyapache

 

For the Apache status view in WHM I was unable to determine a desirable workaround; I believe a proper fix will depend on further inspection and examination per internal case ID #26350.

Is the Apache status viewable via command-line, using one of the init scripts?

Code:

# /etc/init.d/httpd fullstatus
# /usr/local/apache/bin/apachectl fullstatus

When testing the Apache status via WHM and while nginx is running are there any messages logged in the Apache access_log and error_log?

Code:

/usr/local/apache/logs/access_log
/usr/local/apache/logs/error_log

Assuming the Apache logs are still at their usual paths, the following command could be used to monitor for new log entries while accessing the Apache status page in WHM:

Code:

# tail -fvn0 /usr/local/apache/logs/*log

 

Regarding the Apache logs I would like to know if nginx is at least relaying the request to Apache. If it is, it will help to know what IP address is being seen by Apache; the Location directive in the Apache configuration for the URI "/whm-server-status" by default only allows requests when accessed from localhost (IP: "127.0.0.1"):

Code:

<Location /whm-server-status>
    SetHandler server-status
    Order deny,allow
    Deny from all
    Allow from 127.0.0.1
</Location>

If the request is not reaching Apache, I would consider adding a redirect in the custom nginx configuration.

 

The issue seen while using a customized Apache port, that was affecting the Apache Status page in WHM, is corrected in cPanel version 11.25.1 as of EDGE build number 45714; this newer version is presently only in EDGE (e.g., for development use and public testing). To determine when version 11.25.1 reaches other build trees such as CURRENT, RELEASE, and STABLE, please refer to the following resource on our web site: Latest cPanel/WHM Builds

Here are the relevant change log details: (Reference: cPanel Change Log)
Edge 45714 @ 2010-05-12 22:32:19

• Update apachectl and httpd init script to use correct port for status as defined in Tweak Settings
• Update WHM Apache status page to use correct port as defined in Tweak Settings

 

Important cPanel/WHM Version Number Designation Change

Please Note: Important cPanel/WHM Version Number Designation Change

As of July 28, 2010 the cPanel/WHM version number designations have been officially changed.

Version 11.25.1 is now designated 11.28 and version 11.25.2 is now designated 11.30.

These new changes were explained in some detail recently at the July 2010 - Quarterly Road map - Webinar direct from cPanel's PodCast Studio in Houston, Texas with speakers David Grega and Mario Rodriguez.

An official press release about these changes is forthcoming and can be accessed at this link as soon as it's made available to the Forum Team:
Important cPanel/WHM Version Number Designation Change (To be updated)

This post serves to update users who are subscribed to threads (where this message is posted) looking forward to upcoming enhancements in future versions of cPanel.

 

Please see the following thread: Apache status not working after customizing port - cPanel Forums

 

Friendly Moderator Note

Two threads have been merged to combine related discussion about the same topic.

 

The Apache status issue, exhibited when Apache non-SSL (HTTP) port 80 is customized via Tweak Settings, is fixed in cPanel 11.28 (AKA 11.25.1) that is currently in the EDGE release tier.