Bug 1152220

Summary:	Systemd ignores TimeoutSec=0 in service file
Product:	[Fedora] Fedora	Reporter:	Martin Kolman <mkolman>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	johannbg, jsynacek, lnykryn, mkolman, msekleta, s, systemd-maint, vpavlin, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1154768 (view as bug list)		Environment:
Last Closed:	2014-11-07 03:16:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1154768

Description Martin Kolman 2014-10-13 15:25:02 UTC

Description of problem:
The Initial Setup systemd service file[0] contains the TimeoutSec=0 options, but systemd still shuts-down the system after initial setup has been running for about 10-15 minutes.


Version-Release number of selected component (if applicable):
systemd
Version     : 216
Release     : 10.fc22

initial-setup
Version     : 0.3.23
Release     : 2.fc22

How reproducible:
always

Steps to Reproduce:
0a.: install rawhide with kickstart that contains "firstboot --enable"
     and don't configure user - this should make Initial Setup start after
     installation
0b.: some other service that has TimeoutSec=0 and is run during startup might
     also do 
1. leave the given service running for about 10-15 minutes

Actual results:
The system is shutdown by systemd after about 10-15 minutes, regardless
of what's going on (it even once shut down during dnf update, trashing my testing VM...).

Expected results:
The given service will run indefinitely without systemd shutting down the system.


Additional info:
This is in Journal directly before shutdown:

Oct 13 15:38:28 rawinit systemd[1]: Startup timed out.
Oct 13 15:38:28 rawinit systemd[1]: Forcibly powering off as result of failure.
Oct 13 15:38:28 rawinit systemd[1]: Shutting down.


[0] https://git.fedorahosted.org/cgit/initial-setup.git/tree/systemd/initial-setup-graphical.service

Comment 1 Zbigniew Jędrzejewski-Szmek 2014-10-13 16:04:29 UTC

I don't know if this is a consolation, but a fix for this is on the todo list [1]:

* apply start timeout during the "initializing" manager state only,
  instead of both "initializing" and "starting". maybe rename the
  timeout to "initialization-timeout" then or so?

[1] http://cgit.freedesktop.org/systemd/systemd/tree/TODO?id=HEAD#n78

Comment 2 Martin Kolman 2014-10-20 16:23:25 UTC

Does not happen in the latest F21 nightly with systemd 215-19.

Comment 3 Martin Kolman 2014-10-20 17:09:05 UTC

Looks like it got backported to F21 with 216-4.