The 00core.ldif schema file should contain only those schema elements which are required to start up the server. All other schema should be moved to 01common.ldif. Andrew and Satish have already done the work to determine that subset of schema required to start the server.
Created attachment 149163 [details] diffs
Created attachment 149164 [details] real diffs
Created attachment 149166 [details] cvs commit log Reviewed by: prowley, nkinder (Thanks!) Files: see diff Branch: HEAD Fix Description: Moved all schema not required to start the server from 00core.ldif into a new file called 01common.ldif. Andrew and Satish already did the work to determine which schema are required to start the server, which is the schema needed to be in 00core.ldif. Platforms tested: RHEL4 Flag Day: no Doc impact: no
Actually, core means only 00core.ldif and nothing else, no other schema files. Try it with only the file 00core.ldif in the schema directory.
I get this error on startup bash-3.00# /opt/dirsrv/slapd-goblin3/start-slapd [02/Jan/2008:11:20:33 -0800] - Entry "cn=config" has unknown object class "nsslapdConfig" [02/Jan/2008:11:20:33 -0800] - Entry "cn=encryption,cn=config" has unknown object class "nsEncryptionConfig" [02/Jan/2008:11:20:33 -0800] - Entry "cn=SNMP,cn=config" has unknown object class "nsSNMP" [02/Jan/2008:11:20:33 -0800] - Entry "cn=Kerberos uid mapping,cn=mapping,cn=sasl,cn=config" has unknown object class "nsSaslMapping" [02/Jan/2008:11:20:33 -0800] - Entry "cn=rfc 2829 dn syntax,cn=mapping,cn=sasl,cn=config" has unknown object class "nsSaslMapping" [02/Jan/2008:11:20:33 -0800] - Entry "cn=rfc 2829 u syntax,cn=mapping,cn=sasl,cn=config" has unknown object class "nsSaslMapping" [02/Jan/2008:11:20:33 -0800] - Entry "cn=uid mapping,cn=mapping,cn=sasl,cn=config" has unknown object class "nsSaslMapping" [02/Jan/2008:11:20:33 -0800] - Entry "cn=encryption,cn=config" has unknown object class "nsEncryptionConfig" [02/Jan/2008:11:20:33 -0800] - Entry "cn=SNMP,cn=config" has unknown object class "nsSNMP" [02/Jan/2008:11:20:33 -0800] - Entry "ou=Netscape Directory Team,cn=monitor" has unknown object class "organizationalUnit"
Based on above comments, my test is below: 1. install DS as standard procedure 2. start ds to verify it runs fine 3. stop ds 4. remove all schema under /etc/dirsrv/schema/, except 00core.schema to /tmp/schema 5. start ds again, verify : (1) it starts up without error message in error and access log (2) perform ldapsearch as "cn=directory manager" against "cn=config" success 6. stop ds, move all schemas back to /etc/dirsrv/schema, start ds again, verify: (1) DS starts up success (no error msg in error log and access log) (2) perform ldapsearch as "cn=directory manager" againt "cn=config" success
Test result: RHEL 5 i386 : PASS
Test on RHEL 5 x86_64 platform: [root@mv64a-vm schema]# service dirsrv start Starting dirsrv: mv64a-vm...[02/Apr/2009:06:16:20 -0700] - Entry "cn=config" has unknown object class "nsslapdConfig" [02/Apr/2009:06:16:20 -0700] - Entry "cn=encryption,cn=config" has unknown object class "nsEncryptionConfig" [02/Apr/2009:06:16:20 -0700] - Entry "cn=SNMP,cn=config" has unknown object class "nsSNMP" [02/Apr/2009:06:16:20 -0700] - Entry "cn=Kerberos uid mapping,cn=mapping,cn=sasl,cn=config" has unknown object class "nsSaslMapping" [02/Apr/2009:06:16:20 -0700] - Entry "cn=rfc 2829 dn syntax,cn=mapping,cn=sasl,cn=config" has unknown object class "nsSaslMapping" [02/Apr/2009:06:16:20 -0700] - Entry "cn=rfc 2829 u syntax,cn=mapping,cn=sasl,cn=config" has unknown object class "nsSaslMapping" [02/Apr/2009:06:16:20 -0700] - Entry "cn=uid mapping,cn=mapping,cn=sasl,cn=config" has unknown object class "nsSaslMapping" [02/Apr/2009:06:16:20 -0700] - Entry "cn=encryption,cn=config" has unknown object class "nsEncryptionConfig" [02/Apr/2009:06:16:20 -0700] - Entry "cn=SNMP,cn=config" has unknown object class "nsSNMP" [02/Apr/2009:06:16:20 -0700] - Entry "ou=Netscape Directory Team,cn=monitor" has unknown object class "organizationalUnit" [ OK ] ?? shall we output these messages? please verify otherwise, the rest of test on this platform passed
Platform RHEL 4 i386 pass
Wait - test passes on RHEL 4 i386 but fails on RHEL 5 x86_64? What other platforms pass/fail?
Solaris 9 passed -- rechecking RHEL 5 x86_64 (and same test passed this time, but i am so sure it did happened just 10 minutes ago)
RHEL 4 x86_64 pass rechecking rhel 5 x86_64 in new host now ...
recheck on RHEL 5 x86_64, it is pass. bug closed.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-0455.html