On (14/10/19 23:04), Rowan Decker wrote:
>Following through the troubleshooting guide and getting stuck on step 3.
>https://docs.pagure.org/SSSD.sssd/users/troubleshooting.html#getent-passwd-or-id-doesn-t-print-the-user-or-getent-group-doesn-t-print-the-group-at-all
>
>Absolutely no output occurs in the sssd log (good or bad) even with [nss]
>debug_level=6. Running strace on getent I can confirm that the sss library is
>getting loaded.
>
> open("/lib64/libnss_sss.so.2", O_RDONLY) = 3
> open("/lib64/libnss3.so", O_RDONLY) = 3
> open("/lib64/libnssutil3.so", O_RDONLY) = 3
>
Which command do you test here?
Does nsswitch support modules?
Was "sss" in /etc/nsswitch.conf
Did command try to connect to sssd_nss unix socket?
"${some_prefix}/sss/pipes/nss"
>Looking in the sssd output I can see that the nss responder has started
>
> (Thu Oct 10 22:22:50 2019) [sssd[nss]] [sss_process_init] (0x0400):
> Responder initialization complete (explicitly configured)
>
>What other steps can be preformed to help debug this issue? We are using a
>custom distribution with an older gcc/glibc toolchain with the following
>configuration.
>
> ./configure \
> --with-smb-idmap-interface-version=6 \
> --without-selinux \
> --without-semanage \
> --exec-prefix=/ \
> --localstatedir=/var \
> --libexecdir=/usr/libexec \
> --datarootdir=/usr/share \
> --prefix=/. \
I am not sure whether prefix="/" is the best "/usr" is usually more suitable
but it should not influence anything if "libnss_sss.so.2" is instaled
on the right location. (but that could be solved with --enable-nsslibdir,
--enable-pammoddir)
LS
_______________________________________________
sssd-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedorahosted.org/archives/list/[email protected]
