Comment 45 for bug 155947

--On Wednesday, January 23, 2008 10:13:10 PM +0000 Jamie Strandboge
<email address hidden> wrote:

> This may be related to https://bugs.launchpad.net/ubuntu/+source/libnss-
> ldap/+bug/51315. Can people test the solutions there (look towards the
> bottom)?

The symptom that is reported here is not the problem that I was seeing.

Here is a quick summary of what I saw.

  1. Successfully running libpam_ldap and libnss_ldap on gutsy
  2. Aptitude upgrade merged two config files into /etc/ldap.conf
  3. Reboot of the system runs to login prompt, BUT no scripts in
     /etc/init.d are run after the kernel log.

The solution was to change the host line in the /etc/ldap.conf file to:

  host 127.0.0.1 123.123.123.123

where 123.123.123.123 is a working ldap server in the network. This works
okay, but it is really unclear how you bring up the first server with ldap
and libnss_ldap. This has been a problem for long enough I am quickly
coming to the opinion that you should _never_ run the ldap server on a
system that is using libnss_ldap. This is a big pain in the neck since two
sites that I manage are configured to have a local ldap replica to improve
reliability. Currently, running a local ldap server is fine if you can
ever get the system booted.

Bill

+---------------------------------------------------------------------
| Bill MacAllister <email address hidden>
| Systems Programmer, ITS Unix Systems, Stanford University