vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello, I installed a Debian with LDAP on a server with AMD 64 bit processor. 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. how do I fix this? Thank you |
| |||
| 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. 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. Regards Michael |
| ||||
| On 6 Mag, 23:34, 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. > > 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. > > Regards > Michael Thank you for your help. Now the system doesn't loop any more. However, the error continues to remain; but after some attempts the system goes on. Regards |