Apache not reloading

Discussion in 'Installation/Configuration' started by Attila Mesterhazy, Jul 29, 2021.

  1. Attila Mesterhazy

    Attila Mesterhazy New Member

    Hi,

    for some reason apache is not reloading/restarting after making changes in any virtual hosts under Sites. If I manually restarts apache from SSH than the new settings are loaded. Why ISPconfig is not restarting apache?
     
  2. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    Which OS are you running? Which ISPConfig version?
     
  3. Attila Mesterhazy

    Attila Mesterhazy New Member

    I'm using Debian Buster and the latest version of ISPConfig (3.2.5)
     
  4. Chris_UK

    Chris_UK Active Member HowtoForge Supporter

    Are you running multi server?
     
  5. till

    till Super Moderator Staff Member ISPConfig Developer

  6. Attila Mesterhazy

    Attila Mesterhazy New Member

    What does multi server means? I have one Debian Buster machine with ISPconfig on it. I have web server on this machine with many domains.
     
  7. Attila Mesterhazy

    Attila Mesterhazy New Member

  8. till

    till Super Moderator Staff Member ISPConfig Developer

    Please follow the debug instructions I pointed out if you like to know why your server fails.
     
  9. Attila Mesterhazy

    Attila Mesterhazy New Member

    Thank you for your help. It seems the problem is ISPconfig wants to restart httpd.service intead of apache2. Where can I change it?

    Code:
    2021. júl. 31., szombat, 23:04:01 CEST 31.07.2021-22:04 - DEBUG - Calling function 'restartHttpd' from module 'web_module'.
    2021. júl. 31., szombat, 23:04:01 CEST 31.07.2021-22:04 - DEBUG - Restarting httpd: systemctl reload httpd.service
    2021. júl. 31., szombat, 23:04:01 CEST 31.07.2021-22:04 - DEBUG - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock
    2021. júl. 31., szombat, 23:04:01 CEST finished server.php.
     
  10. ahrasis

    ahrasis Well-Known Member

    Or it could also be due to e.g. some wrong directive you used, etc. so instead of writing it to a vhost proper file, ISPConfig keep the failed one in a vhost err file. Just a guess so debug as instructed above would help to know more.
     
  11. till

    till Super Moderator Staff Member ISPConfig Developer

    Which Operating system and operating system version do you use and which tutorial did you use to prepare your system for the ISPConfig installation?
     
  12. Attila Mesterhazy

    Attila Mesterhazy New Member

    I use Debian Buster and I followed this tutorial: https://www.howtoforge.com/perfect-server-debian-10-buster-apache-bind-dovecot-ispconfig-3-1/

    The strange thing is that on anouther machine (which is also Debain Buster with the same tutorial) it works fine. There the log sais:
    Code:
    2021.08.01 08:53     maxiz.nebet.hu     Debug     Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock     
    2021.08.01 08:53     maxiz.nebet.hu     Debug     Restarting httpd: systemctl reload apache2.service     
    2021.08.01 08:53     maxiz.nebet.hu     Debug     Calling function 'restartHttpd' from module 'web_module'.
    The diffrenece is that on the working server ISPconfig restarts apache2.service and on the not working it tries to restarts httpd.service.
     
  13. till

    till Super Moderator Staff Member ISPConfig Developer

    Maybe you have set a wrong value under System > server config > apache init script or if this field is empty, then you either have created a script /etc/init.d/httpd or /etc/httpd folder, which both should not exist on a Debian 10 system. If either of them is there, remove them. if you did not created them yourself, then you might not have started with a clean server at the beginning. Or alternatively, set the apache init script under system > server config to 'apache2'.
     
  14. Attila Mesterhazy

    Attila Mesterhazy New Member

    Thank you for your help!
    After setting apache2 under system > server config it works!
     
  15. Chris_UK

    Chris_UK Active Member HowtoForge Supporter

    Firstly, it is good to see you have sorted things out now.

    Multi server is when you run multiple servers, A primary server that hosts the ISPConfig control panel and any number of secondary servers that will each poll the primary server for updates. for example, a web server would check for changes to sites and update itself accordingly.

    I apologise if I was causing any confusion, it is easy to assume that people using the software are aware of that option.
     
    Last edited: Aug 1, 2021

Share This Page