Hi,
We are using 64 bit version of centos, and the ram of this system is 1gb so should we increase this limit to 100000 in the limits.conf
Regards senthil
On Sun, Jun 30, 2013 at 12:31 AM, Michael Curran [email protected]wrote:
Are you running 32-kernel for centos?
32-bit limits in the 4500 range for open connections due to the memory constraints
We usually set our open file limits to 100I specifically for Stunnel user
*Sent from my Verizon Wireless 4G LTE DROID*
Senthil Naidu [email protected] wrote:
Hi
We are using stunnel 4.32 on centos and our ulimits in limits.conf are as follows
soft nofile 16384
hard nofile 65536
We keep getting the error “too many open files(24)” and stunnel does not accept new connection till we restart the same
Is this ulimit proper or we need to increase the same , we are look for 3000 to 5000 connections
Regards
Senthil
2013/6/30 Senthil Naidu [email protected]:
Hi,
We are using 64 bit version of centos, and the ram of this system is 1gb so should we increase this limit to 100000 in the limits.conf
limits.conf is used only for interactive login sessions (i.e. when you login to your system as a stunnel user). It is _not_ used by daemons in your system (unless CentOS does something unusual in the startup script). You can check limits of a running process in /proc/PID/limits file, most probably your stunnel has still the default value (1024 usually). You should use ulimit -n in your stunnel startup script to modify file descriptor limit.
-- Janusz Dziemidowicz
Hi janusz,
Thanks for the mail, after checking the limits in /proc/PID/limits file is was found to be 1024 after adding the ulimit -n <value> to stunnel startup the same was showing the new value.
Thanks for the support
Regards senthil
On Mon, Jul 1, 2013 at 1:55 PM, Janusz Dziemidowicz [email protected]wrote:
2013/6/30 Senthil Naidu [email protected]:
Hi,
We are using 64 bit version of centos, and the ram of this system is 1gb so should we increase this limit to 100000 in the limits.conf
limits.conf is used only for interactive login sessions (i.e. when you login to your system as a stunnel user). It is _not_ used by daemons in your system (unless CentOS does something unusual in the startup script). You can check limits of a running process in /proc/PID/limits file, most probably your stunnel has still the default value (1024 usually). You should use ulimit -n in your stunnel startup script to modify file descriptor limit.
-- Janusz Dziemidowicz
-
Janusz Dziemidowicz -
Senthil Naidu