[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Slapd startup behavior when unable to bind to an interface

--On Monday, January 11, 2016 7:06 PM -0800 Ryan Tandy <ryan@nardis.ca> wrote:

On Sat, Jan 09, 2016 at 03:48:12PM -0800, Quanah Gibson-Mount wrote:
This is fairly trivial to reproduce.  As a non-privileged user, simply

-h "ldap:// ldapi://slapd.sock"

It will fail to bind to 389, but bind to the LDAPI socket anyway, and
continue the startup process.

I was sure I saw this at the time when we were talking about it in IRC,
but now I can't get it to reproduce again. Guess I screwed up.

Either way, I am seeing it sporadically on systems where it has a screwy /etc/hosts file, along the lines of: localhost
::1 hostname.fqdn hostname localhost

ipv4address hostname.fqdn hostname

and of course, hostname is not assigned to ::1, just localhost is.

In this case, every once in a great while, we see:

Jan 9 08:37:56 zqa-126 slapd[23993]: daemon: bind(8) failed errno=22 (Invalid argument) Jan 9 08:37:56 zqa-126 slapd[23993]: @(#) $OpenLDAP: slapd 2.4.43 (Jan 4 2016 20:01:22) $#012#011build@u1287:/home/build/p4/zimbra/JUDASPRIEST/ThirdParty/openldap/tmp/UBUNTU12_64/zimbra-openldap/servers/slapd

(and away it goes, only listening on ldapi).



Quanah Gibson-Mount
Platform Architect
Zimbra, Inc.
Zimbra ::  the leader in open source messaging and collaboration