Skip to main content

Update to alt-php and EA-php files, httpd restart and apache server status

bloatedstoat
  • Edited

Hello,

Last night our server updated a raft of alt-php and EA-php packages across multiple PHP versions.

The web server is up and operating as expected and serving content, however; since that upgrade and httpd restarting we're seeing the following errors reported to the LFD log:

Jun  9 21:55:23 lfd[833327]: STATS: Unable to retrieve Apache Server Status [http://127.0.0.1/whm-server-status?auto&key=REDACTED] - Unable to download: Not Found

Jun  9 21:54:27 lfd[832159]: *System Integrity* has detected modified file(s): /usr/bin/arpaname /usr/bin/bind9-config /usr/bin/delv /usr/bin/dig /usr/bin/dnstap-read /usr/bin/ea-php72 /usr/bin/ea-php73 /usr/bin/host /usr/bin/isc-config.sh /usr/bin/mdig /usr/bin/named-rrchecker /usr/bin/nslookup /usr/bin/nsupdate /usr/sbin/ddns-confgen /usr/sbin/dnssec-dsfromkey /usr/sbin/dnssec-importkey /usr/sbin/dnssec-keyfromlabel /usr/sbin/dnssec-keygen /usr/sbin/dnssec-revoke /usr/sbin/dnssec-settime /usr/sbin/dnssec-signzone /usr/sbin/dnssec-verify /usr/sbin/genrandom /usr/sbin/isc-hmac-fixup /usr/sbin/lwresd /usr/sbin/named /usr/sbin/named-checkconf /usr/sbin/named-checkzone /usr/sbin/named-compilezone /usr/sbin/named-journalprint /usr/sbin/nsec3hash /usr/sbin/rndc /usr/sbin/rndc-confgen /usr/sbin/tsig-keygen /usr/sbin/unbound-anchor /bin/arpaname /bin/bind9-config /bin/delv /bin/dig /bin/dnstap-read /bin/ea-php72 /bin/ea-php73 /bin/host /bin/isc-config.sh /bin/mdig 
/bin/named-rrchecker /bin/nslookup /bin/nsupdate /sbin/ddns-confgen /sbin/dnssec-dsfromkey /sbin/dnssec-importkey /sbin/dnssec-keyfromlabel /sbin/dnssec-keygen /sbin/dnssec-revoke /sbin/dnssec-settime /sbin/dnssec-signzone /sbin/dnssec-verify /sbin/genrandom /sbin/isc-hmac-fixup /sbin/lwresd /sbin/named /sbin/named-checkconf /sbin/named-checkzone /sbin/named-compilezone /sbin/named-journalprint /sbin/nsec3hash /sbin/rndc /sbin/rndc-confgen /sbin/tsig-keygen /sbin/unbound-anchor /usr/local/bin/ea-php72

Server version: Apache/2.4.67 (cPanel)
Server built: Jun 4 2026 12:32:08
[2026-06-09 21:53:38 +1000][/usr/local/cpanel/scripts/update-packages] 
Built /etc/apache2/conf/httpd.conf OK

 

 

Comments

21 comments

Date Votes
  • Pedro Fernandes

    I don't have LFD/CSF, but i also can see that issue, with the Apache Status showing:
    "Failed to receive status information from Apache.
    Unable to connect to local httpd server."

    Apache, however, is working fine.

    1
  • ciao70

    Hello,

    https://support.cpanel.net/hc/en-us/community/posts/41004520007703-Failed-to-receive-status-information-from-Apache

    1
  • cPRex Jurassic Moderator

    We've got an update on this one: https://support.cpanel.net/hc/en-us/articles/41084398618519-Apache-Status-not-displaying-after-upgrading-to-v136

    but I'll keep everything in the thread that ciao70 linked to ensure I don't miss anything.

    1
  • bloatedstoat

    The resolution link provided cPRex in your post above produces a 404 mate.

    0
  • Pedro Fernandes
    • Edited

    bloatedstoat

    The link was left i think by mistake.

    You only need to run:

    /scripts/rebuildhttpdconf
    /scripts/restartsrv_httpd
     
    1
  • bloatedstoat

    Pedro Fernandes thank you.

    The above didn't resolve my issue though.

    0
  • Ricardo Salvador

    Same issue Pedro Fernandes runned that mantiane error Failed to receive status information from Apache.

    0
  • cPRex Jurassic Moderator

    Correct - that link shouldn't have been there to begin with, so I've removed that now.

    If you're still seeing the error even after rebuilding Apache and re-logging in to WHM, we'd like to see a ticket.

    0
  • bloatedstoat

    Our license is provided by a Partner Supported License so I am unable to open a ticket directly using the cpanel request portal. I have opened one with our provider. Assume there will be communication between you both cPRex ?

    0
  • cPRex Jurassic Moderator

    Yes, if necessary they'll poke us!

    1
  • Ricardo Salvador

    Hello good morning all,

    Any update tell me pls .

    i saw they updated to136.0.22 but still not fixed.

    0
  • cPRex Jurassic Moderator

    Last night's update did not contain a fix for this issue, so that is to be expected.

    If you'd already rebuilt Apache and you're still seeing this it would be best to create a ticket so this can be examined directly on your system.

    0
  • bloatedstoat

    Ricardo Salvador Pedro Fernandes cPRex this post pointed me in the right direction.

    https://support.cpanel.net/hc/en-us/community/posts/41451717897879-CSF-bug-with-whm-server-status

    I edited csf.conf to correct the path and the error has now vanished.

     

    0
  • bloatedstoat

    As an aside, our license is through our server provider and they wanted $200 plus tax an hour to investigate through a ticket. Glad I waited. I didn't create the problem, paying to investigate it is absurd.

    0
  • cPRex Jurassic Moderator
    • Edited

    bloatedstoat - that's crazy, and I'm sorry to hear that's how your provider is doing business.

    0
  • Ricardo Salvador

    I have made this to fix but with tonight update is back again:
    The bug in CPANEL-53901: the key file gets regenerated correctly, but the Apache template (ea4_main.default) still generates a hardcoded <Location /whm-server-status> block — it does not inject the key as a <Location> path. So Apache has no handler for /<secret_key> and returns 404. The WHM page gets nothing back and shows the error.

    Fix — permanent, survives rebuildhttpdconf

    cPanel's pre_virtualhost_global.conf include is the correct place for this. It is not overwritten by /scripts/rebuildhttpdconf.

    Step 1 — create the include:

    KEY=$(tr -d '[:space:]' < /var/cpanel/whm_server_status_key)

    cat > /etc/apache2/conf.d/includes/pre_virtualhost_global.conf << EOF

    # WHM Apache Status - workaround CPANEL-53901

    # Generated: $(date)

    # Key: ${KEY}

    <IfModule status_module>

    <Location /${KEY}>

    SetHandler server-status

    Order deny,allow

    Deny from all

    Allow from 127.0.0.1 ::1

    <IfModule security2_module>

    SecRuleEngine Off

    </IfModule>

    <IfModule security3_module>

    modsecurity_rules 'SecRuleEngine Off'

    </IfModule>

    </Location>

    </IfModule>

    EOF

    Step 2 — test and restart:

    apachectl configtest && /scripts/restartsrv_httpd

    Step 3 — verify:

    curl -si http://127.0.0.1/$(cat /var/cpanel/whm_server_status_key)?auto | head -3

    # Should return: HTTP/1.0 200 OK

    Then reload WHM > Server Status > Apache Status — it should work.

    0
  • cPRex Jurassic Moderator

    Ricardo Salvador - we're expecting this to be resolved in version 136 at this time.  If you're still seeing issues it would be best to create a ticket as you shouldn't need a custom workaround at this point.

    0
  • Ricardo Salvador
    • Edited

    Hello,

    Right now i have version: 136.0.27

    0
  • cPRex Jurassic Moderator

    Would you be able to create a ticket so we can take a look at that system?

    0
  • Ricardo Salvador

    the issue is license is on OVH and i dont have acess to cpanel support directly

    0
  • cPRex Jurassic Moderator

    You should still be able to contact your host to have them check an issue.

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post