We check via IMAP that the values at the ends are not different for everything we care about. There are a range of reasons why the cyrus.index is different - it's not a binary sync. I've attached the perl module we use and the script that drives it - it's not super-reusable right now, you need to strip all the FastMail specific crud - but it gives you an outline of a way to do it. (we also tail the syslogs looking for errors - you can't wait until the weekly deep check if you want to catch errors quickly) Bron. On Mon, Aug 11, 2014, at 05:04 PM, Sven Schwedas wrote: > Hi all, > > Is there a way to quickly verify that replication is working (for e.g. > nagios monitoring)? It seems that file differences in e.g. cyrus.index > happen even when replication succeeds, and parsing the whole mail log > for error messages seems a bit overkill. > > -- > Mit freundlichen Grüßen, / Best Regards, > Sven Schwedas > Systemadministrator > TAO Beratungs- und Management GmbH | Lendplatz 45 | A - 8020 Graz > Mail/XMPP: sven.schwedas@xxxxxx | +43 (0)680 301 7167 > http://software.tao.at > > ---- > Cyrus Home Page: http://www.cyrusimap.org/ > List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ > To Unsubscribe: > https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus > Email had 1 attachment: > + signature.asc > 1k (application/pgp-signature) -- Bron Gondwana brong@xxxxxxxxxxx
Attachment:
CheckReplication.pm
Description: Perl program
Attachment:
checkreplication.pl
Description: Perl program
---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
