On 09/12/2004 at 09:22 Eric wrote:
Hi Sean,
Thanks for your reply, but that wasn't exactly what I was getting at.
I don't need to increase the system's imposed limit on the number of
open files. I'm more concerned to see if anyone has run across a
memory or fd leak in asterisk that sucks them
There should be no reason that I hit my limit of open files on this
machine. Restarting asterisk immediately solved the problem, so
I'm leaning towards a leak, however, I didn't have the opportunity,
in the moment, to check and see how many files and what type were
open.
This is a problem
/proc/sys/fs/file-max
This file defines a system-wide limit on the number of open
files for all processes. (See also setrlimit(2), which can be
used by a process to set the per-process limit, RLIMIT_NOFILE,
on the number of files it may open.) If you get
Asterisk does not do anything in this vein.
Simply
% echo somevalue /proc/sys/fs/file-max
a good starting point for this value would be double your existing
value.
% cat /proc/sys/fs/file-nr
will give you your existing max files. I would also suggest doubling
your inodes as well.
%
Hi Sean,
Thanks for your reply, but that wasn't exactly what I was getting at.
I don't need to increase the system's imposed limit on the number of
open files. I'm more concerned to see if anyone has run across a
memory or fd leak in asterisk that sucks them all up.
There should be no reason
On Thursday 09 December 2004 14:22, Eric wrote:
Hi Sean,
Thanks for your reply, but that wasn't exactly what I was getting at.
I don't need to increase the system's imposed limit on the number of
open files. I'm more concerned to see if anyone has run across a
memory or fd leak in asterisk
I don't need to increase the system's imposed limit on the number of
open files. I'm more concerned to see if anyone has run across a
memory or fd leak in asterisk that sucks them all up.
My apologies. If you are looking for leaking fd's in asterisk, I am
afraid I am not much help.
My asterisk process produced the following errors this morning:
Dec 8 10:44:07 WARNING[50315282]: rtp.c:829 ast_rtp_new_with_bindaddr: Unable
to allocate socket: Too many open files
Dec 8 10:44:07 WARNING[50315282]: chan_sip.c:2352 sip_alloc: Unable to create
RTP session: Too many open files
Easiest thing (as long as filedescriptors are being closed properly) is
to increase the number of allowed open files:
/proc/sys/fs/file-max
This file defines a system-wide limit on the number of open
files for all processes. (See also setrlimit(2), which can be
used
