Re: 2.3.1 Replication is throwing scary errors

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

Re: 2.3.1 Replication is throwing scary errors

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

Re: 2.3.1 Replication is throwing scary errors

Michael Grimm wrote: > First of all: Major improvement by this patch applied to 2.3.1, there are no > more hanging processes. From my point of view: the recent commit from Timo did not only fix those hanging processes ... > But: I do find quite a number of error messages like: > > Jun

Re: 2.3.1 Replication is throwing scary errors

Regarding my comment below - it looks like a false alarm on my part. The commit referenced below hasn't gone into master-2.3 yet which meant it wasn't included when I rebuilt earlier today. That was was an incorrect assumption I made. I have since manually patched it into master-2.3 and it

Re: 2.3.1 Replication is throwing scary errors

On 7 Jun 2018, at 11.43, Michael Grimm wrote: > > Timo Sirainen: > >> Should be fixed by >> https://github.com/dovecot/core/commit/a952e178943a5944255cb7c053d970f8e6d49336 > > please ignore my ignorance but shouldn't one add this commit regarding > src/doveadm/client-connection-tcp.c ... > >

Re: 2.3.1 Replication is throwing scary errors

On 6/7/18, 3:43 AM, "dovecot on behalf of Michael Grimm" wrote: Timo Sirainen: > Should be fixed by > https://github.com/dovecot/core/commit/a952e178943a5944255cb7c053d970f8e6d49336 please ignore my ignorance but shouldn't one add this commit regarding

Re: 2.3.1 Replication is throwing scary errors

Timo Sirainen: Should be fixed by https://github.com/dovecot/core/commit/a952e178943a5944255cb7c053d970f8e6d49336 please ignore my ignorance but shouldn't one add this commit regarding src/doveadm/client-connection-tcp.c ...

Re: 2.3.1 Replication is throwing scary errors

Am 2018-06-07 08:48, schrieb Remko Lodder: On Thu, Jun 07, 2018 at 08:04:49AM +0200, Michael Grimm wrote: Conclusion: After 12 hours of running a patched FBSD port I do get those error messages but replictaion seems to work now. But, I still have the feeling that there might something else

Re: 2.3.1 Replication is throwing scary errors

Am 2018-06-07 07:34, schrieb Remko Lodder: On 7 Jun 2018, at 07: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

Re: 2.3.1 Replication is throwing scary errors

And 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

Re: 2.3.1 Replication is throwing scary errors

> On 7 Jun 2018, at 07: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

Re: 2.3.1 Replication is throwing scary errors

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

Re: 2.3.1 Replication is throwing scary errors

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 wrote: > > Should be fixed by > https://github.com/dovecot/core/commit/a952e178943a5944255cb7c053d970f8e6d49336 > >

Re: 2.3.1 Replication is throwing scary errors

Should be fixed by https://github.com/dovecot/core/commit/a952e178943a5944255cb7c053d970f8e6d49336

Re: 2.3.1 Replication is throwing scary errors

On 1/06/2018 2:47 AM, Michael Grimm wrote: On 31. May 2018, at 18:09, Remko Lodder wrote: On 31 May 2018, at 17:52, Michael Grimm wrote: I would love to get some feedback from the developers regarding: #) are commercial customers of yours running 2.3 master-master replication without

Re: 2.3.1 Replication is throwing scary errors

On 31. May 2018, at 18:09, Remko Lodder wrote: >> On 31 May 2018, at 17:52, Michael Grimm wrote: >> I would love to get some feedback from the developers regarding: >> >> #) are commercial customers of yours running 2.3 master-master replication >> without those issues reported in this

Re: 2.3.1 Replication is throwing scary errors

> On 31 May 2018, at 17:52, Michael Grimm wrote: > > Reuben Farrelly wrote: > >> Checking in - this is still an issue with 2.3-master as of today (2.3.devel >> (3a6537d59)). > > That doesn't sound good, because I did hope that someone has been working on > this issue ... > >> I haven't

Re: 2.3.1 Replication is throwing scary errors

Reuben Farrelly wrote: > Checking in - this is still an issue with 2.3-master as of today (2.3.devel > (3a6537d59)). That doesn't sound good, because I did hope that someone has been working on this issue ... > I haven't been able to narrow the problem down to a specific commit. The best >

Re: 2.3.1 Replication is throwing scary errors

Hi, Checking in - this is still an issue with 2.3-master as of today (2.3.devel (3a6537d59)). I haven't been able to narrow the problem down to a specific commit. The best I have been able to get to is that this commit is relatively good (not perfect but good enough):

