On Wed, Aug 12, 2015, at 04:06 AM, Stefan Viljoen wrote:
> Hi Steve
>
> Just running about 50 calls??
>
> If I do
>
> lsof | grep asterisk | wc -l
>
> to narrow the realm of what is reported I still get just under 100 000
> files:
>
> lsof | grep asterisk | wc -l
> 95903
>
> with 50 calls run
Hi Steve
Just running about 50 calls??
If I do
lsof | grep asterisk | wc -l
to narrow the realm of what is reported I still get just under 100 000
files:
lsof | grep asterisk | wc -l
95903
with 50 calls running.
So apparently this is excessive? I can only guess that there must be a MAJOR
bug
On Tue, 11 Aug 2015, Stefan Viljoen wrote:
I suspected something like that, though repeatedly running
lsof | wc -l
Always stays quite low - 100 000 open files, which is still 8 times less
than the system maximum as confirmed by running ulimit -n
What the 'h' are you doing that takes x00,000
In article <002b01d0d414$36af31b0$a40d9510$@verishare.co.za>,
Stefan Viljoen wrote:
> >> Anybody else ran into this?
>
> >No, but I would ask myself why so many file descriptors are being used.
> >It sounds like you have a file descriptor leak (not being closed when
> >finished with).
>
> Hi Ton
Hi Stefan,
we ran into a similar problem using Debian.
There we are able to check the current limits using:
pidof asterisk -> 23351
cat /proc/23351/limits
Output:
Limit Soft Limit Hard Limit Units
Max open files1024 1024 files
I thin
>> Anybody else ran into this?
>No, but I would ask myself why so many file descriptors are being used.
>It sounds like you have a file descriptor leak (not being closed when
>finished with).
Hi Tony
Thanks for replying.
I suspected something like that, though repeatedly running
lsof | wc -l
