Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Victor Duchovni (Victor.DuchovniMorganStanley.com)
Date: Wed Oct 31 2007 - 10:02:10 CDT
On Wed, Oct 31, 2007 at 07:49:23AM -0700, Andreas Grimm wrote:
> Hello Victor,
> it's not the greylist server that slows down the whole thing. Under stress:
> #> time netcat 127.0.0.1 2525 < requesttest
> real 0m0.012s
> user 0m0.004s
> sys 0m0.000s
> The server still answers stalled. I also tried now to raise the process limit for smtpd from 1500 to 2000. Some seconds later anvil has gone away:
> Oct 31 15:30:13 mx-01 postfix/smtpd: warning: problem talking to server private/anvil: Resource temporarily unavailable
> Oct 31 15:29:49 mx-01 postfix/smtpd: warning: connect to private/anvil: Resource temporarily unavailable
What did anvil(8) and master(8) log for this event? Can you strace
anvil to see what is happening? What are the resource limits of the
processes on a standard kernel (attach to the anvil(8) or master(8)
daemon with gdb and print the value of the "event_fdlimit" variable,
your Postfix binaries need to be not stripped).
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.