dovecot - Sep 2018 - Auth process sometimes stop responding after upgrade

In data venerd? 7 settembre 2018 09:39:23 CEST, Aki Tuomi ha
scritto:
> Do you see anything else in logs? 
> 
Just the usual proxy messages, like these:

Sep  6 14:45:41 imap-front13 dovecot: imap-login: 
proxy(alessandro at soldinicarrelli.it): disconnecting 5.169.233.224 
(Disconnected by server(0s idle, in=451, out=3556)): 
user=<alessandro at soldinicarrelli.it>, method=PLAIN, rip=5.169.233.224, 
lip=80.76.81.92, TLS, session=<uqVq2TJ1VbkFqeng>

Sep  6 14:45:51 imap-front13 dovecot: pop3-login: proxy(prg at pedrini.it): 
started proxying to 192.168.1.144:110: user=<prg at pedrini.it>,
method=DIGEST-
MD5, rip=5.34.191.10, lip=80.76.81.92, TLS, session=<WqhRRDN1qw0FIr8K>


The only suspect thing is this:

Sep  6 14:45:41 imap-front13 dovecot: director: doveadm: Host 192.168.1.142 
vhost count changed from 100 to 0
Sep  6 14:45:41 imap-front13 dovecot: director: doveadm: Host 192.168.1.143 
vhost count changed from 100 to 0
Sep  6 14:45:41 imap-front13 dovecot: director: doveadm: Host 192.168.1.219 
vhost count changed from 100 to 0

Nothing on the other system logs (e.g. kernel, daemon, syslog, messages ....).

-- 
*Simone Lazzaris*
*Qcom S.p.A.*

> On 7 Sep 2018, at 11.00, Simone Lazzaris <s.lazzaris at
interactive.eu> wrote:
> 
> 
> The only suspect thing is this:
> 
> Sep  6 14:45:41 imap-front13 dovecot: director: doveadm: Host 192.168.1.142
> vhost count changed from 100 to 0
> Sep  6 14:45:41 imap-front13 dovecot: director: doveadm: Host 192.168.1.143
> vhost count changed from 100 to 0
> Sep  6 14:45:41 imap-front13 dovecot: director: doveadm: Host 192.168.1.219
> vhost count changed from 100 to 0
> 
> Nothing on the other system logs (e.g. kernel, daemon, syslog, messages
....).
Any idea what is changing the vhost count on the backends? Do you have some
script running that possibly does change the vhost count for some triggering
event?

Sami

In data venerd? 7 settembre 2018 10:06:00 CEST, Sami Ketola ha
scritto:
> > On 7 Sep 2018, at 11.00, Simone Lazzaris <s.lazzaris at
interactive.eu>
> > wrote:
> > 
> > 
> > The only suspect thing is this:
> > 
> > Sep  6 14:45:41 imap-front13 dovecot: director: doveadm: Host
> > 192.168.1.142
> > vhost count changed from 100 to 0
> > Sep  6 14:45:41 imap-front13 dovecot: director: doveadm: Host
> > 192.168.1.143
> > vhost count changed from 100 to 0
> > Sep  6 14:45:41 imap-front13 dovecot: director: doveadm: Host
> > 192.168.1.219
> > vhost count changed from 100 to 0
> > 
> > Nothing on the other system logs (e.g. kernel, daemon, syslog,
messages
> > ....).
> Any idea what is changing the vhost count on the backends? Do you have some
> script running that possibly does change the vhost count for some
> triggering event?
> 
> Sami
Actually, I have a poolmon script running that should drop vhost count for
unresponsive
backends; the strage thing is, the backends are NOT unresponsive, they are
working as
ususal.


*Simone Lazzaris*
*Qcom S.p.A.*
simone.lazzaris at qcom.it[1] | www.qcom.it[2]
* LinkedIn[3]* | *Facebook[4]*
[5] 






--------
[1] mailto:simone.lazzaris at qcom.it
[2] https://www.qcom.it
[3] https://www.linkedin.com/company/qcom-spa
[4] http://www.facebook.com/qcomspa
[5] https://www.qcom.it/includes/email-banner.gif
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://dovecot.org/pipermail/dovecot/attachments/20180907/7a1fe30d/attachment.html>

In data venerd? 7 settembre 2018 10:06:00 CEST, Sami Ketola ha
scritto:
> > On 7 Sep 2018, at 11.00, Simone Lazzaris <s.lazzaris at
interactive.eu>
> > wrote:
> > 
> > 
> > The only suspect thing is this:
> > 
> > Sep  6 14:45:41 imap-front13 dovecot: director: doveadm: Host
> > 192.168.1.142
> > vhost count changed from 100 to 0
> > Sep  6 14:45:41 imap-front13 dovecot: director: doveadm: Host
> > 192.168.1.143
> > vhost count changed from 100 to 0
> > Sep  6 14:45:41 imap-front13 dovecot: director: doveadm: Host
> > 192.168.1.219
> > vhost count changed from 100 to 0
> > 
> > Nothing on the other system logs (e.g. kernel, daemon, syslog,
messages
> > ....).
> Any idea what is changing the vhost count on the backends? Do you have some
> script running that possibly does change the vhost count for some
> triggering event?
> 
> Sami
Actually, I have a poolmon script running that should drop vhost count for 
unresponsive backends; the strage thing is, the backends are NOT unresponsive, 
they are working as ususal.


To be honest, the configuration that keep failing (again, right now) has imap-
login not configured as I've told you. The configuration you saw was an 
attempt to overcame the problem, in which I've set pop3-login like this:

service pop3-login {
  executable = imap-login director
  service_count = 0
  vsz_limit = 128 M
}

But the machines that fails are like this:

service pop3-login {
  executable = pop3-login director
}

I've got 4 VM configured in the ring. The one with service_count=0 has (so 
far) never failed, the other 3 has failed multiple time (every few hours).

-- 
*Simone Lazzaris*
*Qcom S.p.A.*