Monitoring using cn=config

[Arturo Borrero]

Hi there.




Here is my config:

file /etc/ldap/slapd.d/cn=config/olcDatabase\=\{2\}monitor.ldif
dn: olcDatabase={2}monitor
objectClass: olcDatabaseConfig
objectClass: olcConfig
objectClass: top
olcDatabase: {2}monitor
createTimestamp: 20120918124549Z

 * none
olcAddContentAcl: FALSE
olcLastMod: TRUE
olcMonitoring: FALSE
olcReadOnly: FALSE
olcMaxDerefDepth: 15
olcSyncUseSubentry: FALSE

In file /etc/ldap/slapd.d/cn=config/olcDatabase\=\{1\}hdb.ldif
[...]
olcMonitoring=TRUE
[...]




I try:

root@server:~# ldapsearch -H ldapi:/// -Y EXTERNAL -s sub -b cn=Monitor
SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
# extended LDIF
#
# LDAPv3
# base <cn=Monitor> with scope subtree
# filter: (objectclass=*)
# requesting: ALL
#

# search result
search: 2
result: 32 No such object

# numResponses: 1

So I guess the database for monitoring doesn't exist.

Any idea?

Best regards.

--
Arturo Borrero González
Departamento de Seguridad Informática, @NIS_CICA (twitter)
Centro Informático Científico de Andalucía (CICA)
Avda. Reina Mercedes s/n - 41012 - Sevilla (Spain)
Tfno.: +34 955 056 600 / FAX: +34 955 056 650
Consejería de Economía, Innovación, Ciencia y Empleo
Junta de Andalucía

I'm using slapd 2.4.23-7.2 (from Debian Squeeze) and i'm unable to get monitoring running. olcAccess: {0}to * by peername.ip=127.0.0.1 read by peername.ipv6=::1 read by The documentation isn't complete: www.openldap.org/devel/admin/monitoringslapd.html

smime.p7s
Description: S/MIME Cryptographic Signature