FS#42188 - [vsftpd] PAM adding faulty module
Attached to Project:
Community Packages
Opened by Stefan Tatschner (rumpelsepp) - Tuesday, 30 September 2014, 10:39 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 30 September 2014, 12:25 GMT
Opened by Stefan Tatschner (rumpelsepp) - Tuesday, 30 September 2014, 10:39 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 30 September 2014, 12:25 GMT
|
Details
I have the following problem with vsftpd when trying to
login:
Sep 30 12:22:17 archvm vsftpd[31878]: PAM adding faulty module: /usr/lib/security/pam_unix.so Sep 30 12:22:17 archvm vsftpd[31878]: PAM unable to dlopen(/usr/lib/security/pam_unix.so): /usr/lib/libpthread.so.0: symbol __libc_vfork, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference Rebuilding vsftpd fixed it. |
This task depends upon
Closed by Dave Reisner (falconindy)
Tuesday, 30 September 2014, 12:25 GMT
Reason for closing: Not a bug
Additional comments about closing: Working as intended -- daemons which dlopen must be restarted after upgrading glibc to a new point release.
Tuesday, 30 September 2014, 12:25 GMT
Reason for closing: Not a bug
Additional comments about closing: Working as intended -- daemons which dlopen must be restarted after upgrading glibc to a new point release.
Comment by
Dave Reisner (falconindy) - Tuesday,
30 September 2014, 12:01 GMT
Restarting vsftpd should have fixed it as well. This is a common
error with any daemon (cron is another common example) using
dlopen after upgrading glibc.
Comment by
Stefan Tatschner (rumpelsepp) -
Tuesday, 30 September 2014, 12:03 GMT
Ah okay. Then I think this task could be closed. Sorry for the
clutter.