#3576 sssd-kcm failed to start on F-27 after installing sssd-kcm
Closed: worksforme 3 years ago by jhrozek. Opened 4 years ago by jhrozek.

2017-11-16 11:50:35 simo jhrozek: I just installed sssd-kcm
2017-11-16 11:50:46 simo it dropped a file in krb5.conf.d that enables it
2017-11-16 11:50:57 simo but my user was still using KEYRING (issue 1)
2017-11-16 11:51:07 -- tscherf is now known as tscherf|afk
2017-11-16 11:51:15 simo jhrozek: so I entered as root and removed the sss db and restarted sssd
2017-11-16 11:51:22 simo jhrozek: my users started to fail to auth
2017-11-16 11:51:33 simo debug logs said KCM was not working (issue 2)
2017-11-16 11:51:55 simo checked with systemctl and it said sssd-kcm.socket is enabled, but the dameon is daed
2017-11-16 11:51:58 simo (issue 3)
2017-11-16 11:52:08 sbose simo, I'll bbiab
2017-11-16 11:52:16 simo so I now manually started (and enabled) the sssd-kcm service
2017-11-16 11:52:29 simo sbose: sure, lemme know the answer when back
2017-11-16 11:52:38 simo jhrozek: and now sssd-kcm seem to be working
2017-11-16 11:52:57 simo jhrozek: so main q. is, why sssd-kcm fails to work when socket-enabled ?
2017-11-16 11:53:24 jhrozek simo: which version do you use?
2017-11-16 11:54:11 simo jhrozek: I installed whatever is in F27 now
2017-11-16 11:55:04 simo jhrozek: 1.16.0-2.fc27
2017-11-16 11:55:32 jhrozek hm, that one should be fixed
2017-11-16 11:55:38 jhrozek * Fri Nov 03 2017 Lukas Slebodnik lslebodn@fedoraproject.org - 1.16.0-2 - Resolves: upstream#3529 - sssd-kcm Fix restart during/after upgrade
2017-11-16 11:55:40 simo jhrozek: for now other than this start issue (and the keyring reuse issue) it seem to be working.
2017-11-16 11:55:53 simo jhrozek: it was not an upgrade
2017-11-16 11:56:09 simo jhrozek: it was an install, I had no sssd-kcm installed on this machine before
2017-11-16 11:56:13 jhrozek I see
2017-11-16 11:58:18 jhrozek I guess I need to try a clean install, because on my machine the socket is enabled and running:
2017-11-16 11:58:29 jhrozek Loaded: loaded (/usr/lib/systemd/system/sssd-kcm.socket; enabled

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.0
- Issue tagged with: KCM

4 years ago

Metadata Update from @jhrozek:
- Issue priority set to: major

4 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.1 (was: SSSD 2.0)

3 years ago

I guess it doesn't make sense to keep this ticket around, there was a ton of fixes to KCM in the meantime.

Metadata Update from @jhrozek:
- Issue close_status updated to: worksforme
- Issue status updated to: Closed (was: Open)

3 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/4600

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.