Replacing libnss-ldap with libnss-ldapd fails

[Rich]

I attempted to replace libnss-ldap with libnss-ldapd, as per suggestion for resolving Bug #219527.

Unfortunately, I found it unusable - it responded to all attempts to log into LDAP with the following syslog message:
nslcd: ldap_result() failed: No such object

I could not find any documentation regarding this upgrade, and was forced to revert to libnss-ldap.

[Arthur de Jong (adejong)]

Could you indicate which version of nss-ldapd causes problems for you? Ubuntu ships 0.5 in Hardy which I would recommend against using and 0.6.2 in Intrepid. The last version is a lot more stable and is better tested.

If with version 0.6.2 you still have problems, could you give some more information about your configuration (e.g. contents of /etc/nss-ldapd.conf, any output when nslcd is run in debugging mode, etc).

[Mathias Gug (mathiaz)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[bernhard (bernhardredl)]

i'm getting same error at alpha2 lucid i368

[8b4567] ldap_result() failed: No such object

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu lucid (development branch)
Release: 10.04
Codename: lucid

apt-cache policy libnss-ldap
libnss-ldap:
  Installed: (none)
  Candidate: 264-2ubuntu1
  Version table:
     264-2ubuntu1 0
        500 http://at.archive.ubuntu.com lucid/main Packages

[bernhard (bernhardredl)]

solution:
you have to change the config line
/etc/nslcd.conf

base dc=satega,dc=local/
to
base dc=satega,dc=local

(remove the / at the end)

i think the installer creates a broken on

[Arthur de Jong (adejong)]

It is strange that a slash would end u in the config. Can you include the output of the following commands in the bugreport:

hostname --domain
hostname --nis | grep '\.'
hostname --fqdn | sed -n 's/^[^.]*\.//p'
sed -n 's/^ *\(domain\|search\) *\([^ ]*\) *$/\2/p' /etc/resolv.conf
sudo grep -i base /etc/ldap/ldap.conf /etc/ldap.conf
sudu grep -i base /etc/libnss-ldap.conf /etc/pam_ldap.conf
sudo grep -i base /etc/nss-ldapd.conf /etc/nslcd.conf

These are the only things that should be used to build the default search base, perhaps one of them is in an unexpected format. After the guessing of the search base you should be prompted for a search base to confirm. Do you remmeber if there was a slash present in the shown value at configuration time?