Instalei o apche2 e o php7.1-fpm recentemente e os adicionei para inicializar com
systemctl enable apache2
systemctl enable php7.1-fpm
Após a reinicialização do sistema, o status systemctl mostra o seguinte:
sudo systemctl status apache2.service php7.1-fpm.service
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor
preset: enabled)
Active: failed (Result: timeout) since Mon 2017-12-25 18:53:43 CET;
10min ago
Process: 468 ExecStart=/usr/sbin/apachectl start (code=killed,
signal=TERM)
Dez 25 18:53:33 drupal-PC systemd[1]: Starting The Apache HTTP
Server...
Dez 25 18:53:43 drupal-PC apachectl[468]: AH00558: apache2: Could not
reliably determine the server's fully qualified do
Dez 25 18:53:43 drupal-PC systemd[1]: apache2.service: Start operation
timed out. Terminating.
Dez 25 18:53:43 drupal-PC systemd[1]: Failed to start The Apache HTTP
Server.
Dez 25 18:53:43 drupal-PC systemd[1]: apache2.service: Unit entered
failed state.
Dez 25 18:53:43 drupal-PC systemd[1]: apache2.service: Failed with
result 'timeout'.
● php7.1-fpm.service - The PHP 7.1 FastCGI Process Manager
Loaded: loaded (/lib/systemd/system/php7.1-fpm.service; enabled;
vendor preset: enabled)
Active: failed (Result: timeout) since Mon 2017-12-25 18:53:43 CET;
10min ago
Docs: man:php-fpm7.1(8)
Process: 463 ExecStart=/usr/sbin/php-fpm7.1 --nodaemonize --fpm-
config /etc/php/7.1/fpm/php-fpm.conf (code=killed, sig
Main PID: 463 (code=killed, signal=TERM)
Dez 25 18:53:33 drupal-PC systemd[1]: Starting The PHP 7.1 FastCGI
Process Manager...
Dez 25 18:53:43 drupal-PC systemd[1]: php7.1-fpm.service: Start
operation timed out. Terminating.
Dez 25 18:53:43 drupal-PC systemd[1]: Failed to start The PHP 7.1
FastCGI Process Manager.
Dez 25 18:53:43 drupal-PC systemd[1]: php7.1-fpm.service: Unit entered
failed state.
Dez 25 18:53:43 drupal-PC systemd[1]: php7.1-fpm.service: Failed with
result 'timeout'.
Se eu iniciar os serviços manualmente, tudo funcionará bem. Onde está o problema?
Parece que a pergunta é bem antiga, mas para alguém como eu que enfrenta o mesmo problema - há um
DefaultTimeoutStartSec
DefaultTimeoutStopSec
opções responsáveis por isso no global /etc/systemd/system.conf .
Ou o
TimeoutStartSec
TimeoutStopSec
nos arquivos individuais .service vinculados em /etc/systemd/system ,
que no meu sistema foi definido por padrão para 15s . Mudando para 60s resolveu o problema