CSF bug with whm-server-status
Greetings,
It appears that cPanel has deprecated:
http://127.0.0.1/whm-server-status
...for:
http://127.0.0.1/server-status
...which is fine, sans that in:
/etc/csf/csf.conf
...the default for PT_APACHESTATUS is:
PT_APACHESTATUS = "http://127.0.0.1/whm-server-status"
...so when you get, say, a load warning from CSF and it includes/attaches apachestatus.html instead of that file actually containing the apache status scoreboard, you just get:
Unable to retrieve Apache Server Status [http://127.0.0.1/whm-server-status?key=REDACTED] - Unable to download: Not Found
Would think that either the legacy status path should be redirected or the next version of CSF should update that CSF default path IF it's still set to the legacy status page.
-
Hey there! This is a known issue we're tracking through case CPANEL-54008 and we hope to have this fixed as part of the next CSF update!
I've linked this thread to the case so I'll be sure to post an update if I hear anything on my end.
1 -
Thanks Rex Hatt
0 -
Anytime!
0 -
Any idea when this is likely to be fixed? The apache status reports are very useful for seeing what was causing the high load average, and at present we can't take any action to try to stop the problems as we don't know what is causing them. It seems like this would be fairly straight-forward to correct.
1 -
Let me reach out to the team and I'll let you know what I find!
0 -
It looks like the specific CSF team leader I wanted to speak with is out today so I may not hear about this until tomorrow, but I'll be sure to post then.
0 -
This worked for us, first edit csf.conf and change :
PT_APACHESTATUS = "http://127.0.0.1/whm-server-status"
to read:
PT_APACHESTATUS = "http://127.0.0.1/server-status"
Save and restart csf
Next, in WHM open the Apache configuration and click on the include editor, in the pre-main drop down menu select your apache version and add the following:
<Location /server-status>
SetHandler server-status
Require local
Require ip 127.0.0.1
</Location>save and restart apache.
Done!
0 -
chris matthews - that does indeed work, but we want to ensure that there is a long-term solution without the need to adjust files on the server.
Our team is still looking into this one on my end.
0 -
@ cPRex Adjusting files on servers is something system admins frequently do to make things work :)
We look forward to seeing that long term solution when your team gets around to it.
0 -
hello,
We have cpanel 136.0.33 and same issue here:
STATS: Unable to retrieve Apache Server Status [http://127.0.0.1/whm-server-status?auto&key=REDACTED] - Unable to download: Not Found
Any updates on this matter?
Regards,
Reginaldo Bray
0 -
It looks like we have a fix in place and it's going through final testing now.
0 -
Thank you cPRex for the update.
I will wait for the fix.
Best regards,
Reginaldo Bray
0 -
I’m seeing this same issue on two cPanel servers running the cPanel nginx reverse proxy.
Both servers were fine until
cpanel-csf 16.31-1.2.1.cpanelwas installed automatically on September 3. Immediately after LFD restarted, the once-per-minuteSTATS: Unable to retrieve Apache Server Status ... Not Founderrors began.On these servers nginx listens on 80/443 and Apache listens on 8080/8443.
Directly querying the existing Apache status endpoint works:
curl http://127.0.0.1:8080/whm-server-status?autoreturns HTTP 200 and the normal Apache scoreboard.
I see the confirmed workaround above is to change
PT_APACHESTATUSto/server-statusand add the Apache<Location /server-status>include.With cPanel nginx installed and Apache on port 8080, should the corresponding setting be:
PT_APACHESTATUS = "http://127.0.0.1:8080/server-status"after adding that same Apache include?
I’d like to make sure I’m using the cPanel-recommended workaround for an nginx reverse-proxy setup before changing Apache configuration.
Thanks for any help!
0 -
Still an issue on cPanel 138.0.11 / cpanel-csf 16.32-1.1.1.cpanel
0
Please sign in to leave a comment.
Comments
14 comments