Problem with initial sync on new mailbox in a replicated setup

[Christian Mack]

Hello

Am 06.04.22 um 10:35 schrieb ppq at tuta.io:
> Hello,
> 
> I run a two-node replicated setup with director + dovecot and replication between the two nodes.
> The setup is a couple of years old and has been working properly until recently, so I suspect some type of regression.
> 
> I'm having an issue with replication and merging of newly created mailboxes. Old mailboxes work properly.
> 
> When creating a new mailbox, the two nodes will not replicate and sync the new mailbox. I have to manually "merge" the mailbox via a "doveadm sync -1f..." command, after which all works properly. This has not been the case in the past, so I'm trying to debug the issue.
> 
> When syncing manually, I get the following error:
> -----------------------------
> # doveadm -v sync -df  -u 'testaccount at mydomain.ext'
> doveadm(testaccount at mydomain.ext)<38041><wl3tAQ5LTWKZlAAAxdOQ8Q>: Warning: Mailbox changes caused a desync. You may want to run dsync again: Remote lost mailbox GUID 6bfcbb2f92484d624b890000c5d390f1 (maybe it was just deleted?)
> ----------------------------
> 
> I have to sync once with a one-way merge using sync -1f and after the sync works properly.
> 
> My setup is running Dovecot CE 2:2.3.18-4+debian11 from the dovecot.org repository installed on debian bullseye. The replicaiton is dove via TCP plaintext connection.
> 
> Below I'm attaching some debug logs, for both sync -1f and sync -f.
> 
> Is this a normal behavior or is this a bug ?
> 
> Kind regards,
> Dave
> 
[...]
> 2022-04-06 10:12:17 doveadm(testaccount at mydomain.ext)<38324><WJH0HGFLTWK0lQAAxdOQ8Q>: Debug: brain M: Mailbox Drafts: local=6bfcbb2f92484d624b890000c5d390f1/0/1, remote=4b70ba2389484d628fa91300660b22f9/0/1: GUIDs conflict - will be merged later
> 2022-04-06 10:12:17 doveadm(testaccount at mydomain.ext)<38324><WJH0HGFLTWK0lQAAxdOQ8Q>: Debug: brain M: Mailbox INBOX: local=08b6a62792484d624b890000c5d390f1/0/1, remote=4d70ba2389484d628fa91300660b22f9/0/1: GUIDs conflict - will be merged later
> 2022-04-06 10:12:17 doveadm(testaccount at mydomain.ext)<38324><WJH0HGFLTWK0lQAAxdOQ8Q>: Debug: brain M: Mailbox Junk: local=6afcbb2f92484d624b890000c5d390f1/0/1, remote=4c70ba2389484d628fa91300660b22f9/0/1: GUIDs conflict - will be merged later
> 2022-04-06 10:12:17 doveadm(testaccount at mydomain.ext)<38324><WJH0HGFLTWK0lQAAxdOQ8Q>: Debug: brain M: Mailbox Sent: local=69fcbb2f92484d624b890000c5d390f1/0/1, remote=4a70ba2389484d628fa91300660b22f9/0/1: GUIDs conflict - will be merged later
> 2022-04-06 10:12:17 doveadm(testaccount at mydomain.ext)<38324><WJH0HGFLTWK0lQAAxdOQ8Q>: Debug: brain M: Mailbox Trash: local=68fcbb2f92484d624b890000c5d390f1/0/1, remote=4970ba2389484d628fa91300660b22f9/0/1: GUIDs conflict - will be merged later
[-cut-]
Problem is, that those folders are already created on the target system
by other means than replication.
Therefore they exist already, but with different GUIDs.
With that the replication can not create those folders on the target
side and refuses to sync mails into the existing ones.
That is, till you explicitly want to merge.

You have to stop automatic creation on the target machine, before doing
initial sync.


Kind regards,
Christian Mack

-- 
Christian Mack
Universität Konstanz
Kommunikations-, Informations-, Medienzentrum (KIM)
Abteilung IT-Dienste Forschung und Lehre
78457 Konstanz
+49 7531 88-4416

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5351 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://dovecot.org/pipermail/dovecot/attachments/20220407/33455dfd/attachment.bin>