similar to: Replication Upgrade 2.2 -> 2.3 Question

Do both replication nodes need to be updated at the same time? Or can a 2.2(.36.4) node replicate with a 2.3(.10.1)? Ralf -- Ralf Becker EGroupware GmbH [www.egroupware.org] Handelsregister HRB Kaiserslautern 3587 Gesch?ftsf?hrer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 631 31657-0 -------------- next part -------------- A non-text attachment was

Running 2.2.15 on FreeBSD 10.0. Forcing replication with: doveadm replicator replicate -f user at host.com on one user that I've seen some syslogs show up to see what's going on. Other users are fine. When I run the above command on the one user it produces a core dump. See below for syslog output and full backtrace: syslog output: Oct 26 22:44:09 d3cstorage dovecot: dsync-server(user

Hi, I have a setup with 3 Dovecot Director v2.2.36 and director_consistent_hashing = yes ;-) Now I would like to upgrade to 2.3.7, first only Director and after also Backend. Can works fine a ring of director with mixed 2.2 and 2.3 version? Mi idea is to setup a new Director server with 2.3, stop one server with 2.2 and insert the new 2.3 in the current ring to check if works fine. If all

On 18 Jul 2019, at 11.44, Alessio Cecchi via dovecot <dovecot at dovecot.org> wrote: > > Hi, > > I have a setup with 3 Dovecot Director v2.2.36 and director_consistent_hashing = yes ;-) > > Now I would like to upgrade to 2.3.7, first only Director and after also Backend. > > Can works fine a ring of director with mixed 2.2 and 2.3 version? > > Mi idea is to

Il 18/07/19 21:42, Timo Sirainen ha scritto: > On 18 Jul 2019, at 11.44, Alessio Cecchi via dovecot > <dovecot at dovecot.org <mailto:dovecot at dovecot.org>> wrote: >> >> Hi, >> >> I have a setup with 3 Dovecot Director v2.2.36 and >> director_consistent_hashing = yes ;-) >> >> Now I would like to upgrade to 2.3.7, first only Director

Hi Timo, here you can see two images with the load average and CPU usage with Dovecot 2.2 (Centos 6) and 2.3 (Centos 7) on the same hardware and same configuration: https://imgur.com/a/1hsItlc Load average increment is relevant but CPU usage is similar. Il 22/07/19 18:49, Timo Sirainen ha scritto: > On 22 Jul 2019, at 17.45, Alessio Cecchi <alessio at skye.it > <mailto:alessio

Trying to figure out Proxying with LMTP to a few back end storage servers for quota checking before accepting email delivery on the front end nodes. If I connect to the back end server directly via telnet, everything works great. If I use a front-end server to proxy to the back end server, I don't get the same result. Running 2.2.4 on both front and back end servers. Any help would be

> On 22 June 2018 at 10:18 tai74 at vfemail.net wrote: > > > > hi sorry if question was asked already. Was reading > https://wiki2.dovecot.org/Upgrading/2.3 > > first I'm confused on diffie hellman parameters file. I never set up > ssl-parameters.dat before (should i have? do I have one that was > automatically made for me by dovecot?) > > Do I need

Hello, i was using dovecot version 2.2 on debian server. After upgrade to debian version 2.3 i have problems. After some time imap doesn't work. There are lot of messages in log 2019-05-21T10:27:49.186373+02:00 hermes dovecot: imap-login: Error: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable - http://wiki2.dovecot.org/SocketUnavailable (client-pid=24810,

On 16 May 2015, at 09:39, Xin Li <delphij at delphij.net> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Hi, > > On 5/15/15 10:58, Xin Li wrote: >> Hi, >> >> I have seen the following assertion fails on my own mail server >> (indexer-worker): >> >> Panic: file charset-iconv.c: line 132 (charset_to_utf8):

Running 2.2.15 on FreeBSD 10.0 with two back end storage boxes using TCP to sync. Seeing a couple of users that always seem to be throwing these kind of errors in the logs: dovecot: dsync-server(user at host.com): Error: write(/var/run/dovecot/replicator-doveadm) failed: Resource temporarily unavailable Just wondering what's the proper course of action to fix it? Thanks.

On 15 May 2018, at 12.06, Timo Sirainen <tss at iki.fi> wrote: > > If you look at .176's error log, do you see an error about "director_consistent_hashing settings differ between directors"? Have you set director_consistent_hashing=yes in the old directors? That is needed now, because the old non-consistent-hashing method is obsoleted. Unfortunately there's no easy

On 22 Jul 2019, at 17.45, Alessio Cecchi <alessio at skye.it> wrote: > > one server of the ring is now running Dovecot 2.3.7 and works fine with the others Dovecot 2.2 since 3 days. > I notice only that the load avarage of this CentOS 7 server is higher compared with CentOS 6 and Dovecot 2.2, but I don't know if is related to the new operating system or Dovecot (hardware is the

> On 6 May 2018, at 8.46, Niels Kobsch?tzki <niels at kobschaetzki.net> wrote: > > Hi, > > I have a setup with several dovecot-servers (2.2.35) and I use dovecot > proxy. I upgraded one server to 2.3.1 and got the configs fixed so far > that it started again. But when I tried to add it into the proxying > again with "doveadm director add" I see the

Hi. I use custom script: > require [ "vnd.dovecot.pipe", "variables" ]; > > if address :is :all "from" "snip at snap" > { > ? pipe "sieve_to_owncloud"; > } sieve_to_owncloud: > DATE=`date +%Y-%m-%d_%H-%M-%S` > PYTHONIOENCODING=utf8 python /opt/sieve-pipe/python-imap-to-owncloud.py \ > ? --owncloud-host

We recently upgraded from dovecot 2.2 to 2.3.7.1-1 Not many, but some users are experiencing difficulties. The dovecot directors log: Aug 21 14:28:49 director01 dovecot: pop3-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=redacted, lip=10.0.0.120, TLS handshaking: SSL_accept() failed: error:1408A0C1:SSL routines:ssl3_get_client_hello:no shared cipher,

Op 3/28/2018 om 6:01 AM schreef Konstantin Shalygin: > > Hi. > > > I use custom script: > >> require [ "vnd.dovecot.pipe", "variables" ]; >> >> if address :is :all "from" "snip at snap" >> { >> ? pipe "sieve_to_owncloud"; >> } > > > sieve_to_owncloud: > >> DATE=`date

On 21/8/2019 16:12, Kristijan Savic - ratiokontakt GmbH via dovecot wrote: > We recently upgraded from dovecot 2.2 to 2.3.7.1-1 > > Not many, but some users are experiencing difficulties. The dovecot directors > log: > > Aug 21 14:28:49 director01 dovecot: pop3-login: Disconnected (no auth attempts > in 0 secs): user=<>, rip=redacted, lip=10.0.0.120, TLS handshaking:

hi sorry if question was asked already. Was reading https://wiki2.dovecot.org/Upgrading/2.3 first I'm confused on diffie hellman parameters file. I never set up ssl-parameters.dat before (should i have? do I have one that was automatically made for me by dovecot?) Do I need to make a fresh dh.pem? The upgrade doc tells how to convert ssl-parameters.dat but how to make a new one? other

Out of the blue my proxy installations started showing this: dovecot: login: tried to change state 2 -> 2 (if you can't login at all, see src/lib/fdpass.c) Nobody can login. Running 1.0.0 on the proxy and 1.0.2 on my storage boxes. Anybody have any insights? -c