Configuration change kills running Apache processes

Discussion in 'Tips/Tricks/Mods' started by bvbmedia, Apr 20, 2012.

  1. bvbmedia

    bvbmedia New Member HowtoForge Supporter

    Hi,

    First of all: ISPConfig, amazing open source solution! It runs very light and the source code looks good. :cool:

    But, I have noticed that when we do a change on the sites configuration (in the ISPCONFIG panel), Apache will be restarted. This is not so nice, cause when Apache is busy with processing some scripts those processes will be stopped. It's better to use the graceful parameter, so Apache restarts, but the running scripts will continue running.

    I fixed it by changing:

    /usr/local/ispconfig/server/mods-available/web_module.inc.php

    if($action == 'restart') {
    exec($conf['init_scripts'] . '/' . $daemon . ' restart');
    }

    To:

    if($action == 'restart') {
    exec($conf['init_scripts'] . '/' . $daemon . ' graceful');
    }
     
  2. falko

    falko Super Moderator ISPConfig Developer

    I've added this to our bugtracker, so we will check that.
     
  3. till

    till Super Moderator Staff Member ISPConfig Developer

    We used graceful before but it does not work reliably so we had to change it to restart Ispconfig uses a reload werever possible but especially operations related to ssl changes require a restart.
     
  4. styx-tdo

    styx-tdo New Member

    apache2ctl configtest && apache2ctl restart
    ;)
     
  5. till

    till Super Moderator Staff Member ISPConfig Developer

    indeed, thats what ispconfig uses and whats required for ssl changes ;)
     
  6. bvbmedia

    bvbmedia New Member HowtoForge Supporter

    The side affect of apache restart is that when running Apache in combination with mod-php the running processes are killed.

    When running apache graceful the running processes are continued. This is very useful when running cronjobs that must be runned over the web-port.
     

Share This Page