[SSSD-users]Re: Issue with SSSD and NSS user/group resolution, sort of

[Alexey Tikhonov]

On Sat, Feb 15, 2025 at 10:46 AM Alexey Tikhonov 
wrote:
> On Fri, Feb 14, 2025 at 11:10 PM Lawrence Kearney via sssd-users <
> [e-mail]> wrote:
> > Alex,
> > Sure. As a base, the daemon status and original call:
>
> Thanks. At least, it does talk to SSSD:
> connect(4, {sa_family=AF_UNIX, sun_path="/var/lib/sss/pipes/nss"}, 110) = 0
> ...
> sendto(4, "\24\0\0\0\22\0\0\0\0\0\0\0\0\0\0\0", 16, MSG_NOSIGNAL, NULL, 0)
> = 16  --  SSS_NSS_GETPWUID
> sendto(4, "\363\372\256\1", 4, MSG_NOSIGNAL, NULL, 0) = 4  --  UID being
> looked up, but if I parse this correctly, this is not 28244723, but
> 179959027
> read(4, "\30\0\0\0\22\0\0\0\0\0\0\0\0\0\0\0", 16) = 16  --
>  response(SSS_NSS_GETPWUID), no server error
> read(4, "\0\0\0\0\0\0\0\0", 8)         = 8  --  NSS_STATUS_NOTFOUND
>
> --  if I parse strace correctly, it looks up a wrong id... sure thing
> SSSD replies NOTFOUND
> Next it continues with the next provider from nsswitch.conf - systemd -
> but payload is cut so we can't say it it looks up the same (wrong?) id
> there:
> connect(6, {sa_family=AF_UNIX,
> sun_path="/run/systemd/userdb/io.systemd.DynamicUser"}, 45) = 0
> ...
> sendto(6, "{\"method\":\"io.systemd.UserDataba"..., 116,
> MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 116
>
> The same with SSS_NSS_GETGRGID: it looks up "r\334\261\1" == 180729970,
> not 28433522...
>
> I've also asked for 'ltrace' of the same command. Have you got it?

`ltrace ls -l /home/lck`