Howard,
This is actually a format that I have use on other ldif's and they work. I did follow you advice on the slapd.conf and got pas the errors and hit another snag to discover that after following instructions on createing a build and installing with no errors that openLdap still wsa showing as installed. So I have started going back over those instructions from the install file as well as the 2.4 admin documentation that is out of date. The slapd.conf man pages on the server don't even list mdb as an attribute for the database. So reading documentation that has not been updated isn't always that helpful.
This is my first go at openLDAP and I am sorry that I might waste some of your time, but the last book that written on this software that I can find was written 7 years when some of the now deprecated features were just in the planning stages.
Thank you for our help. Eric Speake Web Systems Administrator O'Reilly Auto Parts
From: Howard Chu hyc@symas.com To: espeake@oreillyauto.com, openldap-technical@openldap.org Date: 10/03/2013 05:14 PM Subject: Re: Log level will not change. Sent by: openldap-technical-bounces@OpenLDAP.org
espeake@oreillyauto.com wrote:
Here is the contents of configlog.ldif
You seem to have continual difficulty understanding that whitespace is significant. Please read the ldif(5) manpage more carefully. Judging from your other lengthy email thread, you also need to read slapd.conf(5) more carefully.
dn: cn=config changetype: modify
delete: olcLogLEvel
add: olcLogLevel olcLogLevel: 0
I run the following commend:
ldapmodify -Wx -D "uid=admin,dc=oreillyauto,dc=com" -H ldap://tntest-ldap-1.oreillyauto.com -c -f /tmp/configlog.ldif
the output shows:
Enter LDAP Password: modifying entry "cn=config"
Except the loglevel cn=config does not change. The modifyTimeStamp and entryCSN change to match the server. I have a 3 node MMR cluster on 2.4.31. I am working on a build to go to 2.4.36, but in the mean time I need to get this working.
Thanks, Eric Speake Web Systems Administrator O'Reilly Auto Parts
This communication and any attachments are confidential, protected by
Communications Privacy Act 18 USCS § 2510, solely for the use of the intended recipient, and may contain legally privileged material. If you are not the intended recipient, please return or destroy it immediately. Thank you.
-- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/
-- This message has been scanned for viruses and dangerous content, and is believed to be clean. Message id: ABCAD600DE6.A2076
This communication and any attachments are confidential, protected by Communications Privacy Act 18 USCS § 2510, solely for the use of the intended recipient, and may contain legally privileged material. If you are not the intended recipient, please return or destroy it immediately. Thank you.