From: Bertram Scharpf <lists@bertram-scharpf.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] LDAP: Slapd fails asking itself while startup [solved]
Date: Tue, 23 Oct 2007 03:52:03 +0200 [thread overview]
Message-ID: <20071023015203.GA15338@bart.bs.l> (raw)
In-Reply-To: <20071022042056.GA24002@bart.bs.l>
Am Montag, 22. Okt 2007, 06:20:56 +0200 schrieb Bertram Scharpf:
> Hi,
>
> Am Freitag, 19. Okt 2007, 21:09:59 +0200 schrieb Bertram Scharpf:
> > @(#) $OpenLDAP: slapd 2.3.38 (Oct 18 2007 22:12:26) $ root@myhost:/var/tmp/portage/net-nds/openldap-2.3.38/work/openldap-2.3.38/servers/slapd
> > nss_ldap: failed to bind to LDAP server ldap://127.0.0.1: Can't contact LDAP server
> > nss_ldap: failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server
> > nss_ldap: failed to bind to LDAP server ldapi://%2fvar%2frun%2fldapi_sock/: Can't contact LDAP server
> > ...
> > nss_ldap: could not search LDAP server - Server is unavailable
> >
> > I found out that the Gentoo init script activates the
> > options "-u ldap -g ldap".
>
> I detected I have a machine where this didn't happen. Then I
> upgraded from glibc-2.5-r4 to glibc-2.6.1 ...
>
> Could this be a real bug in glibc? Does anybody experience
> the same behaviour?
The developer list gave me the answer. Glibc checks for
group memberships of user ldap. A possible (temporary)
solution is to say in /etc/ldap.conf:
nss_initgroups_ignoreusers root,ldap
Bertram
--
Bertram Scharpf
Stuttgart, Deutschland/Germany
http://www.bertram-scharpf.de
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2007-10-23 1:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 19:09 [gentoo-user] LDAP: Slapd fails asking itself while startup Bertram Scharpf
2007-10-22 4:20 ` Bertram Scharpf
2007-10-23 1:52 ` Bertram Scharpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071023015203.GA15338@bart.bs.l \
--to=lists@bertram-scharpf.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox