similar to: replication full documentation

Hello. If running dovadm replicator status, i get something like the following. root at mail2:~# doveadm replicator status Queued 'sync' requests??????? 0 Queued 'high' requests??????? 0 Queued 'low' requests???????? 0 Queued 'failed' requests????? 0 Queued 'full resync' requests 4 Waiting 'failed' requests???? 0 Total number of known users? 1000

We're running 2.2.13 on two servers with replication. Still trying to get my replication tweaked correctly and I?m noticing a bunch of these errors for the same users over and over again: dsync-server(user at host.com): Error: write(/var/run/dovecot/replicator-doveadm) failed: Resource temporarily unavailable The 5-7 that I see all have quite a number of individual mailboxes (20+), I?m

Trying to get my new storage server synced up using dsync replication with SSH. Followed the wiki and everything works great for the initial sync, for about 4 hours, then I get some errors and it stops replicating: dsync-local(user at host.com): Warning: Failed to do incremental sync for mailbox INBOX, retry with a full sync dsync-local(user at host.com): Error: Remote command returned error 75:

Dear Dovecot-Admins, I've set up a pair of Dovecot Servers, please find config of server one attached. They are configured to replicate changes over a tcp connection using port 12345, set up as described in http://wiki2.dovecot.org/Replication article page. Adding the user postboxes to replication using "doveadm replicator add '*' " syncs the mailboxes as expected.

Hello, I am using Dovecot version 2.2.10. I am quite familiar with ssh replication and I managed to set it up correctly. The only problem I see is that when i run the command: doveadm replicator status I get a wrong "Total number of known users" which is a) is different between the two (2) replicated dovecot servers, i.e. in mail1 I get a total of 21 users and in mail2 I get a total of

Hi all, I am still struggling with this issue. I scraped my previous configuration and started from beginning. Thanks to Aki Tuomi and his suggestion I changed the users in my configurations from vmail --> root and that helped. Now I have a working replication but with some problems and strange behavior. Replication works only when I manually execute a command: "doveadm sync -A

Hello Alexey, > mx1:~# dovecot --version > 2.2.27 (c0f36b0) > > From dovecot.log: > May 07 19:27:41 auth-worker(34348): Warning: mysql: Query failed, retrying: Unknown column 'username' in 'field list' > May 07 19:27:41 auth-worker(34348): Debug: sql(*): SELECT username, domain FROM users > May 07 19:27:41 auth-worker(34348): Error: sql: Iterate query failed:

Where can I get more detailed information about the output of the 'doveadm replicator status' ? man doveadm-replicator isn't enough. For example, Total number of known users = 29409, but the server has only 17667 users. This is confusing. Look: # doveadm user '*' |wc -l 17667 # doveadm replicator status Queued 'sync' requests 0 Queued 'high' requests

Hello. I've tried to configure TCP replication to slave server. But I got some errors... mx1:~# dovecot --version 2.2.27 (c0f36b0) From dovecot.log: May 07 19:27:41 auth-worker(34348): Warning: mysql: Query failed, retrying: Unknown column 'username' in 'field list' May 07 19:27:41 auth-worker(34348): Debug: sql(*): SELECT username, domain FROM users May 07 19:27:41

Hi, I'm aware its an async process, but despite sending test messages and then waiting a few minutes, the stats are still unchanged : $ sudo doveadm replicator status???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? Queued 'sync' requests???????

Hi, I am trying to establish TCP(s)-based replication between two FreeBSD 11.1 machines, both running Dovecot 2.2.35 (via pkg) with 10 virtual users and 1.2GB maildir. I followed the Wiki description (https://wiki2.dovecot.org/Replication), just skipped the SSH part. My resulting configurations are attached below. Problem: After reloading both Dovecot instances, a few seconds later they start to

Hello, I have two installations of dovecot configured to replicate mailboxes between them. recently, i upgraded the operating system on one of them (mx2.example.com) and now i'm running one installation on version 2.2.27 (debian stretch) and another on version 2.3.4.1 (mx1.example.com debian buster). My setup includes 3 shared namespaces that point to the mailboxes of 3 accounts. these

> Thank you for the details. As per your suggestion, I have made the changes to dovecot.conf file. Still I don't see any replication is happening. Please see the dovecot.conf file. > > I do not see "/etc/dovecot/conf.d/12-replication.conf" in my servers. So I had put everything in the dovecot.conf file only. Please see the complete data in it below. The below data is in

Hi, FWIW this was also reported back in August[1] - experienced with 2.3.2.1 (not sure if earlier 2.3 releases were affected) and currently reproducible with latest 2.3.3 stable release. [1] https://www.dovecot.org/pipermail/dovecot/2018-August/112548.html Cheers, Tony On 2018-10-12 04:26, Pascal wrote: > Hello, > > I use dovecot replication and the sieve scripts are not

Gentlemen, I've setup 2 servers with dsync replication and hit a serious issue - some messages got duplicated thousands times in some shared mailboxes(~5). There is actually no reason to replicate anything from shared name space and I've tried to limit replication scope with just 'inbox' name space but it didn't help. dovecot version ||2.2.18 (2de3c7248922) errors in the

Nobody ? :-( On 3/30/20 5:26 PM, Olaf Hopp wrote: > Hello everybody, > since now I did no replication and spam is delivered into users folder "spambox" > Every night there is a cronjob which deletes spam older than 30 days via something like > ????"find .... -ctime +30 -delete" > Now I'm going to set up replication (two way) and I thought that > doing

Good day, everyone. I'm playing around with replication to create a backup host. I have hosts backend3 (192.168.100.112) and backend3-replica (192.168.100.113). backend3 acts as a mail-receiving host, backend3-replica is a backup for the case of failure. Both versions are 2.2.13 (form Debian Jessie repository). backend3 receives mail via LMTP-proxy. So far I've managed to setup

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

Hello everybody, since now I did no replication and spam is delivered into users folder "spambox" Every night there is a cronjob which deletes spam older than 30 days via something like "find .... -ctime +30 -delete" Now I'm going to set up replication (two way) and I thought that doing "rm" is not a good idea. So I modified the job to something like

Hi Aki, On 4/4/20 8:12 PM, Aki Tuomi wrote: > Can you provide doveconf -n and try turning on mail_debug=yes on both ends and try doveadm -Dv expunge .... mail_debug=yes is on on both ends and dovecot was restarted but anyway nothing is logged when I issue "doveadm -Dv expunge " In the shell where I issue the "expunge" I see the following: # /usr/bin/doveadm -Dv expunge