#4028 sssd-kcm calls sssd-genconf which triggers nscd warning
Closed: Fixed 2 years ago by jhrozek. Opened 2 years ago by jhrozek.

Ticket was cloned from Red Hat Bugzilla (product Fedora): Bug 1721636

Description of problem:
SSSD on startup checks for the nscd socket in case the nscd caching conflicts
with the NSS maps that SSSD caches.

At the same time, sssd-kcm uses the sssd binary to regenerate the configuration
database. And even if sssd runs in this --genconf mode, it still runs the nscd
check. This is not needed and can be confusing, because it's completely OK to
run sssd-kcm but not the rest of SSSD.

Version-Release number of selected component (if applicable):
sssd-2.2.0

How reproducible:
always

Steps to Reproduce:
1. systemctl restart sssd-kcm
2.
3.

Actual results:
"""
NSCD socket was detected and seems to be configured to cache some of the
databases controlled by SSSD [passwd,group,netgroup,services]. It is
recommended not to run NSCD in parallel with SSSD, unless NSCD is configured
not to cache these
"""
in syslog.

Expected results:
silence is syslog

Additional info:
Reported at https://bugzilla.redhat.com/show_bug.cgi?id=903648#c9

Metadata Update from @jhrozek:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1721636

2 years ago

Metadata Update from @jhrozek:
- Issue assigned to jhrozek

2 years ago

Metadata Update from @jhrozek:
- Issue tagged with: PR, bug

2 years ago

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

2 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.3

2 years ago

Could you also backport patch to 1.16 branch ?

In theory yes, but I don't think it's needed? The code that triggers this bug is that sssd-kcm.service calls sssd --genconf with recent releases to make sure that changes to sssd.conf's kcm service are reflected in confdb and admins can only update [kcm] section without knowing to restart sssd serice. And this code is only in master, so I'm not sure backporting this patch would help.

IOW, I'm not against it, but I'm not sure if would fix any user visible bug.

In theory yes, but I don't think it's needed? The code that triggers this bug is that sssd-kcm.service calls sssd --genconf with recent releases to make sure that changes to sssd.conf's kcm service are reflected in confdb and admins can only update [kcm] section without knowing to restart sssd serice. And this code is only in master, so I'm not sure backporting this patch would help.
IOW, I'm not against it, but I'm not sure if would fix any user visible bug.

Backporting related patches would be welcomed as well. (#3862 #3439)

Or you might wait for bug reports from stable distributions which stick with 1.16 (e.g. #4031)

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/4998

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.

Metadata