On May 6, 11:34 pm, Michael Ziegler <diese-a...@funzt-halt.net> wrote:
> info.avatar wrote:
> > The problem is that while booting client show me this error an enormous
> > amount of times in a loop:
>
> > udevd [1305]: nss_ldap : failed to bind ldap server
> > ldap://192.168.201.16 can't contact ldap server
>
> > Pressing Ctrl + c, the system starts and at the login ldap is working
> > correctly.

This is normal shortcomings inbetween udev, ldap and nss i libc (/etc/
nsswitch.conf)

udev is looking up some users/groups before the network is up (it has
to, to set up network devices).
If you have ldap installed, as you obviously have, it will try to
connect to the server. Which it can't do
untill network is set up. This was a big problem for me for a while.
I hade to have a script that switched
two versions of /etc/nsswitch.conf. One without ldap when booting,
and one with ldap which was copied
when network was set up.
The problem was that ldap-library never timed out. Now it is, and it
is those warnings you see (unless you run
an old Debian, in which case you have the problem I hade).

> Make sure your nsswitch.conf lists ldap as the very last entry in each
> row, because on boot, nsc tries to determine udev's UID. If ldap is then
> listed before files in nsswitch.conf, nsc tries to connect to LDAP via a
> network device that is not yet running.

That doesn't solve this problem, as I described here. It is all
described in Debian bug database at libpam-ldap and/or libnss-ldap

>
> Regards
> Michael

Good luck, Jackson