Double-check your bind DN. Looks like you're missing a 'c':
"cn=directory manager"
instead of:
"cn=diretory manager"
Bliss, Aaron wrote:
I'm attempting to turn the logging level back to zero, however I'm
having much difficulty using both the bundled ldapmodify as well as the
ldapmodify that is part of openldap; here is the syntax that I'm using:
/ldapmodify -D "cn=diretory manager" -w mypassword -f /tmp/errors.ldif
Here is the contents of /tmp/errors.ldif
dn: cn=config
changetype: modify
replace: nsslapd-errorlog-level
nsslapd-errorlog-level: 0
This results in ldap_simple_bind: No such object
Please advise and thanks.
Aaron
-----Original Message-----
From: fedora-directory-users-bounces@xxxxxxxxxx
[mailto:fedora-directory-users-bounces@xxxxxxxxxx] On Behalf Of Richard
Megginson
Sent: Monday, August 07, 2006 3:20 PM
To: General discussion list for the Fedora Directory server project.
Subject: Re: High cpu utilizaton by slapd
Bliss, Aaron wrote:
Replication logging:
Is this the "Enable Changelog" checkbox? It's currently enabled; does
this need to be enabled? Thanks again.
No, not the changelog.
http://directory.fedora.redhat.com/wiki/FAQ#Troubleshooting
Aaron
-----Original Message-----
From: fedora-directory-users-bounces@xxxxxxxxxx
[mailto:fedora-directory-users-bounces@xxxxxxxxxx] On Behalf Of
Richard
Megginson
Sent: Monday, August 07, 2006 3:06 PM
To: General discussion list for the Fedora Directory server project.
Subject: Re: High cpu utilizaton by slapd
Bliss, Aaron wrote:
Hi everyone,
I'm running fds on 2 servers, a supplier and consumer, both are
running
redhat ES 4; I noticed today and for the last few days that the
supplier
directory server is running very, very slow, top reveals that
ns-slapd
is killing the cpu; these are running on server class hardware,
roughly
1.5 GHZ hp proliant servers; the consumer directory server cpu
utilization is almost 0 (99 % idol); I don't really know how to being
to
troubleshoot this problem; I've seen similar issues on oracle
database
servers when database indexes were corrupt and had to be
rebuilt....Any
ideas as to how to begin to troubleshoot this? Thanks very much.
1806 ldap 15 0 517m 33m 14m S 90.6 3.3 4:56.21 ns-slapd
Do you have a lot of delete operations? It could be that the
tombstone
reaping thread is working overtime. You can turn on replication
logging
and look for tombstone messages.
Confidentiality Notice:
The information contained in this electronic message is intended for
the exclusive use of the individual or entity named above and may
contain privileged or confidential information. If the reader of this
message is not the intended recipient or the employee or agent
responsible to deliver it to the intended recipient, you are hereby
notified that dissemination, distribution or copying of this
information
is prohibited. If you have received this communication in error,
please
notify the sender immediately by telephone and destroy the copies you
received.
--
Fedora-directory-users mailing list
Fedora-directory-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-users
--
Fedora-directory-users mailing list
Fedora-directory-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-users
--
Fedora-directory-users mailing list
Fedora-directory-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-users
--
Fedora-directory-users mailing list
Fedora-directory-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-users
