--On Wednesday, February 18, 2009 9:55 AM -0500 Francis Swasey
<Frank.Swasey(a)uvm.edu> wrote:
> Is there anything that should be logged that would help identify
the
> failure (I'm currently using loglevel of "stats sync" on the master
and
> all the replicas) ?
Some further digging into this and I see that the changes this morning to
at least one of these entries are not present in the accesslog database.
No wonder the change didn't make it to the replica's, it didn't even make
it into the accesslog on the master (although auditlog sees the change
and the dc=uvm,dc=edu database on the master has the change).
Any suggestions on where to look in the accesslog overlay to see why
these modify operations are not being recorded?
Well, I'd generally check db_stat -c to make sure you didn't run out of
locks/lockers/lock objects in the accesslog DB to start. I assume you have
reasonable logging on the master, so that you can see if any errors were
thrown when the MODs that didn't get written out occurred, etc.
--Quanah
--
Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra :: the leader in open source messaging and collaboration