php upgrade failed

xml

• April 12, 2014 09:32

Hello I was trying to upgrade from php5.3.27 to php5.4.27 using easyapache UI the I got this error message and the rebuild failed [PHP] chmod 755 /usr/local/apache/modules/mod_bwlimited.so apxs:Error: Activation failed for custom /usr/local/apache/conf/httpd.conf file.. apxs:Error: At least one `LoadModule' directive already has to exist.. !! '/usr/local/apache/bin/apxs -i -a -c ../mod_bwlimited.c' failed with exit code '256' !! !! Restoring original working apache !! !! Executing '/scripts/initsslhttpd' !! !! Restarting 'httpd' ... !! !! 'httpd' restart complete. !! Building global cache for cpanel...Done !! Executing '/scripts/initfpsuexec' !! !! Executing '/scripts/initsslhttpd' !! !! Executing '/scripts/fixmailman' !! !! Executing '/scripts/update_apachectl' !! !! Executing '/scripts/enablefileprotect' !! !! Verbose logfile is at '/usr/local/cpanel/logs/easy/apache/build.1397311335' !! [/PHP] any idea how to fix? WHM 11.42.0.24 apache 2.2 No nginx installed

• 

  cPanelMichael

  • April 14, 2014 15:03

  Hello :) You mentioned that Nginx is not installed. Was it installed in the past? Do you notice any content added to the /scripts/after_apache_make_install file? Thank you.

  0
• 

  xml

  • April 14, 2014 17:53

  [QUOTE] It appears that moving the compiled rogue bwlimited.so modules out of the apache modules directory and rebuilding the apache configuration allowed it to generated a good apache build that did not include the LoadModule directive, this appears to have resolved the conflict in EasyApache and allowed it to complete. Please let us know if you require any further details or assistance with this request. Sky Bly Technical Analyst II Migrations Specialist cPanel, Inc.
  Thanks to Sky Bly and all cPanel staff

  0
• 

  cPanelMichael

  • April 14, 2014 19:04

  I am happy to see the issue is now resolved. Note that for others experiencing this issue, it's a good idea to review "/scripts/after_apache_make_install" as entries within this file from Nginx implementation are the primary cause of the reported error message. Thank you.

  0

Please sign in to leave a comment.