Re: (ITS#4588) ./scripts/test007-replication failed (exit 49)

[ando@sys-net.it]

> Pierangelo Masarati wrote:
>> It would be interesting to
>> see your (server, slave) logs, if you can provide them somewhere (e.g.
>> zipped to the ftp site or in a location of your convenience).
>
> http://www.stroeder.com/temp/openldap/its4588/

I need to amend my previous posting.  The error that shows up is a failed
bind because the entry "cn=manager,dc=example,dc=com" could not be looked
up in the replica's database.  It __should__ be there, though, but your
database got corrupted shortly before.  This is waht appears in
slapd.2.log shortly before that operation:

=> bdb_dn2id("dc=example,dc=com")
<= bdb_dn2id: get failed: DB_NOTFOUND: No matching key/data pair found
(-30989)
bdb_modify: cn=James A Jones 1,ou=Alumni
Association,ou=People,dc=example,dc=com
send_ldap_result: conn=1 op=2 p=3
send_ldap_result: err=16673 matched="" text="invalid transaction identifier"
send_ldap_response: msgid=3 tag=103 err=16673

I've never seen something like that, but I suspect something in back-bdb,
or in the Berkeley DB itself.  I suggest you try running that test, e.g.,
under valgrind or anything like that, to catch where things go weird.  I
use Berkeley 4.2.52 with patches, BTW.

p.



Ing. Pierangelo Masarati
Responsabile Open Solution
OpenLDAP Core Team

SysNet s.n.c.
Via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
------------------------------------------
Office:   +39.02.23998309          
Mobile:   +39.333.4963172
Email:    pierangelo.masarati@sys-net.it
------------------------------------------