sssd won't start
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
sssd (Ubuntu) |
Fix Released
|
High
|
Sergio Durigan Junior | ||
Focal |
Fix Released
|
Medium
|
Sergio Durigan Junior | ||
Groovy |
Fix Released
|
Medium
|
Sergio Durigan Junior | ||
Hirsute |
Fix Released
|
High
|
Sergio Durigan Junior |
Bug Description
[ Impact ]
Starting from Groovy, sssd became a dependency of ubuntu-desktop. This means that Ubuntu users who install the Desktop version will automatically get sssd installed in their systems.
By default, sssd does not try to make any assumptions about the user setup, and does not install a configuration file under /etc/sssd. However, the sssd daemon requires a valid configuration file (/etc/sssd/
These two facts are now causing pristine Groovy installations to display error messages in the log files (journalctl, during boot time) saying that sssd has failed to start. This can cause (and has caused) confusion to the users, who might assume that there is something wrong with their systems.
[ Test Case ]
The test case is simple: you just have to install Ubuntu Groovy Desktop and look at journalctl when you boot the system. You will find error messages like these:
Dec 10 15:06:01 groovy-desktop sssd[800]: SSSD couldn't load the configuration database [2]: No such file or directory.
Dec 10 15:06:01 groovy-desktop systemd[1]: sssd.service: Main process exited, code=exited, status=
Dec 10 15:06:01 groovy-desktop systemd[1]: sssd.service: Failed with result 'exit-code'.
Dec 10 15:06:01 groovy-desktop systemd[1]: Failed to start System Security Services Daemon.
...
With the proposed solution, the user will still see warnings about the sssd socket-activated unit files not being able to start, but no more error messages saying that sssd could not start.
[ Regression Potential ]
The regression potential is low.
* Unless there is a hidden bug in the way systemd performs the ConditionPathExists check, if the user already has sssd active and configured in her system, the service will continue working (i.e., being properly started) as usual.
* Unless the user recompiles sssd to make it look at another configuration file (which is something not supported by Ubuntu), /etc/sssd/sssd.conf will always be the defaul place where the configuration should live.
[ Original Description ]
I am getting messages that sssd failed to start on bootup.
Here is a sample of /var/log/sssd.log
(2020-10-18 12:55:12:700497): [sssd] [main] (0x0020): SSSD couldn't load the configuration database.
(2020-10-19 19:52:22:769622): [sssd] [confdb_
(2020-10-19 19:52:22:769957): [sssd] [get_monitor_
(2020-10-19 19:52:22:770016): [sssd] [get_monitor_
Here is what sssd.service says:
● sssd.service - System Security Services Daemon
Loaded: loaded (/lib/systemd/
Active: failed (Result: exit-code) since Mon 2020-10-19 19:56:55 PDT; 4min 50s ago
Process: 721 ExecStart=
Main PID: 721 (code=exited, status=4)
Oct 19 19:56:55 260-home systemd[1]: sssd.service: Scheduled restart job, restart counter is at 5.
Oct 19 19:56:55 260-home systemd[1]: Stopped System Security Services Daemon.
Oct 19 19:56:55 260-home systemd[1]: sssd.service: Start request repeated too quickly.
Oct 19 19:56:55 260-home systemd[1]: sssd.service: Failed with result 'exit-code'.
Oct 19 19:56:55 260-home systemd[1]: Failed to start System Security Services Daemon.
I'm not familiar with System Security Services, and don't know if this is something to worry about or not, but I think at least it is slowing my boot time.
Rob
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: sssd 2.3.1-3
ProcVersionSign
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 19 20:14:32 2020
InstallationDate: Installed on 2020-10-06 (13 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201005)
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: sssd
UpgradeStatus: No upgrade log present (probably fresh install)
Related branches
- Bryce Harrington (community): Approve
- Canonical Server Core Reviewers: Pending requested
-
Diff: 315 lines (+236/-2)7 files modifieddebian/apparmor-profile (+5/-0)
debian/changelog (+85/-0)
debian/control (+3/-2)
debian/patches/disable-fail_over-tests.patch (+56/-0)
debian/patches/fix-python-tests.patch (+83/-0)
debian/patches/series (+2/-0)
debian/rules (+2/-0)
- Bryce Harrington (community): Approve
- Canonical Server: Pending requested
-
Diff: 160 lines (+96/-37)4 files modifieddebian/changelog (+9/-0)
debian/patches/0003-Only-start-sssd.service-if-there-s-a-configuration-f.patch (+86/-0)
debian/patches/series (+1/-1)
dev/null (+0/-36)
- Bryce Harrington (community): Approve
- Canonical Server: Pending requested
-
Diff: 160 lines (+96/-37)4 files modifieddebian/changelog (+9/-0)
debian/patches/0003-Only-start-sssd.service-if-there-s-a-configuration-f.patch (+86/-0)
debian/patches/series (+1/-1)
dev/null (+0/-36)
- Bryce Harrington (community): Approve
- Canonical Server: Pending requested
-
Diff: 117 lines (+95/-0)3 files modifieddebian/changelog (+8/-0)
debian/patches/0003-Only-start-sssd.service-if-there-s-a-configuration-f.patch (+86/-0)
debian/patches/series (+1/-0)
- Lucas Kanashiro (community): Approve
- Canonical Server Core Reviewers: Pending requested
-
Diff: 80 lines (+47/-1)4 files modifieddebian/changelog (+8/-0)
debian/control (+2/-1)
debian/patches/condition-path-exists-sssd-conf.patch (+36/-0)
debian/patches/series (+1/-0)
- Lucas Kanashiro (community): Approve
- Canonical Server Core Reviewers: Pending requested
-
Diff: 80 lines (+47/-1)4 files modifieddebian/changelog (+8/-0)
debian/control (+2/-1)
debian/patches/condition-path-exists-sssd-conf.patch (+36/-0)
debian/patches/series (+1/-0)
tags: | added: patch |
tags: | added: rls-gg-incoming |
tags: | added: server-next |
Changed in sssd (Ubuntu Groovy): | |
status: | New → Triaged |
assignee: | nobody → Sergio Durigan Junior (sergiodj) |
Changed in sssd (Ubuntu Hirsute): | |
assignee: | nobody → Sergio Durigan Junior (sergiodj) |
Changed in sssd (Ubuntu Groovy): | |
importance: | Undecided → Medium |
description: | updated |
Changed in sssd (Ubuntu Focal): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → Sergio Durigan Junior (sergiodj) |
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.