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

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

On 10. jan. 2016 00:48, Quanah Gibson-Mount wrote:
Currently, slapd will start up even if it can't bind to an interface, if more
than one potential interface is given where the bind is successful. (...)
This is fairly trivial to reproduce.  As a non-privileged user, simply do:

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

It will fail to bind to 389, but bind to the LDAPI socket anyway, and
continue the startup process.  This gives a false result that slapd started
successfully, although clearly external clients will be unable to talk to it.

Doesn't start on my Linux machines, RHEL 6.7 and 7.2:

5693ba7e @(#) $OpenLDAP: slapd 2.4.X (Jan 11 2016 14:14:28) $
5693ba7e daemon: bind(7) failed errno=13 (Permission denied)
5693ba7e daemon: bind(7) failed errno=13 (Permission denied)
5693ba7e slapd stopped.