Cloned from BZ:

Description of problem:
httpd config has:

PassengerStartTimeout 600

allowing Passenger to be kicking off for that long time. However, httpd service uses systemd default timeout 90s (I think it's 90).

So there can be cases (and already is one case) when Passenger started within its timeout limit but after systemd timeout, causing systemd killed the still-starting httpd service.

Please increase httpd.service startup timeout to something more reasonable (not sure if 600s isnt too much, if it won't rather mask potential deadlocks during startup - leaving the decision of particular value to devels).

Version-Release number of selected component (if applicable):
Sat 6.2.*

How reproducible:
100%

Steps to Reproduce:
1. Install Sat6.
2. grep TimeoutStartSec /etc/systemd/system/httpd.service.d/*

Actual results:
no such timeout

Expected results:
Timeout is present with some reasonable value.

Additional info: