v2.3.2 released

[Tom Sommer]

On 2018-06-29 16:00, Timo Sirainen wrote:
> On 29 Jun 2018, at 15.28, Tom Sommer <mail at tomsommer.dk> wrote:
>> 
>> On 2018-06-29 15:20, Timo Sirainen wrote:
>>> On 29 Jun 2018, at 15.05, Tom Sommer <mail at tomsommer.dk> wrote:
>>>> On 2018-06-29 14:51, Timo Sirainen wrote:
>>>>> v2.3.2 is mainly a bugfix release. It contains all the changes in
>>>>> v2.2.36, as well as a bunch of other fixes (mainly for v2.3-only
>>>>> bugs). Binary packages are already in https://repo.dovecot.org/
>>>> A simple "yum update" will result in a ton of these errors:
>>>> Jun 29 15:02:19 stats: Error: stats: Socket supports major version 
>>>> 2, but we support only 3 (mixed old and new binaries?)
>>>> Should the yum update process perhaps not restart the dovecot 
>>>> service?
>>> It sounds like you upgraded from v2.2.x to v2.3.2? The stats was
>>> completely changed.
>> 
>> From 2.3.1 to 2.3.2:
>> 
>> Installed:
>>  dovecot.x86_64 2:2.3.2-3            dovecot-mysql.x86_64 2:2.3.2-3
>> 
>> Updated:
>>  dovecot-pigeonhole.x86_64 2:2.3.2-3
>> 
>> Replaced:
>>  dovecot.x86_64 2:2.3.1-1            dovecot-mysql.x86_64 2:2.3.1-1
> 
> That's weird. Something appears to be connecting to the stats socket
> with old protocol version. What your doveconf -n?

service stats {
   chroot = empty
   client_limit = 0
   drop_priv_before_exec = no
   executable = stats
   extra_groups =
   group =
   idle_kill = 4294967295 secs
   privileged_group =
   process_limit = 1
   process_min_avail = 0
   protocol =
   service_count = 0
   type =
   unix_listener stats-reader {
     group =
     mode = 0600
     user =
   }
   unix_listener stats-writer {
     group = $default_internal_group
     mode = 0660
     user =
   }
   user = $default_internal_user
   vsz_limit = 18446744073709551615 B
}


This is the full error-log that happened after "yum update": 
https://pastebin.com/tUJaehdV

"Jun 29 15:02:20" is the "/etc/init.d/dovecot restart"

Maybe it was a one-time thing for only my setup, I don't know - Although 
I find it hard to understand how a stat-writer socket with an old 
version should be able to run in 2.3.1 with major version 2 for several 
months - and the same thing happened on all of my 22 
director-backend-servers.

Oh well.