Hello list;

db-4.8.30.NC openldap-2.4.23

We have on a few occasions come across a syncrepl problem where some deletion records do not happen everywhere. Today I was looking at two such problems; Usually the procedure is to delete the old record, then add a new record.

#1: deletion of A records in ou=dns ldapmaster has it deleted. ldapslave03 has it deleted. (syncrepl with ldapmaster) dns02, dns04 has it deleted. (syncrepl with ldapslave03) dns01, dns03 still has the record. (syncrepl with ldapslave03)

In detail, from dns03.unix, which now has two records:

dn: DNSRecord=A1,DNSHostName=@,DNSZoneName=customer.com,ou=dns,dc=work objectClass: DNSARecord DNSRecord: A1 DNSHostName: @ DNSType: A DNSIPAddr: zz.yy.xx.ww (new IP in reverse) DNSTTL: 600 structuralObjectClass: DNSARecord entryCSN: 20101021232823.000000Z#000002#000#000000 entryUUID: a43076ee-71b6-102f-95dd-c33ccbc720c3 creatorsName: cn=admin,dc=work createTimestamp: 20101021232823Z modifiersName: cn=admin,dc=work modifyTimestamp: 20101021232823Z

dn: DNSRecord=A,DNSHostName=@,DNSZoneName=customer.com,ou=dns,dc=work objectClass: DNSARecord DNSRecord: A DNSHostName: @ DNSType: A DNSIPAddr: dd.cc.bb.aa (old IP in reverse, should have been deleted) DNSTTL: 600 structuralObjectClass: DNSARecord entryCSN: 20091225133051.000000Z#00000b#000#000000 entryUUID: 77344376-85a5-102e-9deb-dbfa8f00ebbd creatorsName: cn=admin,dc=work createTimestamp: 20091225133051Z modifiersName: cn=admin,dc=work modifyTimestamp: 20091225133051Z

#2 was pretty much same situation, except this time only dns03.unix missed the deletion. There is nothing much in the logs on either dns03.unix, nor ldapslave03. But LogLevel is only set to "sync".

Is this related to:

http://www.openldap.org/its/index.cgi/Software Bugs?id=6059

it is peculiar that it is only occurring on delete records.