Re: 2.3.1 Replication is throwing scary errors

ail] /Message: 1 />/Date: Fri, 6 Apr 2018 15:04:35 +0200 />/From: Michael Grimm <https://dovecot.org/mailman/listinfo/dovecot>> />/To: Dovecot Mailing List https://dovecot.org/mailman/listinfo/dovecot>> />/Subject: Re: 2.3.1 Replication is throwing scary errors />/Message-ID

Re: 2.3.1 Replication is throwing scary errors

Hey all, I've been affected by these replication issues too and finally downgraded back to 2.2.35 since some newly created virtual domains/mailboxes weren't replicated *at all* due to the bug(s). My setup is more like a master-slave, where I only have a rather small virtual machine as the slave

Re: 2.3.1 Replication is throwing scary errors

> 2. ??? both systems ran ok with no errors for 10 days. >>>> 3. ??? Last night I shutdown mx2 and restarted it a few hours later >>>> 4. ??? within minutes i was getting the following types of errors on mx2 >>>> >>>> May 06

Re: 2.3.1 Replication is throwing scary errors

Hi Andy Andy Weal wrote > Hi all, > > New to the mailing lists but have joined up because of above 2.3.1 > Replication is throwing scary errors > > > Brief system configuration > MX1 - Main > Freebsd 11.1-Release-p9 > Hosted on a Vultr VM in

Re: 2.3.1 Replication is throwing scary errors

for now, Andy Hi, [Formatting is a bit rough, replying from a trimmed digest email] /Message: 1 />/Date: Fri, 6 Apr 2018 15:04:35 +0200 />/From: Michael Grimm <https://dovecot.org/mailman/listinfo/dovecot>> />/To: Dovecot Mailing List https://dovecot.org/mailman/listinfo/d

Re: 2.3.1 Replication is throwing scary errors

) > > > > ? Before i venture down the rabbit hole of fault finding and excess > > coffee consumption I was wondering if any of you had any updates on the > > problems discussed below. > > > > > > Cheers for now, > > Andy > > > > > > &g

Re: 2.3.1 Replication is throwing scary errors

i, 6 Apr 2018 15:04:35 +0200 />/From: Michael Grimm <https://dovecot.org/mailman/listinfo/dovecot>> />/To: Dovecot Mailing List https://dovecot.org/mailman/listinfo/dovecot>> />/Subject: Re: 2.3.1 Replication is throwing scary errors />/Message-ID: https://dov

Re: 2.3.1 Replication is throwing scary errors

Hi, [Formatting is a bit rough, replying from a trimmed digest email] Message: 1 Date: Fri, 6 Apr 2018 15:04:35 +0200 From: Michael Grimm <trash...@ellael.org> To: Dovecot Mailing List <dovecot@dovecot.org> Subject: Re: 2.3.1 Replication is throwing scary errors Message-ID: <e7e

Re: 2.3.1 Replication is throwing scary errors

Reuben Farrelly wrote: > From: Michael Grimm >> [This is Dovecot 2.3.1 at FreeBSD STABLE-11.1 running in two jails at >> distinct servers.] >> I did upgrade from 2.2.35 to 2.3.1 today, and I do become pounded by error >> messages at server1 (and vice versa at server2) as

Re: 2.3.1 Replication is throwing scary errors

> On 4 Apr 2018, at 01:34, Reuben Farrelly wrote: > > Hi, > >> -- >> Message: 2 >> Date: Mon, 2 Apr 2018 22:06:07 +0200 >> From: Michael Grimm >> To: Dovecot Mailing List >> Subject: 2.3.1

Re: 2.3.1 Replication is throwing scary errors

Hi, > There is also a second issue of a long standing race with replication > occurring somewhere whereby if a mail comes in, is written to disk, is > replicated and then deleted in short succession, it will reappear again to > the MUA. I suspect the mail is being replicated back from the

Re: 2.3.1 Replication is throwing scary errors

Hi, -- Message: 2 Date: Mon, 2 Apr 2018 22:06:07 +0200 From: Michael Grimm To: Dovecot Mailing List Subject: 2.3.1 Replication is throwing scary errors Message-ID: <29998016-d62f-4348-93d1-613b13da9...@ellael.org>

Re: 2.3.1 Replication is throwing scary errors

Michael Grimm wrote: > [This is Dovecot 2.3.1 at FreeBSD STABLE-11.1 running in two jails at > distinct servers.] > > I did upgrade from 2.2.35 to 2.3.1 today, and I do become pounded by error > messages at server1 (and vice versa at server2) as follows: > > | Apr