similar to: Replication: long detalys

Displaying 20 results from an estimated 10000 matches similar to: "Replication: long detalys"

2013 Oct 24
0
Replication not happening on 2.2
Hello, first - thanks for the help in getting dovecot 2.2 compiled and installed on Debian. I have Dovecot 2.2 running now on two servers, and to test replication, I am polling mail on one server whilst the other creates mail regularly from crontab output. I have replication set up, but nothing at all is appearing on the other server, and I do not have any dsync / doveadm messages in
2013 Sep 26
0
Dsync: Mailbox changes caused a desync.
Hi! Here such synchronization error: dovecot: dsync-local(alex at aaa.com): Warning: Mailbox changes caused a desync. You may want to run dsync again. dovecot: dsync-remote(alex at aaa.com): Warning: /var/mail/virtual/aaa.com/alex/.INBOX.System/dovecot-uidlist: Duplicate file entry at line 2298: 1380157263.M585262P25253.mail1.aaa.com,S=2476,W=2553 (uid 3645 -> 3662) dovecot: dsync-remote(alex
2013 Jan 31
1
dsync replication errors
Hi I'm trying to build a cluster of two servers with dsync replication (based on http://wiki2.dovecot.org/Replication). My test setup works fine for very simple tests, I can log in to both servers, copy a message to one of the servers and it successfully apperars in the other account. But, if I try to copy a large amount of messages at once to one of the accounts, my maillogs get flodded with
2013 Oct 20
2
Upgrade from 2.1 to 2.2 on Debian
Hello, I am currently running Dovecot 2.1 on current Debian and need to upgrade to 2.2 to use the replication features. I understand that I therefore need to compile Dovecot myself. I am using a MySQL database for users authentication, therefore I need to compile Dovecot with mysql support: *./configure --with-mysql* Unfortunately this terminates with: *configure: error: Can't build with
2013 Dec 22
1
Duplicated (but only for unread) messages after second rsync pass...
Ok, I know I should probably be using dsync for this, but I'm more familiar with rsync, and didn't think this would be a problem. Here is what I am doing, and what is apparently happening (only done this once, but I'm guessing it will happen each time): rsync -avHP /mnt/vmail/example.com/user1/ /var/vmail/example.com/user1/ chown -R vmail:vmail /var/vmail/example.com Ok, so far
2016 Mar 01
2
Dsync induces redundant mail after rapid append/expunge repeatedly
?I meet the problem about dsync with ?expunge. The problems is expunged mail would reappear after dsyncing and it is easily to reproduce. ?Environment Settings: - Two servers(serverA, serverB) both enabled plugin "*replication"* - And more detail get by "dovecot -n" show below ?Reproduce flow: ?- ?Run two processes pA and pB both would run in while loop ?- pA?(All behavior is
2017 Mar 01
0
Expunged message reappeared, giving a new UID
Please help. How to stop email replication is on going. dsync-server : Warning Expunged message reappeared, giving a new UID
2019 Jul 13
5
Replication issue 2.3.7
Hello! I noticed these in the logs since upgrading from 2.3.6. to 2.3.7: Jul 13 11:52:10 turin dovecot: doveadm: Error: dsync-remote(reio at mrstuudio.ee)</1ekE7qbKV2gYwAAsNnMGQ>: Error: Exporting mailbox INBOX failed: Mailbox attribute vendor/vendor.dovecot/pvt/server/sieve/files/MR lookup failed: Mailbox attributes not enabled Jul 13 11:52:11 turin dovecot: doveadm: Error:
2019 Jul 13
0
Replication issue 2.3.7
Hello, Thanks for the info and workaround! I found and have the same problems after read your mail :-(. Am Samstag, 13. Juli 2019, 11:13:23 CEST schrieb Reio Remma via dovecot: > Hello! > > I noticed these in the logs since upgrading from 2.3.6. to 2.3.7: > > Jul 13 11:52:10 turin dovecot: doveadm: Error: > dsync-remote(reio at mrstuudio.ee)</1ekE7qbKV2gYwAAsNnMGQ>:
2017 Mar 01
1
Expunged message reappeared, giving a new UID
Dovecot 2.2.27 dsync-server(account_name): Warning: Maildir /usr/local/vhosts/mail/*******/info/Sent: Expunged message reappeared, giving a new UID (old uid=29787, file=*******) What triggers this replication for ever ?? Thank you George
2015 Sep 07
0
dsync replication errors
On 08 Sep 2015, at 01:16, Gedalya <gedalya at gedalya.net> wrote: > > On 02/17/2013 03:21 AM, Timo Sirainen wrote: >> Although there's still some mail >> duplication problem with maildir that doesn't log any errors about it. >> I'm not sure why that happens. > > While you're around, Timo :-) > > I've had such an issue recently with
2015 Jun 16
2
Dovecot 2.2.16: disappearing messages, mismatched summaries, duplicated messages, excessive full re-downloads
-------- Original Message -------- Subject: Re: Dovecot 2.2.16: disappearing messages, mismatched summaries, duplicated messages, excessive full re-downloads From: Benny Pedersen <me at junc.eu> To: dovecot at dovecot.org Date: Mon Jun 01 2015 16:47:48 GMT+0300 (Arabic Standard Time) > Alessio Cecchi skrev den 2015-06-01 15:29: >> Il 20/05/2015 10:44, David Gessel ha scritto:
2017 Feb 17
3
Replication Troubles
Hi Dovecot Users, I?ve configured dovecot dsync replication and I see troubles in the logs and get user complaints which I can?t explain. I found similar threads on this mailinglist, but I couldn?t find a solution anywhere. Does anybody have dsync running without problems on a high volume mailserver? I see the following logs, examples given: Feb 17 18:16:49 dovecot dovecot: imap(zoechi):
2015 Sep 08
2
dsync replication errors
Timo, I use mdbox and probably have similar issue, but in my case only shared mailboxes were affected. May 26 12:35:05 mx10 dovecot: doveadm: Error: dsync-remote(anna.harina at bgoperator.com): Error: Mailbox shared/l.davydjanc at bgoperator.com/russia: Save commit failed: Message has been copied too many times (50045 + 1) May 26 12:35:19 mx10 dovecot: dsync-local(anna.harina at
2014 Oct 24
0
Replication only sporadic
Hello dear Dovecot Gurus, I am setting up two servers with Dovecot replication as hot-standby servers for a small high availability cluster, switch-over through DNS-redirect. For testing purposes, both servers are generating a small test mail every few minutes and delivering to the local dovecot each. In my mail client, I added both servers through IMAP to watch how the replication is
2017 Feb 20
0
Replication Troubles
On 17 Feb 2017, at 21.37, Wolfgang Hennerbichler <wogri at wogri.com> wrote: > > Hi Dovecot Users, > > I?ve configured dovecot dsync replication and I see troubles in the logs and get user complaints which I can?t explain. I found similar threads on this mailinglist, but I couldn?t find a solution anywhere. Does anybody have dsync running without problems on a high volume
2014 Jan 13
1
Replication and public namespaces
Hi, I'm having some issues with replicating public namespaces. Everything seems to work fine for private namespaces, but while importing some huge mailboxes (many small mails) into a public namespace via imapsync, something goes wrong. The expected mail flow is: old-server (imapsync)> new-server1 (replication)> new-server2 But then, dovecot seems to run into race conditions when the
2006 Nov 03
1
mbox sync: Expunged message reappeared in mailbox
Starting at 05:32 this morning, one user on my dovecot server is receiving hundreds of copies of old email. This is a short excerpt from my dovecot.log showing the problem: > dovecot: Nov 03 05:27:02 Info: pop3-login: Login: > user=<howard at obfusca.ted>, method=PLAIN, rip=::ffff:81.44.31.210, > lip=::ffff:zz.zz.zz.zz, TLS > dovecot: Nov 03 05:27:02 Info: POP3(howard at
2013 Oct 28
2
Dovecot replication - I'm stuck
Hi, I've been following the wiki document at http://wiki2.dovecot.org/Replication, but I've become stuck. I'm running version 2.1.3 on NetBSD 5.2 (v2.2+ isn't available as a package yet, and compiling my own is well outside my wheelhouse). I have a couple of questions: The wiki page keeps referring to "vmail". Is this a just system user I need to create? Presumably
2016 Dec 06
0
Panic: file dsync-mailbox-tree-sync.c: line 576 (node_mailbox_trees_cmp): assertion failed: (ret != 0)
Hi, Here is a crash that's happening using the latest Dovecot version (v2.2.27 on CentOS7 x86_64): We are using replication. Judging by the second server's logs, I believe this has something to do with the fact that we're using the lazy_expunge plugin. Every night after midnight, we purge the lazy_expunge namespace by running a command similar to following one on the main server