Re: policy-2-postfix process connection pegged at 201

[Wietse Venema]

Len Conrad:
> 
> >>> freebsd 7.1 and 7.0
> >>> 
> >>> postfix mail_version = 2.4.10
> >>> 
> >>> When traffic triggers postfix to log:
> >>> 
> >>> postfix/smtpd[4]: warning: problem talking to server 127.0.0.1:10041: 
> >>> Operation timed out
> >>> 
> >>> ... I see that the process qty of policy-to-postfix pegs at 201.  
> >>> 
> >>> As long as that qty stays below 200, there are no postfix timeouts.
> >>> 
> >>> I can't find any param in the policy process/docs or postfix/docs that is 
> >>> 200.
> >>> 
> >>> Where is this 200?
> >>
> >>Most likely default_process_limit, put a "0" in the process limit column
> >>of the master.cf entry for the policy service.
> >
> >thanks, but none of the 3 policy services, all listen on TCP, talk about 
> >configuring a policy line in master.cf.  They aren't spawned by postfix, but 
> >started with init scripts and permanently resident.  
> >
> >What would a policy line look like in master.cf?
> >
> >Len
> 
> Is there any other way to increase this 200 limit?

If the policy daemon is not configured in master.cf, then that is
not a Postfix question.

Wietse

Re: policy-2-postfix process connection pegged at 201

[Len Conrad]

>>> freebsd 7.1 and 7.0
>>> 
>>> postfix mail_version = 2.4.10
>>> 
>>> When traffic triggers postfix to log:
>>> 
>>> postfix/smtpd[4]: warning: problem talking to server 127.0.0.1:10041: 
>>> Operation timed out
>>> 
>>> ... I see that the process qty of policy-to-postfix pegs at 201.  
>>> 
>>> As long as that qty stays below 200, there are no postfix timeouts.
>>> 
>>> I can't find any param in the policy process/docs or postfix/docs that is 
>>> 200.
>>> 
>>> Where is this 200?
>>
>>Most likely default_process_limit, put a "0" in the process limit column
>>of the master.cf entry for the policy service.
>
>thanks, but none of the 3 policy services, all listen on TCP, talk about 
>configuring a policy line in master.cf.  They aren't spawned by postfix, but 
>started with init scripts and permanently resident.  
>
>What would a policy line look like in master.cf?
>
>Len

Is there any other way to increase this 200 limit?

Len

Re: policy-2-postfix process connection pegged at 201

[Wietse Venema]

Len Conrad:
> >> As long as that qty stays below 200, there are no postfix timeouts.
> >> 
> >> I can't find any param in the policy process/docs or postfix/docs that is 
> >> 200.
> >> 
> >> Where is this 200?
> >
> >Most likely default_process_limit, put a "0" in the process limit column
> >of the master.cf entry for the policy service.
> 
> thanks, but none of the 3 policy services, all listen on TCP, talk
> about configuring a policy line in master.cf.  They aren't spawned
> by postfix, but started with init scripts and permanently resident.
> 
> What would a policy line look like in master.cf?

If the policy server's TCP port number exists in master.cf, then
the process limit field must be 0.

Wietse

Re: policy-2-postfix process connection pegged at 201

[Len Conrad]

>
>> freebsd 7.1 and 7.0
>> 
>> postfix mail_version = 2.4.10
>> 
>> When traffic triggers postfix to log:
>> 
>> postfix/smtpd[4]: warning: problem talking to server 127.0.0.1:10041: 
>> Operation timed out
>> 
>> ... I see that the process qty of policy-to-postfix pegs at 201.  
>> 
>> As long as that qty stays below 200, there are no postfix timeouts.
>> 
>> I can't find any param in the policy process/docs or postfix/docs that is 
>> 200.
>> 
>> Where is this 200?
>
>Most likely default_process_limit, put a "0" in the process limit column
>of the master.cf entry for the policy service.

thanks, but none of the 3 policy services, all listen on TCP, talk about 
configuring a policy line in master.cf.  They aren't spawned by postfix, but 
started with init scripts and permanently resident.  

What would a policy line look like in master.cf?

Len



>-- 
>Viktor.
>
>Disclaimer: off-list followups get on-list replies or get ignored.
>Please do not ignore the "Reply-To" header.
>
>To unsubscribe from the postfix-users list, visit
>http://www.postfix.org/lists.html or click the link below:
>
>
>If my response solves your problem, the best way to thank me is to not
>send an "it worked, thanks" follow-up. If you must respond, please put
>"It worked, thanks" in the "Subject" so I can delete these quickly.

__
IMGate OpenSource Mail Firewall www.IMGate.net

Re: policy-2-postfix process connection pegged at 201

[Victor Duchovni]

On Sat, Apr 25, 2009 at 02:03:43PM -0500, Len Conrad wrote:

> freebsd 7.1 and 7.0
> 
> postfix mail_version = 2.4.10
> 
> When traffic triggers postfix to log:
> 
> postfix/smtpd[4]: warning: problem talking to server 127.0.0.1:10041: 
> Operation timed out
> 
> ... I see that the process qty of policy-to-postfix pegs at 201.  
> 
> As long as that qty stays below 200, there are no postfix timeouts.
> 
> I can't find any param in the policy process/docs or postfix/docs that is 200.
> 
> Where is this 200?

Most likely default_process_limit, put a "0" in the process limit column
of the master.cf entry for the policy service.

-- 
Viktor.

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.

To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:


If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.

policy-2-postfix process connection pegged at 201

[Len Conrad]

freebsd 7.1 and 7.0

postfix mail_version = 2.4.10

When traffic triggers postfix to log:

postfix/smtpd[4]: warning: problem talking to server 127.0.0.1:10041: 
Operation timed out

... I see that the process qty of policy-to-postfix pegs at 201.  

As long as that qty stays below 200, there are no postfix timeouts.

I can't find any param in the policy process/docs or postfix/docs that is 200.

Where is this 200?

Len