Re: meta backend olc?
Marc Patermann wrote:
Hi,
while migrating servers form 2.3.x to 2.4.x I stumbled upon this with
openldap2-2.4.20-0.4.29 SLES11SP1.
When I try online config based on my slapd.conf file, I get an error
# slaptest -f /etc/openldap/slapd.conf -F /etc/openldap/slapd.d -u
config file testing succeeded
fine so far.
# slaptest -f /etc/openldap/slapd.conf -F /etc/openldap/slapd.d
WARNING: No dynamic config support for database meta.
WARNING: No dynamic config support for database meta.
WARNING: The converted cn=config directory is incomplete and may not
work.
...
cn=config # cat olcDatabase={1}meta.ldif
dn: olcDatabase={1}meta
There is no URI or any meta specific attribute here.
Of course not, because it is not supported. Does your question indicate
that
the above warning messages are not clear enough? How can we make them
clearer?
from slapd.conf:
databasemeta
suffix ou=AllgV,ou=foo
uri ldap://server/ou=AllgV,ou=foo;
suffixmassage ou=AllgV,ou=foo ou=allgv,ou=proxy,o=bar
conn-ttl 30
idle-timeout 1m30s
subordinate
Is there something wrong with my config or does meta not work with olc?
According to the mail from p.
http://www.openldap.org/its/index.cgi/Documentation?expression=meta;download=Documentation/6277.followup.1.eml
it seems to be not me.
Whereas Howard replied: All of the core overlays now support
cn=config.
http://www.openldap.org/its/index.cgi/Documentation?id=6277;expression=meta#themesg
Exactly so. meta is a backend, not an overlay, and I specifcally said
overlays.
I've had half of back-sql's cn=config support in my working dir for
months; back-meta should be next (unless back-meta is de-commissioned,
still thinking about it). Both these projects are starving because of
lack of time, anyone feel free to jump in.
p.
Re: meta backend olc?
Marc Patermann wrote:
Hi,
while migrating servers form 2.3.x to 2.4.x I stumbled upon this with
openldap2-2.4.20-0.4.29 SLES11SP1.
When I try online config based on my slapd.conf file, I get an error
# slaptest -f /etc/openldap/slapd.conf -F /etc/openldap/slapd.d -u
config file testing succeeded
fine so far.
# slaptest -f /etc/openldap/slapd.conf -F /etc/openldap/slapd.d
WARNING: No dynamic config support for database meta.
WARNING: No dynamic config support for database meta.
WARNING: The converted cn=config directory is incomplete and may not work.
...
cn=config # cat olcDatabase={1}meta.ldif
dn: olcDatabase={1}meta
There is no URI or any meta specific attribute here.
Of course not, because it is not supported. Does your question indicate that
the above warning messages are not clear enough? How can we make them clearer?
from slapd.conf:
databasemeta
suffix ou=AllgV,ou=foo
uri ldap://server/ou=AllgV,ou=foo;
suffixmassage ou=AllgV,ou=foo ou=allgv,ou=proxy,o=bar
conn-ttl 30
idle-timeout 1m30s
subordinate
Is there something wrong with my config or does meta not work with olc?
According to the mail from p.
http://www.openldap.org/its/index.cgi/Documentation?expression=meta;download=Documentation/6277.followup.1.eml
it seems to be not me.
Whereas Howard replied: All of the core overlays now support
cn=config.
http://www.openldap.org/its/index.cgi/Documentation?id=6277;expression=meta#themesg
Exactly so. meta is a backend, not an overlay, and I specifcally said overlays.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
