[Date Prev][Date Next]
Re: How to enable monitoring in OpenLdap with cn=config Backend
at first thank you very much for your answer and the your effort.
Am 25.01.2012 16:49, schrieb Stefan Skoglund:
I think i need to modify my text a litte :-)
ons 2012-01-25 klockan 16:18 +0100 skrev Stefan Skoglund:
When dpkg installs slapd in debian wheezy it
uses /usr/share/slapd/slapd.init.ldif as an template for bootstraping
As i wrote in one of my last emails i've done the configuration from my
ldap server with the documentation from the ubuntuusers wiki (this is in
german, but the steps should be clear)
Which is executed (the script) at slapd install time!
The install shell-script takes the selection which debconf asks and
which you probably did answer and with that transforms (a simple m4
invocation is good enough) the template ldif-file into the final potent
init ldif-file. That ldif file is then interpreted by slapcat and
slapcat can now create an working slapd configuration.
...such that slapcat generates an working slapd config.
slapcat,slapadd,slapindex and slapd is different names for the same
Thanks for this hint. I never had have a look at this before...
These binaries are hardlinked ;-) Fine.
ls -li slap*
1045854 -rwxr-xr-x 9 root root 1284316 2011-11-14 22:27 slapacl
Now slapd can start and the first thing which is done is the insertion
of the root node in the ldap-tree.
My ldap directory (with cn=config Backend - i never had have a
slapd.conf!) is working fine
Oh ok, i think this is what Quannah mentioned in his mails. I'll try to
understand this in the next few days.
The ldif template shows you a number of examles of how to do
continuation lines in ldif which is one of the reason why the ldif
inside your other letters was bad.
Excuse me please, but my english isn't good enough to understand this
sentence. Could give me some more explanations?
The falty line continuations in the ldif fragments in your emails
explains a number of your problems.
Ok, i shoud read not only the documentation belonging the ldif format...
The description for ldapvi should be the next one...
For ldapvi you should understand that ldapvi uses an modified ldif, for
example for adding nodes in an ldif tree.
The syntax for ldapvi and ldapadd differs.
Anyway, the monitoring backend is still working, but the script from
does not work for me...
Unfortunately i have not so much time to check all details... and my
programming skill does not touch the perl language...
The idea of activate the monitoring in slapd, was the showing from the
ldap state in the munin tool... I also opened a thread in the
munin-users mailinglist, but they couldn't help me...
PS: So please excuse my english writing. I hope its understandable for
this technical facts.