Easyapache 3 problems after revert from 4

DPNmw

• January 06, 2016 14:08

Hi, I installed easyapache4 today and it wouldn't allow my sites to load up after it completed. I saw this error while it was installing "Cpanel::Easy::Apache::Access" ignored since it does not have an RPM. "Cpanel::Easy::Apache::Fastcgi" ignored since it does not have an RPM. "Cpanel::Easy::ModCloudflare" ignored since it does not have an RPM. "Cpanel::Easy::PHP5::FileInfo" ignored since it does not have an RPM. "Cpanel::Easy::PHP5::SilenceDeprecatedPatch" ignored since it does not have an RPM. So i ran the command to revert back to easyapache3 and my sites still don't load up. When I check for apache status I get root@secure [~]# httpd --status httpd: Syntax error on line 33 of /usr/local/apache/conf/httpd.conf: Syntax error on line 2 of /etc/apache2/conf.modules.d/000_mod_mpm_event.conf: Cannot load modules/mod_mpm_event.so into server: /usr/local/apache/modules/mod_mpm_event.so: cannot open shared object file: No such file or directory root@secure [~]# Apache does not start and I can no longer select FCGI as a php handler it only shows "CGI/None" What can I do to resolve my issues?

• 

  JacobPerkins

  • January 06, 2016 19:29

  Hi, It sounds like you need to run a full easyapache 3 rebuild to get your server back up and running. The migration script, upon receiving the --revert option, will run /usr/local/cpanel/scripts/easyapache --build --skip=Apache When you migrate to EA4, we backup /usr/local/apache, and we restore it upon reversion. However if the script was interrupted by something, then it's possible that /usr/local/apache wasn't restored properly or fully, and a full easyapache build should get you back up and moving. Please let me know how it goes!

  0
• 

  DPNmw

  • January 10, 2016 17:03

  Hi, It sounds like you need to run a full easyapache 3 rebuild to get your server back up and running. The migration script, upon receiving the --revert option, will run /usr/local/cpanel/scripts/easyapache --build --skip=Apache When you migrate to EA4, we backup /usr/local/apache, and we restore it upon reversion. However if the script was interrupted by something, then it's possible that /usr/local/apache wasn't restored properly or fully, and a full easyapache build should get you back up and moving. Please let me know how it goes!

  
  I filed a ticket with cpanel support and the tech fixed it for me. His quoted response on the problem was It appears that there was an error with our internal systems causing Easy Apache 4 to fail, the fix should be pushed out to our servers shortly and you will be able to run EA4. I do apologize for the inconvenience. FCGI wasn't enabled in the exhaustive list of options. The switch to EA4, then the failure on our end, and the switch back had an error. Just one of those things that happens occasionally due to too many errors. Certainly not your fault, things that haven't been fully released yet have issues on occasion, but this helps us identify them and fix them for full stable release in the future. This is why it is always recommended to only run production systems on Fully released and supported software.
  

  0

Please sign in to leave a comment.