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@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.*