When you run the provision script it tries to start the ldap server with the wrong parameters.
'/usr/local/libexec/slapd' '-F/usr/local/samba/private/ldap/slapd.d' '-h' 'ldapi://%2Fusr%2Flocal%2Fsamba%2Fprivate%2Fldap%2Fldapi'
This should be '/usr/local/libexec/slapd' '-f /usr/local/samba/private/ldap/slapd.conf' '-h' 'ldapi://%2Fusr%2Flocal%2Fsamba%2Fprivate%2Fldap%2Fldapi'
Endi, you as s4 directory backend expert, could you also help us with this problem? I think it should be easy to fix but some tests are needed to see if it works afterwards.
Hi, I don't think this is a bug. The provisoning tool converts the slapd.conf into slapd.d folder using the following command (see provisionbackend.py:511):
retcode = subprocess.call([self.slapd_path, "-Ttest", "-f", self.paths.slapdconf, "-F", self.paths.olcdir], close_fds=True, shell=False)
Then it will use the slapd.d folder to start OpenLDAP using the following command (see provisionbackend.py:234):
self.slapd = subprocess.Popen(self.slapd_provision_command, close_fds=True, shell=False)
Just make sure you are using a recent OpenLDAP version.
Thanks Endi for your opinion. Therefore, let us close this with "INVALID" and suggest the user to try a more recent OpenLDAP version. If the problem persists please reopen!