Re: 2.3.1 Replication is throwing scary errors
Aaaaand I forgot to CC the list, sorry for that, it's way too early in the morning :P
On 07.06.18 - 07:39, Thore Bödecker wrote:
What does the output of these two commands show after that error has been logged?
doveadm replicator status
doveadm replicator dsync-status
If there are *waiting failed* requests, that never make it "through" (after being temporarily in state *queued failed* and then returning to *waiting failed*) this means there is something wrong with the replication.
You can try forcing replication of all known users using
doveadm replicator replicate '*'
And see if that resolves the failed requests, but I doubt it.
Please let us know how your status outputs look like.
Cheers, Thore
-- Thore Bödecker
GPG ID: 0xD622431AF8DB80F3 GPG FP: 0F96 559D 3556 24FC 2226 A864 D622 431A F8DB 80F3
On 07.06.18 - 15:21, Reuben Farrelly wrote:
Still not quite right for me.
Jun 7 15:11:33 thunderstorm.reub.net dovecot: doveadm: Error: dsync(lightning.reub.net): I/O has stalled, no activity for 600 seconds (last sent=mail, last recv=mail (EOL)) Jun 7 15:11:33 thunderstorm.reub.net dovecot: doveadm: Error: Timeout during state=sync_mails (send=mails recv=recv_last_common)
I'm not sure if there is an underlying replication error or if the message is just cosmetic, though.
Reuben
On 7/06/2018 4:55 AM, Remko Lodder wrote:
Hi Timo,
Yes this seems to work fine so far. I’ll ask the people to add it to the current FreeBSD version..
Cheers Remko
On 6 Jun 2018, at 19:34, Timo Sirainen
mailto:tss@iki.fi> wrote: Should be fixed by https://github.com/dovecot/core/commit/a952e178943a5944255cb7c053d970f8e6d49...
Hey all,
almost 48h ago I upgraded both my instances to 2.3.1 again to see if the new patches would fix the replication issues for me.
So far, the result is: great.
I haven't been able to provoke any kind of I/O stall or persisting queued/failed resync requests in my replication setup.
Newly added users are replicated instantly upon the first received mails and the home directory gets created without issues now too.
For reference: I'm using the official 2.3.1 tarball together with the 3 attached patches, that have been taken from GitHub diffs/commits linked to me by Aki in the #dovecot channel.
I can only encourage everyone to try out 2.3.1 again with these 3 patches to make sure it is rock-solid so that we might get a proper and stable 2.3.2 release soon-ish :)
PS: For the Arch Linux users among you the dovecot-2.3.1-5 package in the official repo contains said three patches :)
Cheers, Thore
-- Thore Bödecker
GPG ID: 0xD622431AF8DB80F3 GPG FP: 0F96 559D 3556 24FC 2226 A864 D622 431A F8DB 80F3
Err, attached the wrong patches.
the correct ones are attached to this mail (0004, 0005, 0006).
On 13.06.18 - 13:29, Thore Bödecker wrote:
For reference: I'm using the official 2.3.1 tarball together with the 3 attached patches, that have been taken from GitHub diffs/commits linked to me by Aki in the #dovecot channel.
Cheers, Thore
-- Thore Bödecker
GPG ID: 0xD622431AF8DB80F3 GPG FP: 0F96 559D 3556 24FC 2226 A864 D622 431A F8DB 80F3
participants (1)
-
Thore Bödecker