On Sun, 2013-09-22 at 00:13 +0300, Timo Sirainen wrote:
> > One side has uidnext=23 and the other side has uidnext=24. You're
> deleting the last message with uid=22, so the uidnext=23 is correct.
> The other side however thinks that the same mail's uid is 23. There
> must be something wrong with
On 22.9.2013, at 0.02, Timo Sirainen wrote:
> The A and B node logs are exactly the same. I think you sent the same ones
> for both? Anyway, one of the sides is enough. The interesting parts are:
>
> 1375808883.299424 O: NINBOX y 0314c806e3fa0052d26a736ac1b0
> 1375795939
On 8.8.2013, at 11.21, Simon Fraser wrote:
> I ran two tests: one using 'doveadm expunge' and one deleting the
> message using mutt. Since the hosts mentioned so far have a copy of my
> full mailbox on, I re-ran the tests (with the same results) on a test
> server with a fresh mailbox on, so ther
On Mon, 2013-08-19 at 12:08 +0100, Simon Fraser wrote:
> Are there any more tests I can run for this?
I've tried an ssh-based replication configuration, and still experience
the same symptoms. Going through a director proxy also doesn't help (as
expected, that one, since I was already only connec
Are there any more tests I can run for this?
Thanks,
Simon.
On Thu, 2013-08-08 at 09:21 +0100, Simon Fraser wrote:
> On Tue, 2013-08-06 at 19:15 +0300, Timo Sirainen wrote:
>
> > > Presumably it's thinking the "-r /tmp/dsync-rawlog" is a mail location?
> > > I've tried changing its location in
On Tue, 2013-08-06 at 19:15 +0300, Timo Sirainen wrote:
> > Presumably it's thinking the "-r /tmp/dsync-rawlog" is a mail location?
> > I've tried changing its location in the appends, but it doesn't make a
> > difference.
>
> Oops, I messed up the parameter order. It was supposed to have -s sta
On 6.8.2013, at 18.58, Simon Fraser wrote:
> On Tue, 2013-08-06 at 16:45 +0300, Timo Sirainen wrote:
>
>>>
>>> Weird, I was sure that would have worked. Well, maybe rawlogs would
>> show something interesting. I should probably add a proper option for
>> them, but attached a patch to enable for
On Tue, 2013-08-06 at 16:45 +0300, Timo Sirainen wrote:
> >
> > Weird, I was sure that would have worked. Well, maybe rawlogs would
> show something interesting. I should probably add a proper option for
> them, but attached a patch to enable for now. Be sure to
> mkdir /tmp/dsync-rawlogs with en
On 6.8.2013, at 16.42, Timo Sirainen wrote:
> On 6.8.2013, at 15.59, Simon Fraser wrote:
>
>>> Try disabling replicator plugin from only one side, so there's not
>>> possibility of two dsyncs running at the same time. That should be
>>> prevented already by locking though.
>>
>> I disabled t
On 6.8.2013, at 15.59, Simon Fraser wrote:
>> Try disabling replicator plugin from only one side, so there's not
>> possibility of two dsyncs running at the same time. That should be prevented
>> already by locking though.
>
> I disabled the replication on node b, restarted both, and connected
On Tue, 2013-08-06 at 14:30 +0300, Timo Sirainen wrote:
> Here's another idea:
>
Thank you for still looking into this
> Try disabling replicator plugin from only one side, so there's not
> possibility of two dsyncs running at the same time. That should be prevented
> already by locking thoug
On 6.8.2013, at 14.30, Timo Sirainen wrote:
> Here's another idea:
>
> Try disabling replicator plugin from only one side, so there's not
> possibility of two dsyncs running at the same time. That should be prevented
> already by locking though.
>
> The servers have different hostnames, right
On 1.8.2013, at 17.02, Simon Fraser wrote:
>>> Connect with a mail client, and delete the message - without delayed
>>> expunge. So, for example, mutt (press 'd' then '$' to sync the mailbox),
>>> or Evolution set to immediately delete.
>>
>> Can you reproduce this by disabling automatic replica
Hello,
For what it's worth, still experiencing these symptoms with 2.2.5.
Thanks,
Simon.
On Thu, 2013-08-01 at 15:02 +0100, Simon Fraser wrote:
> On Thu, 2013-08-01 at 15:09 +0300, Timo Sirainen wrote:
> > On Fri, 2013-07-26 at 11:28 +0100, Simon Fraser wrote:
> >
> > > I am running dovecot 2.
On Thu, 2013-08-01 at 15:09 +0300, Timo Sirainen wrote:
> On Fri, 2013-07-26 at 11:28 +0100, Simon Fraser wrote:
>
> > I am running dovecot 2.2.2 with tcp based replication, and experiencing
> > some duplicated emails. `doveconf -n` output is below.
>
> Are both of the servers using the same mail
On Fri, 2013-07-26 at 11:28 +0100, Simon Fraser wrote:
> I am running dovecot 2.2.2 with tcp based replication, and experiencing
> some duplicated emails. `doveconf -n` output is below.
Are both of the servers using the same mailbox format?
> I have narrowed it down to the following scenario:
>
Hi, is there anything I can do to help debug this - any tools I should
run to discover where the cause might be?
Simon.
On Mon, 2013-07-29 at 10:05 +0100, Simon Fraser wrote:
> On Fri, 2013-07-26 at 20:26 +0200, Daniel Parthey wrote:
> > Hi Simon,
> >
> > Version 2.2.2 is not current any more.
On Fri, 2013-07-26 at 20:26 +0200, Daniel Parthey wrote:
> Hi Simon,
>
> Version 2.2.2 is not current any more. I would try to update to the
> latest stable version 2.2.4 first, since some dsync bugs have been
> fixed between 2.2.2 and 2.2.4:
I've now upgraded to 2.2.4 (and pigeonhole 0.4.1 from
Hi Simon,
Version 2.2.2 is not current any more. I would try to update to the latest
stable version 2.2.4 first, since some dsync bugs have been fixed between 2.2.2
and 2.2.4:
http://www.dovecot.org/doc/NEWS-2.2
Regards
Daniel
On Fri, 2013-07-26 at 17:47 +0200, Reindl Harald wrote:
>
> Am 26.07.2013 17:41, schrieb Simon Fraser:
> > I've just converted the mailboxes to mdbox, so mail_location now looks
> > like this:
> >
> > mail_location = mdbox:~/mail
> >
> > The log entry about messages reappearing no longer happens
Am 26.07.2013 17:41, schrieb Simon Fraser:
> I've just converted the mailboxes to mdbox, so mail_location now looks
> like this:
>
> mail_location = mdbox:~/mail
>
> The log entry about messages reappearing no longer happens, but the
> symptoms are the same - if I delete a message, it instantly
I've just converted the mailboxes to mdbox, so mail_location now looks
like this:
mail_location = mdbox:~/mail
The log entry about messages reappearing no longer happens, but the
symptoms are the same - if I delete a message, it instantly reappears.
Simon.
On Fri, 2013-07-26 at 11:28 +0100, S
I am running dovecot 2.2.2 with tcp based replication, and experiencing
some duplicated emails. `doveconf -n` output is below.
I have narrowed it down to the following scenario:
An email arrives, and is successfully replicated to both nodes. It is in
INBOX/new/ at this point on both servers.
C
23 matches
Mail list logo
