On Thu, 2012-03-08 at 11:26 +0100, Michael Grimm wrote:
Let me start with replicator's configuration ...
Below is a configuration for virtual user setup. [...] service doveadm { # if you're using a single virtual user, set this to # start ssh as vmail (not root) user = vmail }
... that led to the following complaints at start-up:
| dovecot: master: Dovecot v2.1.1 (d66568d34e40) starting up | dovecot: doveadm: Error: Error reading configuration: net_connect_unix(/var/run/dovecot/config) failed: Permission denied | [...] | (repeatedly, presumably for the number of users in userdb?)
You can do for example:
service config { unix_listener config { user = vmail } }
Now some observations regarding replicator:
I see a lot of error messages whenever replicator is in action like (although everything is being synced correctly):
| <mail.err> mail dovecot: dsync-local(test): Error: remote: dsync-remote(test): Info: save: box=INBOX, uid=27, msgid=<3V2JfH5Kv4z7Ft@example.tld>, size=547, from=test@example.tld (admin), flags=()
| <mail.info> mail dovecot: dsync-local(test): Error: remote: dsync-remote(test): Info: flag_change: box=TEST, uid=27568, msgid=<20120307144810.6360A74F013@example.tld>, size=435, from=test@example.tld, flags=(\Seen)
JFTR: I do have mail_log plugin activated.
Hmm. Right. I guess all the logging should go to the log files instead of via the ssh pipe. Of course that would also require that dsync has write access to your log files.
It seems to me, that whenever a larger number of mails arrive on both servers simultaneously, the replicator gets into trouble [1]. I am unsure if one can expect that a replicator should deal with such stress, though. Or?
Were these mails delivered via LMTP or dovecot-lda?
The locks should prevent duplicates I think, so there's something still going wrong.