On Wed, Aug 01, 2007 at 08:42:42PM +0200, Gerald Holl wrote:
> Robert Felber wrote:
> > Assuming that you are using 0.1.14:
> >
> > - Update to 0.1.14.5 (or even 0.1.14.6, both should be ok)
> > - check whether policyd-weight's $MAX_PROC reflect postfix' smtpd MAX_PROC
> >
> >
> > Probably the notification about exceeded policyd-weight MAX_PROCs was
> > logrotated out. This notification is only announced once.
>
> Hello,
>
> I have updated policyd-weight to 0.1.14.6 and I still see the error in
> the logs:
> Aug 1 17:27:37 jimbo postfix/smtpd[2100]: warning: timeout on
> 127.0.0.1:12525 while reading input attribute name
> Aug 1 17:27:37 jimbo postfix/smtpd[2100]: warning: problem talking to
> server 127.0.0.1:12525: Connection timed out
Thanks, Paul B. Henson has sent me privately a system state overview
at such timeouts.
It appears, that in cases where 1 child has to handle too much
SMTPD connections those problems occur.
Scenario:
*** Jul 31 23:36:43 adler postfix/smtpd[27423]: warning: problem talking to
server 127.0.0.1:12525: Connection timed out:
smtpd 27423 postfix 15u IPv4 448326585 TCP
localhost:53355->localhost:12525 (ESTABLISHED)
policyd-w 10831 polw 24u IPv4 448326503 TCP
localhost:12525->localhost:53350 (ESTABLISHED)
policyd-w 10831 polw 25u IPv4 448323681 TCP
localhost:12525->localhost:53205 (ESTABLISHED)
policyd-w 10831 polw 26u IPv4 448325530 TCP
localhost:12525->localhost:53286 (ESTABLISHED)
policyd-w 10831 polw 27u IPv4 448302867 TCP
localhost:12525->localhost:55232 (ESTABLISHED)
policyd-w 10831 polw 28u IPv4 448306964 TCP
localhost:12525->localhost:55440 (ESTABLISHED)
policyd-w 10831 polw 29u IPv4 448315886 TCP
localhost:12525->localhost:55400 (ESTABLISHED)
policyd-w 10831 polw 30u IPv4 448316166 TCP
localhost:12525->localhost:55420 (ESTABLISHED)
policyd-w 10831 polw 31u IPv4 448326586 TCP
localhost:12525->localhost:53355 (ESTABLISHED)
I.e: 10831 had 8 SMTPD "clients". If 1 of those is served, all others must wait.
So - the 8th one has to wait a long time - but not always, depending on whether
all other smtpd are active and how long the requests take.
Actually it shouldn't happen that the SMTPD policy requests are spread
unbalanced over the policyd-weight children (others did only have two
or no connections).
Your workaround would be to implement policyd-weight via
master.cf + spawn until I have a fix.
--
Robert Felber (PGP: 896CF30B)
Munich, Germany
____________________________________________________________
Policyd-weight Mailinglist - http://www.policyd-weight.org/
