Ok, we've figured it out...
if i only start the slapd-samba4 from the fedora-ds it wil work.
but then the 389-console wil not function anymore.
kind of odd, if you ask me, to install fedora-ds
and not using the console to administer the directory...
anny tips or tricks on how to get the console running with the samba4 ??
or how to inter grade samba4-scheme with the standard 389 and console ??
Cheers... Collen
On 11-12-2009 10:49, collen at hermanjordan.nl wrote:> Hi we're busy discovering samba4 at the moment.
> we've installed fedora-ds as ldap backend.
>
> all install's configs and provisioning went well.. (no strange errors
orso)
> after fireing it all up we tried to add a user and this is what we got
back:
> -----------------------------------------
> Traceback (most recent call last):
> File "./newuser", line 69, in<module>
> samdb.newuser(username, opts.unixname, password,
> force_password_change_at_next_login_req=opts.must_change_at_next_login)
> File
"/usr/local/samba/lib/python2.6/site-packages/samba/samdb.py", line
> 129, in newuser
> "objectClass": "user"})
> _ldb.LdbError: (32, 'objectclass: Cannot add
> CN=test,CN=Users,DC=jordan,DC=net, parent does not exist!')
> ------------------------------------------
>
> i can see that there is a prob with the CN=Users, but what's the idea.
> i thought the provisioning did all the schema's and setup the ldap
backend
>
> in the 389-console, there is no samba thing what so ever.
> but if i start the dirsrv samba4 is also started..
>
> anny clue here..
> Thx C.
>
>
>