Re: Monitoring using cn=config

[Dieter KlÃnter <dieter@dkluenter.de>]

Am Wed, 19 Sep 2012 11:42:04 +0200
schrieb Arturo Borrero <aborrero@cica.es>:

> Hi there.
> 
> I'm using slapd 2.4.23-7.2 (from Debian Squeeze) and i'm unable to
> get monitoring running.
> 
> 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
> olcAccess: {0}to * by peername.ip=127.0.0.1 read by peername.ipv6=::1 
> read by
[...]
> root@server:~# ldapsearch -H ldapi:/// -Y EXTERNAL -s sub -b
> cn=Monitor SASL/EXTERNAL authentication started
[...]
> 
> # numResponses: 1
> 
> So I guess the database for monitoring doesn't exist.

According to your access rules, only a tcp connection on ip address
127.0.0.1 has read access, ldapi:// is a connection via ipc socket.
In order to test the availability of cn=Monitor try
ldapsearch -x -H ldap://localhost -b "" -s base + | grep monitorContext

-Dieter

-- 
Dieter KlÃnter | Systemberatung
http://dkluenter.de
GPG Key ID:DA147B05
53Â37'09,95"N
10Â08'02,42"E