On 16.2.2013, at 20.26, Michael Grimm trashcan@odo.in-berlin.de wrote:
Timo Sirainen tss@iki.fi wrote:
I did a bunch of dsync fixes today in hg. With the new locking behavior (and other fixes) you shouldn't be able to break it anymore.
Sorry to say, but I am still able to break replicator with v2.2.beta1 (35194cf0693e) under the conditions outlined below.
I wonder if locking is working correctly in your setup. Your users have home directories, right? Dovecot should be creating .dovecot-sync.lock files in there during the sync.
This is v2.2.beta1 (78bdcb6642c7) with freshly created mailboxes "test" at both servers "mx1" and "mx2", and replicator uses ssh for remote access. Both servers run a recent postfix, use lmtp for local delivery, and "test" is a virtual user.
I might add that both servers run inside FreeBSD jails (if that might make the difference to your test setup.
Inside jail Dovecot sees two different hostnames (same as "hostname" command)?
Good: I cannot find any "Error:" entries in both logfiles any longer.
What about Warning?