Re: Postfix 2.2.5 on latest Solaris 9 x86


Postfix 2.2.5 on latest Solaris 9 x86
\ Shaun Mccullagh (23 Sep 2007)
. \ (Wietse Venema) (23 Sep 2007)
. . \ Shaun Mccullagh (23 Sep 2007)
. . . \ (Wietse Venema) (23 Sep 2007)
. . . . \ Shaun Mccullagh (24 Sep 2007)
. . . . . \ (Wietse Venema) (24 Sep 2007)
. \ Shaun Mccullagh (23 Sep 2007)

5 msg	Postfix Relay, and Pop-before-smtp
12 msg	Newb Question
13 msg	Best defense against this?
1 msg	undelivered mail problem - SOLVED
4 msg	Legal local-part
3 msg	virtual_alias_domains with mysql: 'User unknown...
6 msg	Submission port (587): howto to use differente ...
5 msg	When does smtpd_reject_unlisted_recipient kick in?
4 msg	Postfix 'falling back' on sasldb? I don't want ...
3 msg	Nested access maps (I think ;))
3 msg	Suppression of encoding bad header function in ...
4 msg	RE: Catchall ??
3 msg	problem with .forward files + forwarding loops
5 msg	Postfix Strange Behaviours
7 msg	Content filter question, based upon auth'ed or not
28 msg	Mail stuck in active queue for loooong time
11 msg	How to stop a user from changing the 'From:' he...
10 msg	[Semi-OT] blocked port 465, anywhere?
7 msg	chroot problems on Nexenta (OpenSolaris)

Subject:	Re: Postfix 2.2.5 on latest Solaris 9 x86
Group:	Postfix-users
From:	(Wietse Venema)
Date:	24 Sep 2007

Shaun Mccullagh:
> Hi Wietse,
>
> I'm monitoring the number of connections in FIN_WAIT_2 state. So far the
> maximum has been less than 50.
>
> I noticed this error again this afternoon
>
> Sep 24 15:43:17 green postfix/proxymap[3053]: fatal: accept connection:
> Too many open files

Prior to Postfix 2.4, each Postfix process can handle up to FD_SETSIZE
open files/sockets/etc.

On my several-year old copy of Solaris 9 for Intel, FD_SETSIZE is
defined as 65535 for 64-bit machines, otherwise it is defined as
1024.

Even with 1024, I still don't see how proxymap could run out of
open files, unless the master.cf proxymap process limit is much,
much, smaller than the master.cf smtpd process limit.

If the system were out of files/sockets/etc. then I could expect
Solaris to report an ENFILE error (Too many open files in system)
instead of EMFILE (Too many open files).

Wietse