2

I've installed apche2 and php7.1-fpm recently and added them to boot with

systemctl enable apache2
systemctl enable php7.1-fpm

After rebooting the system systemctl status shows the following:

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'.

If I start the services by hand everything works fine. Where is the issue?

GAD3R
  • 63,407
  • 31
  • 131
  • 192
Josh
  • 135
  • 1
  • 9

1 Answers1

7

Looks like the question is pretty old, but for someone like me who encounter the same problem - there are a

DefaultTimeoutStartSec
DefaultTimeoutStopSec

options responsible for that in the global /etc/systemd/system.conf.

Or the

TimeoutStartSec
TimeoutStopSec

in the individual .service files linked in /etc/systemd/system, which in my system was by default set to 15s. Changing to 60s solved the problem

rimek
  • 71
  • 1
  • 2