Bug 1215923

Summary:	Authentication failures (PAM unable to dlopen) in radiusd and saslauthd
Product:	[openSUSE] openSUSE Distribution	Reporter:	Markus Gaugusch <markus>
Component:	Basesystem	Assignee:	E-mail List <screening-team-bugs>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None	CC:	Michael.Dobrovnik
Version:	Leap 15.5
Target Milestone:	---
Hardware:	x86-64
OS:	All
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Markus Gaugusch 2023-10-04 04:10:02 UTC

Hi,
After the recent glibc update to 2.31-150300.52.2 (suspected, but reverted on one machine and not seen since then there), I receive errors in saslauthd and radiusd after ~1/2 day of operation:

2023-10-04T04:46:29.859746+02:00 zephyrus saslauthd[2187]: PAM unable to dlopen(/lib64/security/pam_env.so): /lib64/security/pam_env.so: failed to map segment from shared object
2023-10-04T04:46:29.859863+02:00 zephyrus saslauthd[2187]: PAM adding faulty module: /lib64/security/pam_env.so
2023-10-04T04:46:29.859913+02:00 zephyrus saslauthd[2187]: PAM unable to dlopen(/lib64/security/pam_localuser.so): /lib64/security/pam_localuser.so: failed to map segment from shared object
2023-10-04T04:46:29.859941+02:00 zephyrus saslauthd[2187]: PAM adding faulty module: /lib64/security/pam_localuser.so
2023-10-04T04:46:29.859963+02:00 zephyrus saslauthd[2187]: PAM unable to dlopen(/lib64/security/pam_unix.so): /lib64/security/pam_unix.so: failed to map segment from shared object
2023-10-04T04:46:29.859986+02:00 zephyrus saslauthd[2187]: PAM adding faulty module: /lib64/security/pam_unix.so
2023-10-04T04:46:29.860039+02:00 zephyrus saslauthd[2187]: PAM unable to dlopen(/lib64/security/pam_listfile.so): /lib64/security/pam_listfile.so: failed to map segment from shared object
2023-10-04T04:46:29.860092+02:00 zephyrus saslauthd[2187]: PAM adding faulty module: /lib64/security/pam_listfile.so
2023-10-04T04:46:29.860119+02:00 zephyrus saslauthd[2187]: PAM unable to dlopen(/lib64/security/pam_deny.so): /lib64/security/pam_deny.so: failed to map segment from shared object
2023-10-04T04:46:29.860151+02:00 zephyrus saslauthd[2187]: PAM adding faulty module: /lib64/security/pam_deny.so
2023-10-04T04:46:29.860190+02:00 zephyrus saslauthd[2187]: PAM unable to dlopen(/lib64/security/pam_ldap.so): /lib64/security/pam_ldap.so: failed to map segment from shared object
2023-10-04T04:46:29.860226+02:00 zephyrus saslauthd[2187]: PAM adding faulty module: /lib64/security/pam_ldap.so
2023-10-04T04:46:29.860474+02:00 zephyrus saslauthd[2187]: PAM unable to dlopen(/lib64/security/pam_cracklib.so): /lib64/security/pam_cracklib.so: failed to map segment from shared object
2023-10-04T04:46:29.860525+02:00 zephyrus saslauthd[2187]: PAM adding faulty module: /lib64/security/pam_cracklib.so
2023-10-04T04:46:29.860774+02:00 zephyrus saslauthd[2187]: PAM unable to dlopen(/lib64/security/pam_systemd.so): /lib64/security/pam_systemd.so: failed to map segment from shared object
2023-10-04T04:46:29.860824+02:00 zephyrus saslauthd[2187]: PAM adding faulty module: /lib64/security/pam_systemd.so
2023-10-04T04:46:29.860848+02:00 zephyrus saslauthd[2187]: PAM unable to dlopen(/lib64/security/pam_limits.so): /lib64/security/pam_limits.so: failed to map segment from shared object
2023-10-04T04:46:29.860873+02:00 zephyrus saslauthd[2187]: PAM adding faulty module: /lib64/security/pam_limits.so
2023-10-04T04:46:29.860895+02:00 zephyrus saslauthd[2187]: PAM unable to dlopen(/lib64/security/pam_umask.so): /lib64/security/pam_umask.so: failed to map segment from shared object
2023-10-04T04:46:29.860916+02:00 zephyrus saslauthd[2187]: PAM adding faulty module: /lib64/security/pam_umask.so
2023-10-04T04:46:29.861097+02:00 zephyrus saslauthd[2187]: PAM unable to dlopen(/lib64/security/pam_warn.so): /lib64/security/pam_warn.so: failed to map segment from shared object
2023-10-04T04:46:29.861146+02:00 zephyrus saslauthd[2187]: PAM adding faulty module: /lib64/security/pam_warn.so
2023-10-04T04:46:29.861170+02:00 zephyrus saslauthd[2187]: DEBUG: auth_pam: pam_authenticate failed: Module is unknown
2023-10-04T04:46:29.861197+02:00 zephyrus saslauthd[2187]:                 : auth failure: [user=saurabh] [service=smtp] [realm=] [mech=pam] [reason=PAM auth error]

Example for radiusd:
023-10-02T20:09:31.374648+02:00 proxy radiusd[3986]: PAM unable to dlopen(/lib64/security/pam_unix.so): libnsl.so.2: failed to map segment from shared object
2023-10-02T20:09:31.375332+02:00 proxy radiusd[3986]: PAM adding faulty module: /lib64/security/pam_unix.so
2023-10-02T20:09:31.375457+02:00 proxy radiusd[3986]: PAM unable to dlopen(/lib64/security/pam_cracklib.so): /lib64/security/pam_cracklib.so: cannot apply additional memory protection after relocation: Cannot allocate memory
2023-10-02T20:09:31.375684+02:00 proxy radiusd[3986]: PAM adding faulty module: /lib64/security/pam_cracklib.so
2023-10-02T20:09:31.375835+02:00 proxy radiusd[3986]: PAM unable to dlopen(/lib64/security/pam_systemd.so): libp11-kit.so.0: cannot change memory protections
2023-10-02T20:09:31.375957+02:00 proxy radiusd[3986]: PAM adding faulty module: /lib64/security/pam_systemd.so
2023-10-02T20:09:31.376321+02:00 proxy radiusd[3986]: PAM unable to dlopen(/lib64/security/pam_umask.so): /lib64/security/pam_umask.so: cannot change memory protections
2023-10-02T20:09:31.376486+02:00 proxy radiusd[3986]: PAM adding faulty module: /lib64/security/pam_umask.so
2023-10-02T20:09:31.376591+02:00 proxy radiusd[3986]: PAM unable to dlopen(/lib64/security/pam_warn.so): /lib64/security/pam_warn.so: failed to map segment from shared object
2023-10-02T20:09:31.376770+02:00 proxy radiusd[3986]: PAM adding faulty module: /lib64/security/pam_warn.so
2023-10-02T20:09:31.376869+02:00 proxy radiusd[3986]: PAM unable to dlopen(/lib64/security/pam_deny.so): /lib64/security/pam_deny.so: failed to map segment from shared object
2023-10-02T20:09:31.376962+02:00 proxy radiusd[3986]: PAM adding faulty module: /lib64/security/pam_deny.so

The issue can be fixed temporarily by restarting the affected process. A reboot did not help to resolve the issue.

Comment 1 Marcus Meissner 2023-10-04 13:42:39 UTC

thanks for the report, dup of bug 1215891

*** This bug has been marked as a duplicate of bug 1215891 ***