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?
cheers,
Gerald
____________________________________________________________
Policyd-weight Mailinglist - http://www.policyd-weight.org/
