On 17.02.2013, at 06:23, Timo Sirainen tss@iki.fi wrote:
On 17.2.2013, at 7.06, Timo Sirainen tss@iki.fi wrote:
On 17.2.2013, at 0.12, Michael Grimm trashcan@odo.in-berlin.de wrote:
Hmm. Both jails run at distinct servers. ssh replication uses different domains, though. But, both jails are named identically "test", and both jails resolve to identical hostnames "test" if using "hostname". But, a "hostname -f" is lacking to return "test.mx1.invalid" and "test.mx2.invalid", respectively (although a "nslookup test" does). Hmm, do you think I should need to provide different hostnames in both jails?
That's the problem most likely. I'd guess Dovecot sees both servers as having "test" as the hostname and each server thinks it's the one that should be doing the locking and not the other.
See if this helps: http://hg.dovecot.org/dovecot-2.2/rev/e7aabd79c9d5
Good news! Those identical hostnames at both servers broke replicator. Now, with v2.2.beta1 (1dd1e88ba0a2) I cannot break replicator any longer how many messages I do inject at both servers simultaneously. (Tested a couple of times up to 2000 mails at every server.)
Although even if it does, other parts of Dovecot still use only the hostname part to guarantee global uniqueness of things. So better to have unique hostnames.
What parts of Dovecot would be involved? I'm curious because my production mailservers use identical hostnames in their jails ever since running Dovecot (starting 1.x).
Thanks for the new replicator code, I really appreciate your work! And, from my point of view I will consider replicator v2.2 ready for production.
With kind regards, Michael