Okay. I stopped slapd and ran the slapcat command and the full.ldif file is empty. I added the access/write entries to the slapd.conf file. And started slapd up again.
Here are the results from ldapsearch and ldapadd (I guessed on the syntax)
[root@EGGLDAP root]# !ldapsearch
ldapsearch -x -b 'dc=services,dc=egginc,dc=com' -D 'cn=Manager,dc=services,dc=eg
ginc,dc=com' -w secret '(objectclass=*)'
# extended LDIF
#
# LDAPv3
# base <dc=services,dc=egginc,dc=com> with scope sub
# filter: (objectclass=*)
# requesting: ALL
#
# search result
search: 2
result: 32 No such object
# numResponses: 1
[root@EGGLDAP openldap]# !l
ldapadd -x -D 'cn=Manager,dc=services,dc=egginc,dc=com' -W -f egg3.txt
Enter LDAP Password:
adding new entry "cn=Charles Abbate ,ou=egg ,dc=services ,dc=egginc ,dc=com"
ldap_add: Type or value exists (20)
additional info: objectClass: value #0 provided more than once
I stopped slapd and ran the slapcat again. The full.ldif file is still empty. I agree. I must be missing something basic, but obviously necessary. THANK YOU for all your assistance with this!
-----Original Message-----
From: Todd Lyons [mailto:tlyons@ivenue.com]
Sent: Tuesday, October 19, 2004 9:31 PM
To: openldap-software@openldap.org
Cc: Pease, Melanie
Subject: Re: Cannot get users to load
mpease@egginc.com wanted us to know:
> Same results for ldapsearch. I'm guessing there are limited results
> because the ldapadd is not working.
>
> [root@EGGLDAP openldap]# ldapsearch -x -b
> 'dc=services,dc=egginc,dc=com' -D 'cn
> =Manager,dc=services,dc=egginc,dc=com' -w secret '(objectclass=*)'
> # extended LDIF
> #
> # LDAPv3
> # base <dc=services,dc=egginc,dc=com> with scope sub
> # filter: (objectclass=*)
> # requesting: ALL
> #
>
> # search result
> search: 2
> result: 32 No such object
>
> # numResponses: 1
Ok, shut down slapd. Run 'slapcat > /root/full.ldif'. Let's see what's
actually in this full.ldif.
It's my personal belief that something very basic is wrong. I would
suggest to first add an access line in:
access to *
by * write
That will make it so that if a user can authenticate a password, it will
allow them write access to everything. In your case, you don't have any
user yet except for the Manager, so it won't hurt anything.
Again, this is ONLY for *TESTING*. If this is anywhere close to a
production system, you should not be doing such global open holes as
that.
--
Regards... Todd
They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. --Benjamin Franklin
Linux kernel 2.6.3-19mdkenterprise 2 users, load average: 0.16, 0.07, 0.03