guess I have this sorted out, so see below for my last few paragraphs
that I suggest to put into the manual.
Thanks for all your suggestions, though it seems the problem was
something rather unrelated. Just don't ask me what it might have been...
On 03.02.2019 at 22:56, Arno Lehmann wrote:
-----8<--------------cut here... manual text below
Naturally, the ACL(s) may be adjusted as needed.
root@host:~/ldap# ldapadd -H ldapi:/// -Y EXTERNAL -f addMonitorDB.ldif
SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
adding new entry "olcDatabase=monitor,cn=config"
If this command succeds, the OpenLDAP instance can now be monitored
using LDAP. If it fails with an error message such as
ldap_add: Other (e.g., implementation specific) error (80)
additional info: only one monitor database allowed
it may be necessary to stop and restart the slapd process. (In at least
one case, it only worked after a few restarts and after adding some
other objects to a real database backend first. The author is absolutely
not sure what eventually lead to success adding the above LDAP data.)
20.1.7. Verifying monitoring does work
After the above steps are taken, queries such as
root@host:~/ldap# ldapsearch -Q -LLL -H ldapi:/// -Y EXTERNAL -b
'cn=Statistics,cn=Monitor' -s children 'monitorCounter'
will provide useful results.
-----8<--------------cut here... manual text above ------------->8------
So, this is my proposal to add to the manual. Feel free to use it, itf
needed, tell me where I have to assign legal permission!
Sandstr. 6, 49080 Osnabrück