YAWS with SSL Connections Problem

[Chih - Wei Yu [ MTN - Innovation Centre ]]

Hi all,

We're running YAWS (1.75)(Erlang 12B-5) with SSL and there was a stage where we ran out of file descriptors. Now what seems to be is that ssl_esock process is using up all the descriptors.

PID/FILES = 21651 /     1638
$ /usr/ucb/ps -auxww | grep 21651
user 12992  0.0  0.0 1352 1152 pts/1    S 10:59:23  0:00 grep 21651
user 21651  0.0  0.12024019184 ?        S   Sep 09 8235:25 /usr/local/erlang/R12B-5/lib/erlang/lib/ssl-3.10/priv/bin/ssl_esock

$ netstat -an | grep IDLE |more
      *.*                  *.*                0      0 49152      0 IDLE
      *.*                  *.*                0      0 49152      0 IDLE
      *.*                  *.*                0      0 49152      0 IDLE
      *.*                  *.*                0      0 49152      0 IDLE
$  netstat -an | grep IDLE | wc -l
    1630

Another observation was that there were plenty of IDLE 'connections' when doing a netstat. Current max file descriptors is set to 4096 and thus it would eventually run out and the YAWS application would stop as it does not have descriptors to use. Two questions I would like to ask is

-          Under which circumstances does this happen and cause it not to clean up properly?

-          Has this been fixed in newer releases of YAWS?

The following is also seen in the nohup.out
=ERROR REPORT==== 19-Oct-2009::16:08:41 ===
SSL accept failed: enoproxysocket

=ERROR REPORT==== 19-Oct-2009::16:09:29 ===
SSL accept failed: enoproxysocket

Would also like to ask how the error enoproxysocket occurs.

The OS we're running on is Solaris 10.

Thanks

Regards,
Chih-Wei Yu

________________________________
NOTE: This e-mail message is subject to the MTN Group disclaimer see http://www.mtn.co.za/SUPPORT/LEGAL/Pages/EmailDisclaimer.aspx