Bug 50441 – univention-system-setup-boot.service flagged as failed: Start operation timed out

Bug 50441 - univention-system-setup-boot.service flagged as failed: Start operation timed out


Summary:	univention-system-setup-boot.service flagged as failed: Start operation timed...

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	System setup
Version:	UCS 4.4
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:	50410
	Show dependency tree / graph

Reported:	2019-11-01 13:15 CET by Philipp Hahn
Modified:	2020-07-04 10:22 CEST (History)
CC List:	0 users

See Also:	45815 44565
What kind of report is it?:	Bug Report
What type of bug is this?:	3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	1: Nuisance – not a big deal but noticeable
User Pain:	0.034
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Philipp Hahn

2019-11-01 13:15:02 CET

All our EC2 AMIs show this during the initial boot into USS:

root@unassigned-hostname:~# systemctl status univention-system-setup-boot.service 
● univention-system-setup-boot.service - LSB: Univention System Setup on boot
   Loaded: loaded (/etc/init.d/univention-system-setup-boot; generated; vendor preset: enabled)
   Active: failed (Result: timeout) since Fri 2019-11-01 12:48:42 CET; 20min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 815 ExecStart=/etc/init.d/univention-system-setup-boot start (code=killed, signal=TERM)
    Tasks: 0 (limit: 4915)
   Memory: 37.7M
      CPU: 2.762s
   CGroup: /system.slice/univention-system-setup-boot.service

Nov 01 12:43:44 unassigned-hostname chpasswd[1209]: pam_unix(chpasswd:chauthtok): password changed for __systemsetup__
Nov 01 12:43:47 unassigned-hostname su[1408]: Successful su for nobody by root
Nov 01 12:43:47 unassigned-hostname su[1408]: + ??? root:nobody
Nov 01 12:43:47 unassigned-hostname su[1408]: pam_unix(su:session): session opened for user nobody by (uid=0)
Nov 01 12:48:42 unassigned-hostname systemd[1]: univention-system-setup-boot.service: Start operation timed out. Terminating.
Nov 01 12:48:42 unassigned-hostname systemd[1]: Failed to start LSB: Univention System Setup on boot.
Nov 01 12:48:42 unassigned-hostname univention-system-setup-boot[815]: Getting ssh keys from EC2...
Nov 01 12:48:42 unassigned-hostname systemd[1]: univention-system-setup-boot.service: Unit entered failed state.
Nov 01 12:48:42 unassigned-hostname systemd[1]: univention-system-setup-boot.service: Failed with result 'timeout'.
Nov 01 12:58:17 unassigned-hostname chpasswd[1654]: pam_unix(chpasswd:chauthtok): password changed for __systemsetup__

Comment 1 Philipp Hahn

2020-07-04 10:22:22 CEST

system.units have a default Timeout; as the `univention-system-setup-boot.service` takes longer then the default timeout, that service is always flagged as "failed":

$ grep DefaultTimeoutStartSec /etc/systemd/system.conf
#DefaultTimeoutStartSec=90s

Either specify
  TimeoutStartSec=infinity
or
  Type=oneshot

TT 2020-07-01/02
TT 2020-06-25/26
TT 2020-05-20/21