dovecot - Nov 2019 - dovecot -2.2.24 on Fedora 31

On Mon, 11 Nov 2019 17:30:37 +0200 (EET) Aki Tuomi via dovecot wrote:

  [ ... ]
> Is there some reason you want to use ancient dovecot? You should use 2.2.36
at least.
I got dovecot-2.2.36.4 compiled but at start the log shows

dovecot[342614]: master: Dovecot v2.2.36.4 (baf9232c1) starting up for imap
dovecot[342617]: ssl-params: Generating SSL parameters
dovecot[342614]: master: Error: service(auth): command startup failed,
throttling for 2 secs
dovecot[342617]: auth: Fatal: master: service(auth): child 342623 killed with
signal 11 (core dumped)
dovecot[342614]: master: Error: service(auth): command startup failed,
throttling for 4 secs

The configuration files are from dovecot-2.2.24 whre they worked perfect.

What to do to get it working?
conf.d
PS: I can provide dovecot.conf and conf.d/10-auth.conf if necessary.


--Frank

On Mon, 11 Nov 2019 23:47:27 +0100 Frank Elsner via dovecot wrote:

  [ ... ]
> I got dovecot-2.2.36.4 compiled but at start the log shows
> 
> dovecot[342614]: master: Dovecot v2.2.36.4 (baf9232c1) starting up for imap
> dovecot[342617]: ssl-params: Generating SSL parameters
> dovecot[342614]: master: Error: service(auth): command startup failed,
throttling for 2 secs
> dovecot[342617]: auth: Fatal: master: service(auth): child 342623 killed
with signal 11 (core dumped)
> dovecot[342614]: master: Error: service(auth): command startup failed,
throttling for 4 secs
> 
> The configuration files are from dovecot-2.2.24 whre they worked perfect.
I narrowed the probelem down to the warnings

Warning: service auth { client_limit=128 } is lower than required under max.
load (768)
Warning: service anvil { client_limit=256 } is lower than required under max.
load (643)

Where comes max. load from?


--Frank

On Tue, 12 Nov 2019 00:17:28 +0100 Frank Elsner via dovecot
wrote:
> On Mon, 11 Nov 2019 23:47:27 +0100 Frank Elsner via dovecot wrote:
  [ ... ]
> I narrowed the probelem down to the warnings
> 
> Warning: service auth { client_limit=128 } is lower than required under
max. load (768)
> Warning: service anvil { client_limit=256 } is lower than required under
max. load (643)
These messages disappear after changes in the auth and anvil config but I ran
into the following problem:

dovecot[355234]: master: Dovecot v2.2.36.4 (baf9232c1) starting up for imap
dovecot[355234]: master: Error: service(auth): command startup failed,
throttling for 2 secs
dovecot[355237]: auth: Fatal: master: service(auth): child 355242 killed with
signal 11 (core dumped)
dovecot[355234]: master: Error: service(auth): command startup failed,
throttling for 4 secs
dovecot[355237]: auth: Fatal: master: service(auth): child 355256 killed with
signal 11 (core dumped)
dovecot[355234]: master: Error: service(auth): command startup failed,
throttling for 8 secs
dovecot[355237]: auth: Fatal: master: service(auth): child 355271 killed with
signal 11 (core dumped)
dovecot[355234]: master: Error: service(auth): command startup failed,
throttling for 16 secs
dovecot[355237]: auth: Fatal: master: service(auth): child 355285 killed with
signal 11 (core dumped)
dovecot[355234]: master: Warning: Killed with signal 15 (by pid=1 uid=0
code=kill)
dovecot[355237]: imap-login: Warning: Killed with signal 15 (by pid=1 uid=0
code=kill)
dovecot[355237]: anvil: Warning: Killed with signal 15 (by pid=1 uid=0
code=kill)
dovecot[355237]: config: Warning: Killed with signal 15 (by pid=1 uid=0
code=kill)
dovecot[355237]: log: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill)

I guess the solution is simple but I can't find it :-(


--Frank