PAM unable to dlopen(/lib/security/pam_listfile.so)
PAM [dlerror: /lib/security/pam_listfile.so: cannot open shared object file: No such file or directory]
PAM adding faulty module: /lib/security/pam_listfile.so
PAM unable to dlopen(/lib/security/pam_pwdb.so)
PAM [dlerror: /lib/security/pam_pwdb.so: cannot open shared object file: No such file or directory]
PAM adding faulty module: /lib/security/pam_pwdb.so
It’s normal as all *.so files for pam are in /lib64/security/ rather than /lib/security
Is it safe to symlinks /lib64/security to /lib/security ?
Something like
ln -sfd /lib64/security /lib/security
The only thing is that in /lib/security I have a file (poor alone file)
-pam_ccreds.so
I could copy it to /lib64/security first then do the symlink
What do you think about this ?
Do you already encounter this pbm ?
You can often install both 32 and 64 bit versions of libs/binaries Pascal. So I’d check for the 32 bit versions of the libs you need before symlinking as symlinking may confuse programs that are expecting a 32 bit lib in /lib/security.
pam_ccreds-1-3 should be 32 bits (as it was the only one in lib/security/)
These PAM errors arrived when there is an authentifiction error in PROFTPD only.
I’m not sure which 32 bits libs/bin I have to install ? All others pam rpms ?
For example
[root@obiwan ~]# yum list pam-0.77-66.14
Setting up repositories
Reading repository metadata in from local files
Installed Packages
pam.x86_64 0.77-66.14 installed
Available Packages
pam.i386 0.77-66.14 base
I can install this 32 bits pam safely, knowing it will also install the dependencies ?
=============================================================================
Package Arch Version Repository Size
=============================================================================
Installing:
pam i386 0.77-66.14 base 1.8 M
Installing for dependencies:
audit-libs i386 1.0.12-1.EL4 base 33 k
cracklib i386 2.7-29 base 26 k
cracklib-dicts i386 2.7-29 base 1.3 M
glib2 i386 2.4.7-1 base 476 k
I have installed all pam 32 bits shared objects. So now I have in /lib/security/ the needed files.
But I still have the same error
PAM unable to dlopen(/lib/security/pam_listfile.so)
PAM [dlerror: /lib/security/pam_listfile.so: cannot open shared object file: No such file or directory]
PAM adding faulty module: /lib/security/pam_listfile.so
PAM unable to dlopen(/lib/security/pam_pwdb.so)
PAM [dlerror: /lib/security/pam_pwdb.so: cannot open shared object file: No such file or directory]
PAM adding faulty module: /lib/security/pam_pwdb.so
/lib/security/pam_listfile.so exists and has these auth
ls -al /lib/security/
-rwxr-xr-x 1 root root 15656 Jan 1 23:08 pam_listfile.so
I’d try stracing the process that is throwing the error so you can see what exact system calls are occuring Pascal. You can attach to a running process if it’s a daemon by doing: