--On Thursday, July 25, 2013 9:44 AM -0500 Mónico Briseño monico.briseno@gmail.com wrote:

Hi, there. I have installed ldap in Ubuntu 12.04. I decided to use cn=monitor. I added that line in the slap.conf script. I stopped and started the slpad deamon. After that I typed the following command: ldapsearch -x -D 'cn=admin,dc=example,dc=com' -W \ -b 'cn=monitor' -s base '(objectClass=*)' '*' '+'

However, I don't see nothing related with cn=monitor.

What did I do wrong?

If you used the ubuntu build of openldap, that was the first thing you did wrong, given its age.

The second thing is likely that you modified slapd.conf, which isn't used by Ubuntu anymore, as it has moved to the newer slapd-config backend. You would want to use ldapmodify to add the monitor backend.

--Quanah

--

Quanah Gibson-Mount Lead Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

Maybe with : ldapsearch -x -D 'cn=admin,dc=example,dc=com' -W -b 'dc=exemple,dc=com' 'cn=monitor' '(objectClass=*)' '*' '+'

Le 25/07/2013 16:44, Mónico Briseño a écrit :

Hi, there. I have installed ldap in Ubuntu 12.04. I decided to use cn=monitor. I added that line in the slap.conf script. I stopped and started the slpad deamon. After that I typed the following command: ldapsearch -x -D 'cn=admin,dc=example,dc=com' -W \ -b 'cn=monitor' -s base '(objectClass=*)' '*' '+'

The results of this command is:

extended LDIF # # LDAPv3 # base <> (default) with scope baseObject # filter: (objectclass=*) # requesting: -b cn=monitor (objectClass=*) * + #

# dn: objectClass: top objectClass: OpenLDAProotDSE structuralObjectClass: OpenLDAProotDSE configContext: cn=config namingContexts: dc=example,dc=com supportedControl: 2.16.840.1.113730.3.4.18 supportedControl: 2.16.840.1.113730.3.4.2 supportedControl: 1.3.6.1.4.1.4203.1.10.1 supportedControl: 1.2.840.113556.1.4.319 supportedControl: 1.2.826.0.1.3344810.2.3 supportedControl: 1.3.6.1.1.13.2 supportedControl: 1.3.6.1.1.13.1 supportedControl: 1.3.6.1.1.12 supportedExtension: 1.3.6.1.4.1.4203.1.11.1 supportedExtension: 1.3.6.1.4.1.4203.1.11.3 supportedExtension: 1.3.6.1.1.8 supportedFeatures: 1.3.6.1.1.14 supportedFeatures: 1.3.6.1.4.1.4203.1.5.1 supportedFeatures: 1.3.6.1.4.1.4203.1.5.2 supportedFeatures: 1.3.6.1.4.1.4203.1.5.3 supportedFeatures: 1.3.6.1.4.1.4203.1.5.4 supportedFeatures: 1.3.6.1.4.1.4203.1.5.5 supportedLDAPVersion: 3 supportedSASLMechanisms: DIGEST-MD5 supportedSASLMechanisms: CRAM-MD5 supportedSASLMechanisms: NTLM entryDN: subschemaSubentry: cn=Subschema

# search result search: 2 result: 0 Success

# numResponses: 2 # numEntries: 1

However, I don't see nothing related with cn=monitor.

What did I do wrong?

Thanks in Advance

-- M.S. José M. Briseño Cortés Universidad de Guadalajara Instructional Technologist Univ. Houston Moodle Teacher Certificate NTCM, IACEP, iNACOL, ACM member