Red Hat Bugzilla – Bug 177473
ol-schema-migrate.pl generates mangled LDIF during Samba setup.
Last modified: 2008-08-11 19:43:40 EDT
Description of problem:
While setting up FDS 1.0.1 as a LDAP backend for a Samba PDC (per the
Howto:Samba Wiki) the attached mangled 61samba.ldif was generated by
ol-schema-migrate.pl. Slapd does not complain about being unable to read the
schema file when loading, but attempting to load LDIFs with objectClasses
defined in 61samba.ldif fail with an 'Object class violation'.
Version-Release number of selected component (if applicable):
14 June 2005 version of ol-schema-migrate.pl
RHEL ES 3
Steps to Reproduce:
1. Download ol-schema-migrate.pl from
2. perl ol-schema-migrate.pl /usr/share/doc/samba-3.0.9/LDAP/samba.schema >
3. Create /tmp/sambaDomainName.ldif with the following content:
4. /opt/fedora-ds/slapd-<server>/ldif2ldap "cn=Directory manager" password
adding new entry sambaDomainName=CMOMA,dc=cmoma,dc=mycompany,dc=com
ldap_add: Object class violation
ldap_add: additional info: unknown object class "sambaUnixIDPool"
Sucessful LDIF import.
Created attachment 123017 [details]
Weird - I don't have this problem on my Fedora Core 4 system -
Can you attach your original samba.schema file?
Created attachment 123023 [details]
This file was later used to generate a valid 61samba.ldif with the above
described procedure. I'm not sure why it behaved differently the first time.
Closing bug as not reproducable
filed new bug 179379 to address problem with corrupt ldif errors
being silently ignored
Bug already CLOSED. setting screened+ flag