My painful upgrade saga continues on from bug #462304.

I did as you suggested, and removed the bad entries from my LDIF, and tried reconfiguring...and now I've hit this bug. My entryCSNs are in the following format:

dn: dc=.
objectClass: top
objectClass: dcObject
objectClass: dNSDomain
dc: .
structuralObjectClass: dNSDomain
entryUUID: ...
creatorsName: ...
createTimestamp: 20041111015842Z
entryCSN: 2004111101:58:42Z#0x0001#0#0000
modifiersName: ...
modifyTimestamp: 20041111015842Z

...and following the advice I found on here (and elsewhere, I ran some regexes 
over the file and ended up with:

dn: dc=.
objectClass: top
objectClass: dcObject
objectClass: dNSDomain
dc: .
structuralObjectClass: dNSDomain
entryUUID: ...
creatorsName: ...
createTimestamp: 20041111015842Z
entryCSN: 20041111015842Z#000001#00#000000
modifiersName: ...
modifyTimestamp: 20041111015842Z

...but this still doesn't work for me. I have no idea which entry is the 
problem, as the software doesn't tell me; I just get the assertion failure.

$:/var/backups/slapd-2.3.38-1+lenny1# dpkg --configure -a
Setting up slapd (2.4.7-3) ...
  Backing up /etc/ldap/slapd.conf in /var/backups/slapd-2.3.38-1+lenny1... done.
  Upgrading BDB 'checkpoint' options... .
  Moving old database directories to /var/backups:
  Loading from /var/backups/slapd-2.3.38-1+lenny1:
  - directory dc=.... /var/lib/dpkg/info/slapd.postinst: line 1085:  1701 Aborted                
 "$@" 2>&7
failed.

Loading the database from the LDIF dump failed with the following
error while running slapadd:
    slapadd: /build/buildd/openldap2.3-2.4.7/servers/slapd/schema_init.c:3669: csnNormalize: 
Assertion `val->bv_len == 
(sizeof("YYYYmmddHHMMSS.uuuuuuZ#SSSSSS#SID#ssssss")-1)' failed.
dpkg: error processing slapd (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 slapd

I've tried hacking the entries around (trying to make them longer to match the format in the assertion, but TBH, I'm realistically just poking it with sticks, as I've not found any examples of what a valid entry looks like to validate mine against.

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to