Comment 9 for bug 1572976

I seem to be hitting a similar issue but I *do not* see the timeout messages in the journal log; instead the deployment is stuck in Step4

in the process list I can see systemd attempting a restart of httpd

  /usr/bin/systemctl restart httpd

there is no httpd process running though; the error_log mentions the restart signal:

  [core:notice] [pid 18223] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
  [suexec:notice] [pid 18223] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
  [auth_digest:notice] [pid 18223] AH01757: generating secret for digest authentication ...
  [mpm_prefork:notice] [pid 18223] AH00163: Apache/2.4.6 (CentOS) mod_wsgi/3.4 Python/2.7.5 configured -- resuming normal operations
  [core:notice] [pid 18223] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
  [mpm_prefork:notice] [pid 18223] AH00170: caught SIGWINCH, shutting down gracefully

nothing seems to happen after that.