Re: Slow Startup with nss_ldap
Hi Anyways, after setting slapd to start before in rc.d, I was able to get my machine up. Slapd would still give me the following error: nss_ldap: could not search LDAP server - Server is unavailable However slapd is up and running by the time I get a login prompt so the important issue is out of the way. Now to figure out why that message comes up. Pramod Venugopal [EMAIL PROTECTED] On Aug 12, 2006, at 9:00 AM, Atom Powers wrote: Try starting ldap first, using rc.d magic. Try putting 'bind-policy soft" (sp?) in your nss_ldap.conf, ldap.conf On 8/11/06, Pramod Venugopal <[EMAIL PROTECTED]> wrote: Hello everyone, I have a FreeBSD 6.1-RELEASE system configured as a Samba Server with an OpenLDAP backend. I have configured nss_ldap to allow local user authentication via LDAP. However if I reboot this machine for any reason, the bootup process gets stuck on named. If I Ctrl-C out of named, it gets stuck again on slapd. However, if i put the original nsswitch.conf back, the machine boots up fine and i have to copy the old nsswitch.conf back to get local user authentication. Here is the updated nsswitch.conf file: --8<-- passwd: files ldap group: files ldap --8<-- From looking at the logs, it looks like these processes are trying to access the ldap server which isnt up since it has not started yet. Is there any way I can get past this (other than using the original nsswitch.conf and changing back manually)? Thanks in advance, Pramod Venugopal ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions- [EMAIL PROTECTED]" -- -- Perfection is just a word I use occasionally with mustard. --Atom Powers-- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions- [EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Slow Startup with nss_ldap
Try starting ldap first, using rc.d magic. Try putting 'bind-policy soft" (sp?) in your nss_ldap.conf, ldap.conf On 8/11/06, Pramod Venugopal <[EMAIL PROTECTED]> wrote: Hello everyone, I have a FreeBSD 6.1-RELEASE system configured as a Samba Server with an OpenLDAP backend. I have configured nss_ldap to allow local user authentication via LDAP. However if I reboot this machine for any reason, the bootup process gets stuck on named. If I Ctrl-C out of named, it gets stuck again on slapd. However, if i put the original nsswitch.conf back, the machine boots up fine and i have to copy the old nsswitch.conf back to get local user authentication. Here is the updated nsswitch.conf file: --8<-- passwd: files ldap group: files ldap --8<-- From looking at the logs, it looks like these processes are trying to access the ldap server which isnt up since it has not started yet. Is there any way I can get past this (other than using the original nsswitch.conf and changing back manually)? Thanks in advance, Pramod Venugopal ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- -- Perfection is just a word I use occasionally with mustard. --Atom Powers-- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Slow Startup with nss_ldap
Hello everyone, I have a FreeBSD 6.1-RELEASE system configured as a Samba Server with an OpenLDAP backend. I have configured nss_ldap to allow local user authentication via LDAP. However if I reboot this machine for any reason, the bootup process gets stuck on named. If I Ctrl-C out of named, it gets stuck again on slapd. However, if i put the original nsswitch.conf back, the machine boots up fine and i have to copy the old nsswitch.conf back to get local user authentication. Here is the updated nsswitch.conf file: --8<-- passwd: files ldap group: files ldap --8<-- From looking at the logs, it looks like these processes are trying to access the ldap server which isnt up since it has not started yet. Is there any way I can get past this (other than using the original nsswitch.conf and changing back manually)? Thanks in advance, Pramod Venugopal ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"