Displaying 20 results from an estimated 2000 matches similar to: "TCP Cluster replication headache"
2014 Aug 26
0
TCP Cluster replication headache
Le 07/05/2014 17:38, Emmanuel Fust? a ?crit :
> Hello,
>
> After going crazy building a dovecot cluster, I finally see the light ;-))
> But some things are "strange" and could probably be fixed/enhanced.
>
> First :
> I follow the wiki doc, setting global doveadm_port.
> Things did not work, I've got:
>
> dovecot: doveadm(X1234567): Error: sync:
2014 May 13
1
imapc problem
hello,
I have some trouble when trying to migrate from another imap server to
dovecot with imapc/dsync/doveadm.
when running "doveadm -o imapc_user=foo -o imapc_password=bar backup -R
-u localuser imapc:" all is ok.
But when running "doveadm -o imapc_user=foo -o imapc_password=bar sync
-R -u localuser imapc:", all local mods are overwritten. For example
deleting a
2012 Aug 31
1
Possible mbox corruption if mail is saved with wrong Content-Length header (2.1.6)
One of our users likes to delete attachments from his mails. He is using
roundcube and we installed a plugin for that.
He reports that from time to time one of his mails gets corrupted (cut
off in the middle).
I could verify there is something wrong in the logs:
imap(x1234567): Error: Cached message size larger than expected (6796 > 2844)
imap(x1234567): Error: Corrupted index cache file
2018 Jun 16
0
TCP replication: high connection rate and looping in incomplete state
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
2017 Jan 26
0
dsync dovecot / Failed connection refused
Hi,
Jan 26 17:21:40 doveadm(user7 at domain.ltd): Fatal: connect(ip_server_target:4711) failed: Connection refused
Jan 26 17:23:59 doveadm(user3 at domain.ltd): Fatal: connect(ip_server_target:4711) failed: Connection refused
Jan 26 17:24:44 doveadm(user5 at domain.ltd): Fatal: connect(ip_server_target:4711) failed: Connection refused
Jan 26 17:24:44 doveadm(user4 at domain.ltd): Fatal:
2017 Jan 24
0
dsync dovecot / Failed connection refused
Hello,
I might be wrong, but the port which will be used for the replicator
port is the value of 'doveadm_port' which in your case is 4711.
Mike;
On 01/23/2017 05:58 PM, Thierry wrote:
> Dear all,
>
> I am using VMWare and I have cloned my emails server.
> Now I do have two identicals servers, both running the same version of dovecot (2.2.13) and imap.
> Let's call
2017 Jan 24
3
dsync dovecot / Failed connection refused
Hi Mike,
Is the value of the 'doveadm_port' if I am choosing: mail_replica =
tcp:server1.domain.ltd no ?
I might be wrong too ;)
Thx
Le mardi 24 janvier 2017 ? 11:41:28, vous ?criviez :
> Hello,
> I might be wrong, but the port which will be used for the replicator
> port is the value of 'doveadm_port' which in your case is 4711.
> Mike;
> On 01/23/2017
2017 Jan 23
2
dsync dovecot / Failed connection refused
Dear all,
I am using VMWare and I have cloned my emails server.
Now I do have two identicals servers, both running the same version of dovecot (2.2.13) and imap.
Let's call them: server1.domain.ltd and server2.domain.ltd.
I would like to sync both server using dsync.
Dovecot is working well except concerning the sync.
dsync config server1.domain.ltd
# Enable the replication plugin
2015 Dec 04
0
Trouble setting replication over TCP
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
2017 Aug 03
0
Replication and public folders with private (seen) flags
We started using Dovecot replication between two nodes and noticed that
our configured private flags (INDEXPVT) in public/shared mailboxes are
not replicated. We are only replicating INBOX namespace, as we dont want
to replicate content of shared mailboxes for every user again.
Is there a way to replicate the INDEXPVT or is that not (yet) implemented?
Dovecot versions:
# 2.2.31 (65cde28):
2013 Oct 30
1
Replication on v2.2.6 - I'm stuck (again)
Hi,
I'm trying to get Dovecot replication working between two servers. I
didn't have much luck on v2.1.3, so after receiving advice from the list I
have upgraded to v2.2.6.
I now get the error:
Oct 30 11:50:16 server1 dovecot: doveadm(mark): Error: user mark: Auth PASS
lookup failed
Oct 30 11:50:16 server2 dovecot: doveadm(mark): Error: sync:
/var/run/dovecot/auth-userdb: passdb lookup
2016 Sep 01
2
Dsync config help
I was able to workaround the ?Error: sync: /var/run/dovecot/auth-userdb: Configured passdbs don?t support credentials lookups (to see if user is proxied, because doveadm_port is set)? problem:?
=> I simply disabled ?doveadm_port? and added the port number at the end of the remote URL in ?mail_replica?
Replication seems to work although I have regular errors (idk if they are related to each
2014 Jan 30
1
Is replication broken?
Hi,
Apologies for this being my 248th post about replication...
The current error I'm getting is:
Jan 30 12:10:54 Server1 dovecot: dsync-local(MailUser1): Error: dsync(
Server2.test.com): read() failed: read((fd)) failed: Connection reset by
peer
Subsequent errors are:
Jan 30 12:15:47 Server1 dovecot: dsync-local(MailUser1): Error: read(
Server2.test.com) failed: EOF
The above error is
2015 Jan 16
0
dsync SSL fails since 2.2.15
Hello list,
dovecot ran rock-solid on OSX Mavericks for about 1 year replicating my mail between 2 servers via dsync with SSL as that is well described here: http://wiki2.dovecot.org/Replication
After upgrading to 2.2.15, dsync gets stuck with the Error: "Received invalid SSL certificate" even though neither any of the dovecot configs nor the certs, keys or the CA have changed!
When I
2018 May 08
0
replicator: User listing returned failure
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:
2019 Jan 04
1
Feature request: client bind address for replication
Hi
would it be possible to consider a new parameter for replication:
doveadm_local_ip which allows the source ip address to be set when
connection to a remote dovecot for replication?
It could be useful when the network interface has multiple ips and a
specific one is used for mail services. See attached proposal. I tested
against 2.2.36 only. It applies correctly against 2.3.4 with a warning,.
2020 Nov 18
0
Dovecot Replication Errors (only) when using tcps: as the mail_replica Protocol
Hello,
I have two mail servers and am also experiencing sporadic replication
errors over tcps, similar to Reuben. Each server is running Dovecot
2.3.11.3 (502c39af9) on Debian 10.6.
*Log entries from MX1*
Nov 18 00:39:26 mx1 dovecot:
dsync-local(user at example.com)<Ow3zAjWxtF+TDgAAPHKnuQ>: Error:
dsync(mx2.example.com): I/O has stalled, no activity for 600 seconds
(last sent=mailbox,
2018 Dec 10
0
Replication fatal error
This has been fixed in a later version of Dovecot, so your best course of action is to upgrade to some more recent version. I'd recommend 2.2.36.
Aki
> On 10 December 2018 at 18:28 admin via dovecot <dovecot at dovecot.org> wrote:
>
>
> Dear suscribers.
>
> I just dont understand this error. Don't know where to look first. If
> someone have already meet
2017 Feb 06
0
Dovecot dsync 'ssl_client_ca'
Dear Thierry,
- Have you checked that port 12345 as specified below is open/forwarded
and actually /used/ by dovecot (e.g., use "netstat -tulpn|grep dovecot")?
- Did you retrace your steps and have you verified that synchronisation
works with ssl disabled?
- Did you verify your certificate files (e.g., "openssl verify -verbose
-CAfile /etc/ssl/certs/GandiCA2.pem
2013 Nov 09
1
Dovecot replication not redirecting if server is down
Hi everyone,
I'm running a test environment with a proxy in front of working
replication between two backends but redirecting in case of a
backend failure is not working.
Nov 09 21:03:59 imap-login: Error: proxy(mail at example.net):
connect(10.5.29.211, 143) failed: Connection refused (after 0 secs,
local=10.5.29.201:38333)
I appreciate any advice.
Regards
Patrick
Proxy:
# 2.2.7: