Project

General

Profile

Bug #21023

Increase TimeoutStartSec for httpd.service

Added by Chris Roberts over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
Performance
Target version:
-

Description

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:

Associated revisions

Revision 951f30ce (diff)
Added by Chris Roberts over 3 years ago

Fixes #21023 - Update start-timeout to 90

History

#1 Updated by The Foreman Bot over 3 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/puppet-foreman/pull/591 added

#2 Updated by Eric Helms over 3 years ago

  • Bugzilla link set to 1441212

#3 Updated by The Foreman Bot over 3 years ago

  • Pull request https://github.com/theforeman/puppet-foreman/pull/603 added

#4 Updated by Chris Roberts over 3 years ago

  • % Done changed from 0 to 100
  • Status changed from Ready For Testing to Closed

#5 Updated by The Foreman Bot over 3 years ago

  • Pull request https://github.com/theforeman/puppet-foreman/pull/606 added

Also available in: Atom PDF