(E-Mail Removed) (Lew Pitcher) wrote in message news:<(E-Mail Removed)>...
> I've configured, compiled and installed OpenLDAP 2.1.22 on a Slackware Linux 9.0
> system, and am in the process of installing the NetMeeting directory kit (v1.2).
> However, I've run into a problem with the resulting core.schema that causes the
> two slapd servers to fail.
>
> I'm following the instructions in the Linux Netmeeting HOWTO, revision v1.2 (15
> Jan 2002), specifically, section 3 "NetMeeting directory kit".
>
> Berkeley DB v4 has been installed from the Slackware 9.0 "extra" set of packages
> (package db4-4.1.25-i386-1.tgz).
>
> root@srdscs05:~# more /var/adm/packages/db4-4.1.25-i386-1
> PACKAGE NAME: db4-4.1.25-i386-1
> COMPRESSED PACKAGE SIZE: 1626 K
> UNCOMPRESSED PACKAGE SIZE: 7040 K
> PACKAGE LOCATION: db4-4.1.25-i386-1.tgz
> PACKAGE DESCRIPTION:
> db4: db4 (Berkeley database library version 4)
> db4:
> db4: The Berkeley Database (Berkeley DB) library provides embedded database
> db4: support for both traditional and client/server applications.
> db4:
> db4: This package should be installed if compatibility is needed with
> db4: databases created with the Berkeley DB version 4.
>
> Berkeley DB v4 is required by the OpenLDAP 2.1.22 install
>
> I preinstalled the Net::LDAP perl package from CPAN as per the Netmeeting
> directory kit installation instructions. There were no problems installing this
> package.
>
> OpenLDAP 2.1.22 is configured with the following options
> ./configure --enable-shell --disable-debug --enable-ldbm --without-threads
>
> I executed the standard configure / make / make test / make install quickstep.
> make test didn't find any errors.
>
> After "make install", I followed the NDK installation instructions, copying
> netmeeting.perl, netmeeting.schema, slapd.conf and slapd2.conf to the
> appropriate directories.
>
> Now comes the first problem:
>
> I attempted to patch the core.schema as per the instructions, but got errors on
> one hunk out of four:
> root@srdscs05:~/ndk-1.2# cd /usr/local/etc/openldap/schema/
> root@srdscs05:/usr/local/etc/openldap/schema# ls
> README cosine.schema.default misc.schema.default
> corba.schema inetorgperson.schema netmeeting.schema
> corba.schema.default inetorgperson.schema.default nis.schema
> core.schema java.schema nis.schema.default
> core.schema.default java.schema.default openldap.schema
> cosine.schema misc.schema openldap.schema.default
> root@srdscs05:/usr/local/etc/openldap/schema# cp core.schema core.schema.bak
> root@srdscs05:/usr/local/etc/openldap/schema# patch core.schema \
> < ~/ndk-1.2/core.schema.patch
> patching file core.schema
> Hunk #1 succeeded at 1 with fuzz 2.
> Hunk #2 succeeded at 287 with fuzz 2 (offset 160 lines).
> Hunk #3 FAILED at 310.
> Hunk #4 succeeded at 337 (offset -164 lines).
> 1 out of 4 hunks FAILED -- saving rejects to file core.schema.rej
>
> I've hand-edited core.schema to match the required change, and that seems not to
> be an issue. That is to say, the .rej file tells me
> root@srdscs05:/usr/local/etc/openldap/schema# cat core.schema.rej
> ***************
> *** 302,308 ****
>
> attributetype ( 2.5.4.3 NAME ( 'cn' 'commonName' ) SUP name )
>
> - attributetype ( 2.5.4.4 NAME ( 'sn' 'surname' ) SUP name )
>
> attributetype ( 2.5.4.5 NAME 'serialNumber' EQUALITY caseIgnoreMatch
> SUBSTR caseIgnoreSubstringsMatch
> --- 310,316 ----
>
> attributetype ( 2.5.4.3 NAME ( 'cn' 'commonName' ) SUP name )
>
> + attributetype ( 2.5.4.4 NAME ( 'surname' 'sn' ) SUP name )
>
> attributetype ( 2.5.4.5 NAME 'serialNumber' EQUALITY caseIgnoreMatch
> SUBSTR caseIgnoreSubstringsMatch
>
> so I hand reorder the parameters of 2.5.4.4 from " 'surnamen' 'sn' " to
> " 'sn' 'surname' ", and all seems well.
>
> However, when I start up the two slapd servers, they complain that
>
> /usr/local/etc/openldap/schema/core.schema: line 290: AttributeType
> inappropriate matching rule: "caseIgnoreMatch"
>
> Has anyone run into this before? Any suggestions as to the proper fix?
Lew,
I've run into the same problem as you. I simply deleted the lines
in the schema that the slapd server complained about. Can't claim
that's a proper fix, but my severs are now running. The errors came
up for both core.schema and netscape.schema, so watch the file you are
editing (and ending paranthesis).
After deleting all the appropriate lines in the schemas, the slave
server, while not producing any more errors, was still not starting.
I modified two lines in slapd2.conf to look like below:
suffix "objectClass=RTPerson"
rootdn "cn=root,objectClass=RTPerson"
Now the slave server is starting, but I have run into another problem,
so I'm not completely working yet. When I try to initialize the db I
get the following error:
adding new entry "objectClass=RTPerson"
ldapadd: update failed: objectClass=RTPerson
ldap_add: Object class violation (65)
additional info: no structural object class provided
Maybe my initialize script is just not tweaked right. It's getting
late, so my brain is working much now. I hope the above gets you
through your setup. If you get through the db initialization I'd be
interested in hearing the fix. Good luck!
Tom