Hi, It is not as easy as you state it. I have a 2nd set up
olcServerID: 1 ldap://abc1prdp01.abcgroup.com:1600
olcServerID: 2 ldap://abc2prdp01.abcgroup.com:1600
and
SLAPD_URLS="ldapi:/// ldap://:1600/"
This works too.
Op wo 14 aug. 2019 om 17:03 schreef Quanah Gibson-Mount quanah@symas.com:
--On Wednesday, August 14, 2019 11:23 AM +0200 HG hanspeter.sloot@gmail.com wrote:
olcServerID: 1 ldap://linux1014.ts.aa-srv.com olcServerID: 2 ldap://linux1015.ts.aa-srv.com
Neither of those has a trailing slash. You noted:
SLAPD_URLS="ldapi:/// ldap://linux1014.ts.aa-srv.com/"
doesn't start, but
SLAPD_URLS="ldapi:/// ldap://linux1014.ts.aa-srv.com"
starts.
I would expect this. As I said before, it's a MATCH between what's provided in the olcServerID field and the -h option to slapd (SLAPD_URLS in your case). I.e., the software is functioning as documented. If you want it to match on the trailing slash, adjust your olcServerID values to include a trailing slash.
Regards, Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com