Plesk for Linux
kb: technical
ABT: Group A
Applicable to:
- Plesk for Linux
Symptoms
Apache does not start automatically after a server reboot.
Cause
The Apache systemd service is disabled, therefore Apache does not start on system boot:
# systemctl list-unit-files | grep httpd
httpd.service disabled
Resolution
-
Connect to the Plesk server via SSH.
-
Enable the Apache systemd service:
# systemctl enable httpd.service
Comments
4 comments
I have the same problem in plesk on debian. After a system reboot apache is not running. When i click "start" in tools > services > web server it starts properly. How can i fix it, so apache would start after system boot?
Stanisław Daszkiewicz there are might be different reasons for such a behavior. Please review /var/log/syslog and /var/log/apache2/error_log entries right after server reboot. Make sure also automatic Apache start is enabled in systemctl
Anton Maslow, there is an information about dns problems in apache error_log. As far as I can understand, there is something wrong with dns service. I suppose it is not working in the moment when apache starts because in has not already fully started and ready at this precise moment. Few seconds later it wolud probably start? (it starts if i manually start it)
[unique_id:alert] [pid 1062] (EAI 3) Temporary failure in name resolution: AH01564: unable to find IPv4 address of "***my.domain.name***"
AH00016: Configuration Failed
Am i correct? What would be the resolution in this case?
Yes, the error you mentioned likely the cause:
1. Please try to set valid hostname:
https://support.plesk.com/hc/en-us/articles/115003159249--Unable-to-start-Apache-Unable-to-find-IPv4-address-of-server-example-com
2. Or if it changes each time upon reboot try also this:
https://support.plesk.com/hc/en-us/articles/360004542834-The-etc-hosts-file-gets-overwritten-after-a-server-reboot-Your-system-has-configured-manage-etc-hosts-as-True
Please sign in to leave a comment.