60sendmail.ldif has the same OID 2.16.840.1.113730.3.1.13 for mailLocalAddress as 50ns-mail.ldif (part of core schema) for mailAlternateAddress.
60sendmail.ldif
mailLocalAddress
50ns-mail.ldif
mailAlternateAddress
60samba.ldif has comment on line 200, that breaks syntax validation: https://pagure.io/389-ds-base/blob/master/f/ldap/schema/60samba.ldif#_200
60samba.ldif
And 10rfc2307bis.ldif conflicts with 10rfc2307.ldif, but I guess that's expected.
10rfc2307bis.ldif
10rfc2307.ldif
1.2.x, 1.3.x, 1.4.x
Schema validation fails:
Jun 21 08:28:51 server.example.com ns-slapd[308]: [21/Jun/2018:08:28:51.242832202 +0000] - ERR - dse_read_one_file - The entry cn=schema in file /etc/dirsrv/slapd-server/schema/60sendmail.ldif (lineno: 1) is invalid, error code 20 (Type or value exists) - attribute type mailLocalAddress: Does not match the OID "2.16.840.1.113730.3.1.13". Another attribute type is already using the name or OID. Jun 21 08:28:51 server.example.com ns-slapd[308]: [21/Jun/2018:08:28:51.247236375 +0000] - ERR - schema_reload - slapi_reload_schema_files failed Jun 21 08:28:51 server.example.com ns-slapd[308]: [21/Jun/2018:08:28:51.251840516 +0000] - ERR - schemareload - schemareload_thread - Schema reload task failed.
Jun 21 08:42:32 server.example.com ns-slapd[308]: [21/Jun/2018:08:42:32.508008207 +0000] - ERR - dse_read_one_file - The entry cn=schema in file /etc/dirsrv/slapd-server/schema/60samba.ldif (lineno: 1) is invalid, error code 21 (Invalid syntax) - object class ( 1.3.6.1.4.1.7165.2.2.3 NAME 'sambaAccount' DESC 'Samba Auxilary Account' SUP top AUXILIARY MUST ( uid $ rid ): Failed to parse objectclass, error(4) at (end of input) Jun 21 08:42:32 server.example.com ns-slapd[308]: [21/Jun/2018:08:42:32.512515138 +0000] - ERR - schema_reload - slapi_validate_schema_files failed Jun 21 08:42:32 server.example.com ns-slapd[308]: [21/Jun/2018:08:42:32.517542840 +0000] - ERR - schemareload - schemareload_thread - Schema validation failed.
Shipped schema files should work out of the box.
doc bug?
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue set to the milestone: 1.4 backlog
Metadata Update from @mreynolds: - Issue tagged with: Schema
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/2856
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.