Hi!
Trying to create the initial config from LDIF using "slapadd -v -F /etc/openldap/slapd.d -w -S 3 -n0 -l 0.ldif" inSLES15 I get this: added: "cn=config" (00000001) added: "cn=module{0},cn=config" (00000001) added: "cn=schema,cn=config" (00000001) added: "cn={0}core,cn=schema,cn=config" (00000001) added: "cn={1}cosine,cn=schema,cn=config" (00000001) added: "cn={2}inetorgperson,cn=schema,cn=config" (00000001) added: "cn={3}rfc2307bis,cn=schema,cn=config" (00000001) added: "cn={4}yast,cn=schema,cn=config" (00000001) added: "cn={5}sudo,cn=schema,cn=config" (00000001) added: "olcDatabase={-1}frontend,cn=config" (00000001) <= str2entry NULL (smr_normalize createTimestamp 21) slapadd: could not parse entry (line=2360) Closing DB...
I've done that on a different machine without any errors so far.
The LDIF entry after "olcDatabase={-1}frontend,cn=config" is "dn: olcDatabase={0}config,cn=config". The timestamps are: creatorsName: cn=config createTimestamp: 20130712083810Z entryCSN: 20160222141054.581517Z#000000#001#000000 modifiersName: cn=config modifyTimestamp: 20160222141054Z
An "interesting" fact I found in /etc/openldap/slapd.d/cn=config/cn=schema.ldif was the end of the file; it reads: ... anslucentNoGlue $ olcTranslucentLocal $ olcTranslucentRemote $ olcTranslucent BindLocal $ olcTranslucentPwModLocal ) )lucent target database configuration' AUXILIARY )lue uniqueness configuration' SUP olcOverlayConfig STRUCTURAL MAY ( olcUniqueBase $ olcUniqueIgnore $ olcUniqueAttribute $ olcUniqueStrict $ o lcUniqueURI ) )g configuration' SUP olcOverlayConfig STRUCTURAL MUST olcValSo rtAttr )LIARY MAY ( olmBDBEntryCache $ olmBDBDNCache $ olmBDBIDLCache $ olmDb Directory ) )NSFER-REQUIRED 'TRUE' X-NOT-HUMAN-READABLE 'TRUE' )MAN-READABLE 'TRUE' )tion' )DABLE 'TRUE' )ADABLE 'TRUE' )TRANSFER-REQUIRED 'TRUE' X-NOT-HU MAN-READABLE 'TRUE' )NARY-TRANSFER-REQUIRED 'TRUE' X-NOT-HUMAN-READABLE 'TRUE ' )INARY-TRANSFER-REQUIRED 'TRUE' X-NOT-HUMAN-READABLE 'TRUE' )ficate' X-BINA RY-TRANSFER-REQUIRED 'TRUE' X-NOT-HUMAN-READABLE 'TRUE' )ription' )scription' )umber' )ABLE 'TRUE' )DABLE 'TRUE' )ess Points' )tion' )cription' )' )' )ion ' ) ) ) )X-BINARY-TRANSFER-REQUIRED 'TRUE' X-NOT-HUMAN-READABLE 'TRUE' )tifie r' )on' )n' )on' )) Exact Assertion' ) Assertion' ) )
That doesn't look right for me. CPU here is an "AMD EPYC 9354P 32-Core Processor", while the other machine without problems ran with VMware and "Intel(R) Xeon(R) Gold 6238R CPU @ 2.20GHz"; Looks like the last write to the config database is nor correct in case of errors.
Neither option "-c" (continue), nor "-o value-check=no", nor "-o schema-check=no" did help.
After some experiments I get a different error like "<= str2entry NULL (smr_normalize creatorsName 21)" Any insights?
Kind regards, Ulrich Windl