"Dieter Kluenter" dieter@dkluenter.de writes:
Howard Chu hyc@symas.com writes:
Gavin Henry wrote:
Hi All, I think it's worth adding an upgrading section, as I'm just playing with a copy of a live 2.3.38 system and an upgrade to LDAP_REL_ENG_2_4 is giving: olcReplicationInterval: value #0: <olcReplicationInterval> keyword is obsolete (ignored) str2entry: invalid value for attributeType objectClass #0 (syntax 1.3.6.1.4.1.1466.115.121.1.38) => ldif_enum_tree: failed to read entry for /usr/local/etc/openldap/slapd.d/cn=config/cn=include{0}.ldif slaptest: bad configuration file! Admittedly, no slapcat was done as the bdb env is the same, but thought I'd do what a normal user would ;-) Should we list obsolete values from bconfig.c that will apply and discuss/present the best way to upgrade?
Obsolete values don't matter; like the message said - it was simply ignored.
The problem you ran into here is that 2.3.x had cn=include entries (which were also ignored in 2.3) but support for them was axed in 2.4. So, just delete all the cn=include* files from the config directory.
With HEAD i have similar problems # ./slapcat -l /tmp/020907.ldif str2entry: invalid value for attributeType olcDbConfig #11 (syntax 1.3.6.1.4.1.1466.115.121.1.15) => ldif_enum_tree: failed to read entry for /opt/openldap/etc/openldap/slapd.d/cn=config/olcDatabase={1}hdb.ldif slapcat: bad configuration file! magenta:/opt/openldap/sbin #
-Dieter
<quote who="Dieter Kluenter">
"Dieter Kluenter" dieter@dkluenter.de writes:
Howard Chu hyc@symas.com writes:
Gavin Henry wrote:
Hi All, I think it's worth adding an upgrading section, as I'm just playing with a copy of a live 2.3.38 system and an upgrade to LDAP_REL_ENG_2_4 is giving: olcReplicationInterval: value #0: <olcReplicationInterval> keyword is obsolete (ignored) str2entry: invalid value for attributeType objectClass #0 (syntax 1.3.6.1.4.1.1466.115.121.1.38) => ldif_enum_tree: failed to read entry for /usr/local/etc/openldap/slapd.d/cn=config/cn=include{0}.ldif slaptest: bad configuration file! Admittedly, no slapcat was done as the bdb env is the same, but thought I'd do what a normal user would ;-) Should we list obsolete values from bconfig.c that will apply and discuss/present the best way to upgrade?
Obsolete values don't matter; like the message said - it was simply ignored.
The problem you ran into here is that 2.3.x had cn=include entries (which were also ignored in 2.3) but support for them was axed in 2.4. So, just delete all the cn=include* files from the config directory.
With HEAD i have similar problems # ./slapcat -l /tmp/020907.ldif str2entry: invalid value for attributeType olcDbConfig #11 (syntax 1.3.6.1.4.1.1466.115.121.1.15) => ldif_enum_tree: failed to read entry for /opt/openldap/etc/openldap/slapd.d/cn=config/olcDatabase={1}hdb.ldif slapcat: bad configuration file! magenta:/opt/openldap/sbin #
Did you see my previous reply? If not, replace:
olcDbConfig: {11}
with:
olcDbConfig: {11}#
olcDbConfig attribute syntax must block empty values now.
-Dieter
-- Dieter Klünter | Systemberatung http://www.dkluenter.de GPG Key ID:8EF7B6C6
Gavin Henry wrote:
<quote who="Dieter Kluenter">
With HEAD i have similar problems # ./slapcat -l /tmp/020907.ldif str2entry: invalid value for attributeType olcDbConfig #11 (syntax 1.3.6.1.4.1.1466.115.121.1.15) => ldif_enum_tree: failed to read entry for /opt/openldap/etc/openldap/slapd.d/cn=config/olcDatabase={1}hdb.ldif slapcat: bad configuration file! magenta:/opt/openldap/sbin #
Did you see my previous reply? If not, replace:
olcDbConfig: {11}
with:
olcDbConfig: {11}#
olcDbConfig attribute syntax must block empty values now.
That's a bit odd, since the olcDbConfig syntax hasn't changed, it's just DirectoryString.
Howard Chu wrote:
Gavin Henry wrote:
olcDbConfig attribute syntax must block empty values now.
That's a bit odd, since the olcDbConfig syntax hasn't changed, it's just DirectoryString.
But the validation for Ordered Values has changed. I've changed the olcDbConfig syntax (to IA5String) to allow empty values.
<quote who="Howard Chu">
Howard Chu wrote:
Gavin Henry wrote:
olcDbConfig attribute syntax must block empty values now.
That's a bit odd, since the olcDbConfig syntax hasn't changed, it's just DirectoryString.
But the validation for Ordered Values has changed. I've changed the olcDbConfig syntax (to IA5String) to allow empty values.
Yeah, that was lazy of me, I should have dug deeper than just "fixing" my problem.
Gavin.
-
Dieter Kluenter -
Gavin Henry -
Howard Chu