On Tue, 2005-01-11 at 22:43, Rick Cuthill wrote:
> Hello,
>
> I know this isn't a new problem (symptom) as I have seen hints of
> it in the archives but no clean solution was found.
>
> First I installed all openldap RPMs using yum.
>
> I have been following "LDAP System Administrator" by Carter
> (O'Reilly), setting up the slapd.conf slowly and testing along
> the way. As you will see I don't get very far before problems
> start.
>
> For what ever reason, I can start ldap ldbm but not bdb. More
> specifically, ldap appears to start with bdb but when I check to
> see if the processes are active, none exist. When ldbm is
> specified, ldap starts
----
I don't recall what FC-1 used and I'm wondering if you can actually get
Fedora version from yum any longer anyway.
openldap < 2.1.x used ldbm
openldap >= 2.1 could use bdb (2.1 probably needed at least db v. 4.1.25
and 2.2.x wants v. 4.2.52
of course - it also depends upon whether openldap was compiled with bdb
option.
----
>
> I have made sure every db4-* rpm has been installed.
>
> Second symptom is (using ldbm) that I can make the root
> directory entry (i.e dc=metamorfix,dc=net) and then the first
> ou: I think gets entered but when I check using ldapsearch I
> get:
>
> # search result
> search: 2
> result: 32 No such object
>
> Instead of the directory listing.
>
> Okay so barge ahead anyway and try to add my name to the
> directory and I get the following:
>
> adding new entry "cn=Rick
> Cuthill,ou=contacts,dc=metamorfix,dc=net"
> ldapmodify: update failed: cn=Rick
> Cuthill,ou=contacts,dc=metamorfix,dc=net
> ldap_add: Internal (implementation specific) error (80)
>
> I have changed ownership of directory files from root to ldap but
> this didn't change any symptoms.
>
> Any suggestions?
----
files need to also be owned by ldap.ldap - not just the directory
make sure you add 'loglevel -1' to slapd.conf or something of
significance to log stuff (man slapd.conf) to get info on loglevel
add something similar to
local4.* /var/log/slapd.log
to /etc/syslog.conf to channel the logging and restart syslogd
check the logs - logs are your friend
Now to get helpful answers - you are gonna have to be more specific.
slapd.conf ?
version of db4 ?
significant messages from log?
exact command typed and exact reply from console
openldap is a moving target - version 2.0.27 supplied with RHEL is a
vastly different beast from current stable of 2.2.17
slapcat -l /root/ldap.ldif #dumps entire contents of ldap into file
#called ldap.ldif
Craig
