Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!

why does EasyApache kill HTTP?

Discussion in 'EasyApache' started by SoftDux, Oct 15, 2009.

  1. SoftDux

    SoftDux Well-Known Member

    May 27, 2006
    Likes Received:
    Trophy Points:
    Johannesburg, South Africa
    cPanel Access Level:
    Root Administrator

    I'm just curious, why does EasyApache break / kill HTTP altogether when it rebuilds?

    Is it not rather possible to build the new Apache in a temp location, and only move it to the actually Apache location(s) when the build is done?
  2. cPanelDon

    cPanelDon cPanel Quality Assurance Analyst Staff Member

    Nov 5, 2008
    Likes Received:
    Trophy Points:
    Houston, Texas, U.S.A.
    cPanel Access Level:
    DataCenter Provider
    When EasyApache runs it first makes a backup of your existing Apache installation, during this time your existing Apache install is relocated to allow for the new build to install. After initialization of a new build process the first thing EasyApache compiles is Apache and your Apache modules, followed by compiling PHP and any selected PHP options and modules. If when the new build completes there is a failure EasyApache will then be able to immediately revert your Apache installation to the previous version.

    It is entirely possible and normal for Apache be able to continue running in memory while EasyApache compiles a new Apache and PHP installation; however, if a manual or an inadvertent restart of Apache/httpd is attempted before the new build is completed then Apache/httpd will appear offline until EasyApache attempts to restart the new install near the end of the build process. Certain actions could trigger a restart of Apache/httpd, including third-party monitoring tools, the creation of a new account, the removal of an account, adding or removing domains in cPanel, including parked domains, add-on domains, and sub-domains.

    To minimize the likelihood of an inadvertent Apache restart I would run EasyApache during off-peak hours or during a time where the server is under minimal utilization; it is entirely possible for Apache to keep running all the way through a new build to the point where EasyApache performs its own restart and final build tests. I would also ensure to temporarily disable third-party service monitoring tools that may directly trigger a restart.
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice