From: Bertram Scharpf <lists@bertram-scharpf.de>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Slapd calls nss_ldap before opening its ports
Date: Mon, 22 Oct 2007 14:12:29 +0200 [thread overview]
Message-ID: <20071022121229.GA24735@bart.bs.l> (raw)
Hi,
when setting up LDAP Pam authentication I encountered a
problem that seems to be neither Slapd- nor
nss_ldap-specific.
When running the init script there comes up an error that
clutters up my syslog with a lot of useless error messages:
@(#) $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
WARNING: No dynamic config support for database ldbm.
slapd starting
I found out that the Gentoo init script activates the
options "-u ldap -g ldap". Without them, the error messages
do not appear. Therefore I suppose the slapd daemon tries to
obtain passwd/shadow information for ldap via nss_ldap. At
least when I say "compat" in nsswitch.conf, the error
message doesn't appear as well.
The thing I really wonder about is that the lines in
nsswitch.conf say
passwd: files ldap
shadow: files ldap
group: files ldap
The files should be searched first. The "ldap" information
is present in all three of them. I even tried to chown the
shadow file to ldap but this didn't save me from the weird
messages either.
I detected I have a machine where this didn't happen. Then I
upgraded from glibc-2.5-r4 to glibc-2.6.1 ...
I tried to stuff log statements into glibc's nss part but
I'm not experienced enough in glibc to do that in finite
time.
Could this it a real bug in glibc or any of its patches?
Does anybody experience the same behaviour?
Thanks in advance,
Bertram
--
Bertram Scharpf
Stuttgart, Deutschland/Germany
http://www.bertram-scharpf.de
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2007-10-22 12:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 12:12 Bertram Scharpf [this message]
2007-10-22 12:44 ` [gentoo-dev] Slapd calls nss_ldap before opening its ports Benjamin Smee
2007-10-22 12:56 ` Bertram Scharpf
2007-10-22 15:48 ` Alec Warner
2007-10-22 19:50 ` Bertram Scharpf
2007-10-22 13:30 ` Michael Hanselmann
2007-10-22 15:47 ` Alec Warner
2007-10-22 19:56 ` Bertram Scharpf
2007-10-29 13:03 ` Robin H. Johnson
2007-10-29 11:45 ` Mike Frysinger
2007-10-29 12:15 ` Bertram Scharpf
2007-10-29 12:47 ` Mike Frysinger
2007-10-29 12:57 ` Bertram Scharpf
2007-10-29 16:41 ` Mike Frysinger
2007-10-29 17:39 ` Bertram Scharpf
2007-10-29 19:22 ` Chris Gianelloni
2007-10-29 20:41 ` Josh Saddler
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=20071022121229.GA24735@bart.bs.l \
--to=lists@bertram-scharpf.de \
--cc=gentoo-dev@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