Kevin M. Myer wrote:
Quoting David Boreham <david_list(a)boreham.org>:
> Try looking in the access and error logs on the replica server (the
> server that is receiving this update).
> That should tell us which operation is failing. Exactly what is going
> on I'm not sure, I've not seen a
> problem like this before. Perhaps someone else on the list has.
Here's the action its trying to perform:
[16/Dec/2005:09:06:16 -0500] conn=900959 op=3 EXT
oid="2.16.840.1.1137220.127.116.11" name="Netscape Replication Start
[16/Dec/2005:09:06:16 -0500] conn=900959 op=3 RESULT err=0 tag=120
[16/Dec/2005:09:06:16 -0500] conn=900959 op=4 DEL
[16/Dec/2005:09:06:16 -0500] conn=900959 op=4 RESULT err=1 tag=107
nentries=0 etime=0 csn=43a2c9d8000000010000
[16/Dec/2005:09:06:18 -0500] conn=900959 op=5 EXT
oid="2.16.840.1.113718.104.22.168" name="Netscape Replication End
The replication to the slave (garnet) did occur properly for the
account that was being deleted.
Is this the access log from one of the masters?
Its also not inhibiting other changes from occuring in the the same
replication session. I just made a minor modification to my account
and it replicated while the deletion of the account giving errors
failed. I restarted the server that was receiving the changes, and
now the deletion operation that was failing isn't occuring at all :/
So I guess I'll just manually delete the account, since the one master
seems to be convinced that the change went through.
So after the restart, everything is ok?