Last night, we pushed an update to EasyApache4 wherein after the update was installed Apache service may fail to restart properly. Upon checking the Apache error log, you may see error messaging similar to the following:

Primary IP Address xxxxxxxxxx
Service Name httpd
Service Status failed
Notification The service “httpd” appears to be down.
Service Check Method The system failed to connect to this service’s TCP/IP port.
Reason Service check failed to complete
Unable to connect to port 80 on Connection refused: Died
Number of Restart Attempts 49
Startup Log /usr/sbin/httpd: symbol lookup error: /usr/sbin/httpd: undefined symbol: apr_bucket_alloc_aligned_floor
Log Messages [Tue Apr 03 22:54:35.759371 2018] [mpm_prefork:notice] [pid 12717] AH00163: Apache/2.4.29 (cPanel) OpenSSL/1.0.2n mod_bwlimited/1.4 configured -- resuming normal operations

We have pushed an update to resolve the issue for any servers that update in the future. The root cause was a failure where servers did not receive a required EasyApache rpm (ea-apr-util) during the update. If you have experienced this problem, you can resolve it immediately by following the steps below.

On your server, run the following commands

yum clean all
yum -y update

It may be that your PHP Handlers will need to be redefined as well. You can run this command to see what your current handlers are set to:

/usr/local/cpanel/bin/rebuild_phpconf --current

If you see that you have no handlers defined, you can either re-provision your PHP handlers in WHM >> MultiPHP Manager, under the PHP Handlers tab, or you can do set them with this command on the command line, replacing the $i with the ea-php## package name:

/usr/local/cpanel/bin/rebuild_phpconf --$i=cgi --$i=suphp

For example:

/usr/local/cpanel/bin/rebuild_phpconf --ea-php55=cgi --ea-php56=suphp

If you want to set all of the versions of PHP to the same handler, you can use this command:

for i in $(ls -1 /etc/scl/prefixes/|grep ^ea); do /usr/local/cpanel/bin/rebuild_phpconf --$i=cgi; done

We understand the frustration this has caused and is causing, and sincerely apologize for that. We will be updating the situation with more information as we receive it, and thank you for your patience. If you need any further help at all, feel free to open a ticket with our support team: