Your message dated Fri, 16 Nov 2007 09:53:39 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#451508: libpam-modules: PAM adding faulty module:
/lib/security/pam_unix.so
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: libpam-modules
Version: 0.99.7.1-5
Severity: normal
I recently noticed in my syslog, many error messages I hadn't seen before :
>Nov 16 14:15:01 ns1 CRON[9925]: PAM unable to dlopen(/lib/security/pam_unix.so)
>Nov 16 14:15:01 ns1 CRON[9925]: PAM [dlerror: /lib/security/pam_unix.so:
>symbol pam_modutil_getlogin, version LIBPAM_MODUTIL_1.0 not defined in file
>libpam.so.0 with link time reference]
>Nov 16 14:15:01 ns1 CRON[9925]: PAM adding faulty module:
>/lib/security/pam_unix.so
>Nov 16 14:15:01 ns1 CRON[9925]: PAM unable to dlopen(/lib/security/pam_env.so)
>Nov 16 14:15:01 ns1 CRON[9925]: PAM [dlerror: /lib/security/pam_env.so: symbol
>pam_syslog, version LIBPAM_EXTENSION_1.0 not defined in file libpam.so.0 with
>link time reference]
>Nov 16 14:15:01 ns1 CRON[9925]: PAM adding faulty module:
>/lib/security/pam_env.so
>Nov 16 14:15:01 ns1 CRON[9925]: PAM unable to
>dlopen(/lib/security/pam_limits.so)
>Nov 16 14:15:01 ns1 CRON[9925]: PAM [dlerror: /lib/security/pam_limits.so:
>symbol pam_syslog, version LIBPAM_EXTENSION_1.0 not defined in file
>libpam.so.0 with link time reference]
>Nov 16 14:15:01 ns1 CRON[9925]: PAM adding faulty module:
>/lib/security/pam_limits.so
>Nov 16 14:15:01 ns1 CRON[9925]: Module is unknown
I doesn't seems to have much impact on my box, as all seems to run as usual...
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core)
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash
Versions of packages libpam-modules depends on:
ii libc6 2.6.1-1+b1 GNU C Library: Shared libraries
ii libdb4.6 4.6.19-1 Berkeley v4.6 Database Libraries [
ii libpam0g 0.99.7.1-5 Pluggable Authentication Modules l
ii libselinux1 2.0.15-2+b1 SELinux shared libraries
libpam-modules recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, Nov 16, 2007 at 02:20:20PM +0100, [EMAIL PROTECTED] wrote:
> Package: libpam-modules
> Version: 0.99.7.1-5
> Severity: normal
> I recently noticed in my syslog, many error messages I hadn't seen before :
> >Nov 16 14:15:01 ns1 CRON[9925]: PAM unable to
> >dlopen(/lib/security/pam_unix.so)
> >Nov 16 14:15:01 ns1 CRON[9925]: PAM [dlerror: /lib/security/pam_unix.so:
> >symbol pam_modutil_getlogin, version LIBPAM_MODUTIL_1.0 not defined in file
> >libpam.so.0 with link time reference]
> >Nov 16 14:15:01 ns1 CRON[9925]: PAM adding faulty module:
> >/lib/security/pam_unix.so
> >Nov 16 14:15:01 ns1 CRON[9925]: PAM unable to
> >dlopen(/lib/security/pam_env.so)
> >Nov 16 14:15:01 ns1 CRON[9925]: PAM [dlerror: /lib/security/pam_env.so:
> >symbol pam_syslog, version LIBPAM_EXTENSION_1.0 not defined in file
> >libpam.so.0 with link time reference]
> >Nov 16 14:15:01 ns1 CRON[9925]: PAM adding faulty module:
> >/lib/security/pam_env.so
> >Nov 16 14:15:01 ns1 CRON[9925]: PAM unable to
> >dlopen(/lib/security/pam_limits.so)
> >Nov 16 14:15:01 ns1 CRON[9925]: PAM [dlerror: /lib/security/pam_limits.so:
> >symbol pam_syslog, version LIBPAM_EXTENSION_1.0 not defined in file
> >libpam.so.0 with link time reference]
> >Nov 16 14:15:01 ns1 CRON[9925]: PAM adding faulty module:
> >/lib/security/pam_limits.so
> >Nov 16 14:15:01 ns1 CRON[9925]: Module is unknown
> I doesn't seems to have much impact on my box, as all seems to run as usual...
You need to restart cron on your system.
There's upgrade code in libpam0g 0.99.7.1-3 and above that should have
already prompted you to do this; if you opted not to, there's nothing more
the package can do to help.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
--- End Message ---
