Hi,
We're running Cyrus 3.2.x
I recently moved a replica Cyrus IMAP server to a different box - when I
tried to re-start replication, the replica grumbled in the logs:
Oct 20 12:52:14 syncserver[63316]: higher modseq on replica user.fred.Logs
- 1707305 < 1751211
I had to leave the box then - but from what I quickly read looking around,
that would "stop" replication for safety reasons, because something had
changed on the replica.
However, getting back to the box now - the source has finished processing
the run-log etc. - and sync_server is still running on the source.
The replica logged a bunch of 'modseq' warnings for various mailboxes - but
still seems to be tracking the source.
So my question is - is it safe it ignore these warnings? - And presume it's
ok? - Because the source is still happily running sync_server and sending
the changes?
I'm not sure how this happened - the original replica was on a machine that
had imapd shutdown, then the filesystem snapshotted and moved to another
box (and spun up there).
Normally no one can log into the replica.
I'm also sure in the past - the replica has been logged into by me (and
noted changes on the replica, migrate back to the source) - in fact, I just
did this - and the mailboxes on the replica seem fine / up to date (and
flagging a message - it does, indeed replicate back to the source the next
time the source runs a sync for that mailbox).
So ultimately - is it safe to ignore this warning? e.g. Will it happen only
for each mailbox once?
-Karl
------------------------------------------
Cyrus: Devel
Permalink:
https://cyrus.topicbox.com/groups/devel/T0d0d425a1f58c10c-M9cfe9bbb1431ca1e53a175bc
Delivery options: https://cyrus.topicbox.com/groups/devel/subscription
