Wietse Venema via Postfix-users:
> Stuart Armstrong via Postfix-users:
> > Thank you for your response. For clarity, this issue has been present
> > for several weeks now.
> >
> > > warning: SASL: Connect to Dovecot auth socket 'private/auth'
> > > failed: REASON FOR FAILURE HERE
> > I do not have this warning in the logs.
>
> All the debug logging is causing systemd to drop imprtant information.
>
> > For submission, maxproc is set to 550 to avoid the following type of
> > warning:
> > "warning: service "submission" (101) has reached its process limit
> > "100": new clients may experience noticeable delays."
>
> And:
>
> > > Dovecot:
> > > default_process_limit = 400
>
> Should that not match the Postfix process limit?
Ignore that.
However consider this dovecot.conf setting:
auth_worker_max_count = 60
According to the Dovecot author, auth workers are used for "blocking
lookups" (in an old example, passdb and userdb lookups from mysql).
That number may cause the timeouts on the Postfix side when Postfix
overwhelms the workers.
Of course, increasing that number just moves the bottleneck to the
next service, the mysql (or whatever) userdb or passdb backend.
Ultimately, it may be better to limit the nunber of conections at
the source, on the Kubernetes application side.
Wietse
https://dovecot.dovecot.narkive.com/ZYfAA9NU/number-of-auth-process
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
