On Thu, Jul 12, 2007 at 02:20:41PM +0200, Gerald Holl wrote:
> Robert Felber wrote:
> >This could happen if all policyd-weight processes are hogged up. Should be
> >logged with "MAX_PROX NN reached".
> >How many policyd-weight childs do you have at such moments?
> >Alternatively, what is your kernel setting for somaxconn? If it is 128
> >then you should increase it to 1024 or some higher value (this is a general
> >recommendation for any server). This isn't being logged by policyd-weight, as
> >this cannot be detected by polw.
>
> Hello Robert,
>
> The net.core.somaxconn is set to 128. I'll try to increase it to 1024 any
> report any changes.
>
> In thread [EMAIL PROTECTED] you recommend the 0.1.14.5 from
> policyd-weight.org. Is the timeout bug
> fixed in that version?
>
I have re-read
Jul 11 18:06:23 jimbo postfix/smtpd[31532]: warning: timeout on
127.0.0.1:12525 while reading input attribute name
Jul 11 18:06:23 jimbo postfix/smtpd[31532]: warning: problem talking to
server 127.0.0.1:12525: Connection timed out
Jul 11 18:06:23 jimbo postfix/smtpd[31532]: NOQUEUE: reject: RCPT from
unknown[61.142.35.204]: 451 4.3.5 Server configuration problem;
from=<[EMAIL PROTECTED]> to=<[EMAIL PROTECTED]> proto=ESMTP
helo=<204.35.142.61.broad.dg.gd.dynamic.163data.com.cn>
And the "connection timed out" suggests rather, that this is a out of socket
problem but it could also be, that there is another bug in 0.1.14 which
might result in timeouts.
The timeout-bug which I mentioned was introduced in 0.1.14.2 and corrected at
several places along 0.1.14.4 and 0.1.14.5
For further developing and bug-finding I rather require reports of the
latest beta release as there were many changes/fixes from 0.1.14 to 0.1.14.5
--
Robert Felber (PGP: 896CF30B)
Munich, Germany
____________________________________________________________
Policyd-weight Mailinglist - http://www.policyd-weight.org/
