https://bugzilla.suse.com/show_bug.cgi?id=1220032 https://bugzilla.suse.com/show_bug.cgi?id=1220032#c4 --- Comment #4 from Noel Power <nopower@suse.com> --- (In reply to Noel Power from comment #3)

...

(In reply to Noel Power from comment #1)

...

(In reply to Unger from comment #0)

...

Hi,

After an update of a bunch of packages last week, it wasn't possible to log in to / access samba from windows or via smbclient. In log I found:

smbd[3096]: pam_unix(samba:account): helper binary execve failed: Keine Berechtigung nscd[836]: Prüfe auf überwachte Datei »/etc/nsswitch.conf«: Datei oder Verzeichnis nicht gefunden

according to google translate this message is saying /etc/nsswitch.conf is missing so no surprise authentication isn't working

were you doing something else that might have resulted in this file getting deleted ? (or moved)

can you verify nsswitch.conf exists ?

Ok, I can confirm that there was never a /etc/nsswitch.conf since start of the journal in October 2023, so it was a bit misleading. erm I can't see how this can be, /etc/nsswitch.conf is a core file it is

(In reply to Unger from comment #2) part of glibc is should be there, unless I am mistaken if not something is really wrong ok, it seems that server installs apparently don't install /etc/nsswitch.conf anymore (although in the vm I installed to check this it did) nscd apparently has a bug against it for spitting out these errors. So yes, probably a red herring

...

Nevertheless samba worked until 2024 Feb 14 9am. At approx. 9:10 I had a huge upgrade (>1000 packages) and afterwards it was broken.

While browsing through the logs I found the following lines right before it stopped working properly:

Feb 14 09:25:25 MYHOST smbd[28626]: PAM unable to dlopen(/usr/lib64/security/pam_systemd.so): /lib64/libm.so.6: version `GLIBC_2.39' not found (required by /usr/lib64/security/pam_systemd.so) Feb 14 09:25:25 MYHOST smbd[28626]: PAM adding faulty module: /usr/lib64/security/pam_systemd.so

really looks like there is some problem with authentication related components on this system and their required version of glibc versus what is installed. Looks likely that something went very wrong during your upgrade

but those errors indeed to look like they indicating some package broken-ness. Question is what errors do you see in samba logs and journal when trying to authenticate say with smbclient. Also smb.conf would be helpful. Meanwhile I will try a fresh install again (just to see why I seem to have a /etc/nsswitch.conf) -- You are receiving this mail because: You are on the CC list for the bug.