[Bug 387576] Re: Cannot use LDAP accounts on armel build; has incorrect symlink or /lib/nss_ldap.so incorrectly supplied

Bug Watch Updater 387576 at bugs.launchpad.net
Mon Dec 2 13:03:26 UTC 2013


** Changed in: libnss-ldap (Debian)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to libnss-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/387576

Title:
  Cannot use LDAP accounts on armel build; has incorrect symlink or
  /lib/nss_ldap.so incorrectly supplied

Status in nss_ldap:
  Fix Released
Status in “libnss-ldap” package in Ubuntu:
  Fix Released
Status in “libnss-ldap” package in Debian:
  Fix Released

Bug description:
  Binary package hint: libnss-ldap

  This is a report and manual work around:

  Installed info:
  Jaunty on an NSLU2 ARM 
  Description:	Ubuntu 9.04
  Release:	9.04
  2.6.28-11-ixp4xx armv5tel

  Package:
  ii  libnss-ldap                       261-2.1ubuntu1                    NSS module for using LDAP as a naming service

  
  Looks like the build for the armel (NSLU2 specifically)  provides an incomplete symlink'd or unfinished build which doesn't allow LDAP user accounts to operate locally. A Ubuntu Jaunty i686 client with libnss_ldap installed and configured to use the NSLU2 servers works ok, but other remote NSLU2 don't.

  All 'getent passwd' operation executed on NSLU2 (local or remote) only
  list local accounts. Jaunty  i686 to NSLU2 'getent passwd' works.

  Found on NSLU2 that a library symlink in /usr/lib/libnss_ldap.so
  referenced a non-existant /lib/libnss_ldap.so.2

  lrwxrwxrwx root/root         0 2008-11-19 08:32 ./usr/lib/libnss_ldap.so -> /lib/libnss_ldap.so.2
  root at J-SLUG00:/lib# find /lib/*nss*ldap* -ls 
  382776    0 lrwxrwxrwx   1 root     root           13 Jun 12 15:54 /lib/nss_ldap.so -> nss_ldap.so.1
  382775   80 -rw-r--r--   1 root     root        76028 Nov 19  2008 /lib/nss_ldap.so.1
  root at J-SLUG00:/lib# 

  There exists a file called /lib/nss_ldap.so.1,  compared the entry
  points with a Jaunty i686 build libnss_ldap.so.2 and they match.

  Manual installed workaround solution:
    
    Create a symlink for libnss_ldap.so.2 -> nss_ldap.so.1 in /lib

  
  root at J-SLUG00:/ # getent passwd | grep john
  root at J-SLUG00:/ # cd /lib
  root at J-SLUG00:/lib# 
  root at J-SLUG00:/lib# ln -s nss_ldap.so libnss_ldap.so.2
  root at J-SLUG00:/lib# getent passwd | grep john
  john:x:1000:10000:John Doe:/home/john:/bin/bash
  root at J-SLUG00:/lib# 

  
  Build logfile for ARM shows the build kit problem:

  drwxr-xr-x root/root         0 2008-11-19 08:32 ./lib/
  -rw-r--r-- root/root     76028 2008-11-19 08:31 ./lib/nss_ldap.so.1
  lrwxrwxrwx root/root         0 2008-11-19 08:32 ./usr/lib/libnss_ldap.so -> /lib/libnss_ldap.so.2
  lrwxrwxrwx root/root         0 2008-11-19 08:32 ./lib/nss_ldap.so -> nss_ldap.so.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/nss-ldap/+bug/387576/+subscriptions



More information about the foundations-bugs mailing list