Bug 6975 - samba 4 provision - slapd command line incorrect
Summary: samba 4 provision - slapd command line incorrect
Status: RESOLVED INVALID
Alias: None
Product: Samba 4.0
Classification: Unclassified
Component: AD: LDB/DSDB/SAMDB (show other bugs)
Version: unspecified
Hardware: All Linux
: P3 major (vote)
Target Milestone: ---
Assignee: Andrew Bartlett
QA Contact: samba4-qa@samba.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-08 08:15 UTC by Jonn Taylor
Modified: 2010-01-27 01:31 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jonn Taylor 2009-12-08 08:15:09 UTC 
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'
Comment 1 Matthias Dieter Wallnöfer 2010-01-21 01:52:34 UTC 
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.
Comment 2 Endi Sukma Dewata 2010-01-26 16:36:16 UTC 
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.
Comment 3 Matthias Dieter Wallnöfer 2010-01-27 01:31:52 UTC 
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!