Antw: Upgrading from 2.4.26 to 2.4.41: Stricter checks prevent startup?

["Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de>]

For issue 2):

 # slapcat -n0 -F /etc/openldap/slapd.d -l /tmp/0.ldif
5bd1a671 UNKNOWN attributeDescription "OLCACCESSLOGDB" inserted.
5bd1a671 UNKNOWN attributeDescription "OLCACCESSLOGOPS" inserted.
5bd1a671 UNKNOWN attributeDescription "OLCACCESSLOGPURGE" inserted.
5bd1a671 UNKNOWN attributeDescription "OLCACCESSLOGSUCCESS" inserted.
5bd1a671 UNKNOWN attributeDescription "OLCACCESSLOGOLD" inserted.
5bd1a671 config error processing
olcOverlay={1}accesslog,olcDatabase={0}config,cn=config:
slapcat: bad configuration directory!

Ich bin ein gutes Stück weitergekommen, was Ihre Suche deutlich einschränken
sollte:
SLES11SP4:
rksaph03:~ # strings /usr/lib/openldap/slapd | grep AccessLogDB
( OLcfgOvOc:4.1 NAME 'olcAccessLogConfig' DESC 'Access log configuration' SUP
olcOverlayConfig MUST olcAccessLogDB MAY ( olcAccessLogOps $ olcAccessLogPurge
$ olcAccessLogSuccess $ olcAccessLogOld $ olcAccessLogOldAttr $
olcAccessLogBase ) )
( OLcfgOvAt:4.1 NAME 'olcAccessLogDB' DESC 'Suffix of database for log
content' SUP distinguishedName SINGLE-VALUE )

SLES12SP3:
rksapv07:/etc/openldap/slapd.d # strings /usr/lib/openldap/slapd | grep
AccessLogDB
#nix!

Vermutlich ist das Modul in SLES12 SP4 nicht mehr enthalten! Ich habe auch
kein entsprechendes Modul zum Nachinstallieren gefunden.

Können Sie das Problem an die Entwicklung eskalieren?

Mit freundlichen Grüßen
Ulrich Windl


>>> Ulrich Windl schrieb am 25.10.2018 um 08:59 in Nachricht <5BD169CB.6FC :
161 :
60728>:
> Hi!
> 
> I wonder whether there is a summary of additional checks that may prevent 
> 2.4.41 from starting in a 2.4.26 MMR configuration (What I did was upgrading

> SLES11 SP4 to SLES12 SP3). What I found out is:
> 
> 1) olcServerID does not longer accept fifferent URIs mapping to the same ID,

> like here (" slapd[3299]: olcServerID: value #1: <olcServerID> multiple
server 
> ID URLs matched, only one is allowed 1"):
> olcServerID: 1 ldap://host.domain.org:389
> olcServerID: 1 ldaps://host.domain.org:636
> (The idea was that whatever URI is used to contact the server, the server ID

> is the same)
> As we do not actually use ldaps for replication that second line could be 
> dropped easily
> 
> 2) After fixing the first problem, I get another one: "5bd06634 <=
str2entry: 
> str2ad(olcAccessLogDB): attribute type undefined". The schema files seem to

> be the same, and the manual page slapo-accesslog also seems to be the same.
> 
> Any instructions fixing all the issues that may prevent 2.4.41 from starting

> up?
> (please no comments on "2.4.41 is obsolete" unless exactly these problems 
> were fixed in a later version)
> I'm continuing with BDB, BTW, and also please no comments on "MDB is 
> better", please.
> 
> Regards,
> Ulrich
> 
> 
>