On Wed, Jul 11, 2007 at 06:52:58PM -0700, Paul B. Henson wrote:
There are two different errors: Connection timed out, which seems to be
an error at the actual TCP level where the connection is never established,
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.
If I understand correctly, this parameter would only apply for a policy
server named policy which is being spawned out of master.cf, not the case
for policyd-weight. I don't think this parameter would have any effect on a
policyd-weight configuration.
I did find a different parameter:
smtpd_policy_service_timeout (default: 100s)
The time limit for connecting to, writing to or receiving from a
delegated SMTPD policy server.
Possibly increasing this might reduce the number of timeouts when the
server doesn't respond quickly enough, but 100 seconds seems like an
awfully long time. Ideally policyd-weight shouldn't take nearly that long
to do its job.
I wouldn't really increase this. 100s are quite a long time and anything
taking longer than that should be considered a bug in policyd-weight.
--
Robert Felber (PGP: 896CF30B)
Munich, Germany
Policyd-weight Mailinglist - http://www.policyd-weight.org/
