[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: 2.1 upgrade issue
- To: <hyc@highlandsun.com>
- Subject: RE: 2.1 upgrade issue
- From: "John Madden" <jmadden@ivytech.edu>
- Date: Wed, 2 Apr 2003 10:58:24 -0500 (EST)
- Cc: <openldap-software@OpenLDAP.org>
- Importance: Normal
- In-reply-to: <005601c2f7d1$75ed80c0$0e01a8c0@CELLO>
- References: <47557.168.91.2.45.1049141259.squirrel@mail.ivytech.edu> <005601c2f7d1$75ed80c0$0e01a8c0@CELLO>
> Probably because what you call your root object doesn't exist. Have you
> checked your original LDIF to see that it was actually there?
This was the problem. v2.1 must be much more strict with its schema
requirements, as before,
dn:dc=ivy,dc=tec,dc=in,dc=us
objectClass: top
was sufficient, whereaas 2.1 complains about a lack of structural
objectclass. So I created a dummy LDIF of:
dn: dc=ivy,dc=tec,dc=in,dc=us
objectClass: dcObject
objectClass: organization
o: Ivy Tech State College
dc: ivy
Searches from that base now work.
> Did you configure with --enable-crypt? Are you building with OpenSSL? If
> so, have you patched your OpenSSL library so that it doesn't interfere
> with normal crypt() behavior? <
> http://www.openldap.org/faq/data/cache/185.html Note about OpenSSL and
> crypt() >
Yep, --enable-crypt fixed this issue as well. It must've been enabled by
default in 2.0.x.
Thanks!
John
--
John Madden
UNIX Systems Engineer
Ivy Tech State College
jmadden@ivytech.edu