[Asterisk-Dev] EAGI : Pipe saturation

[Steven Critchfield]

On Mon, 2003-12-15 at 13:05, Areski wrote:
> Strange what you said ! That means that the fork is always failing in my
> *. I tested on two different computer and on the first, I lose 16 pipes
> for each EAGI executed and on the second I lose 17 pipes.
> Is this problem happens to all ? 

either it isn't happening to everyone else, or you are one of the very
few doing what you are. My question really is from what you list below,
are you doing anything with the audio stream, or can it be used as a AGI
only? Also are you actively trying to clear the audio on the pipe before
exiting to make sure you aren't leaving behind a buffer?

<disclaimer>
I am not really a C programmer, and while I can muddle my way through
some and read a bit more, I'm grasping at a few straws that seem like
they might be relevant.
</disclaimer>

> Below a part of my extensions.conf
> 
> exten => 1879,1,Answer
> exten => 1879,2,Wait(2)
> exten => 1879,3,eagi,DialAnMp3.agi
> exten => 1879,4,Hangup
> 
> if you check the number of pipe before and after the execution, you will
> see that a fews pipes aren't closed (only with eagi)...
> /usr/sbin/lsof -Rl|grep asterisk|grep pipe|wc -l
> 
> 
> So after a big amount of call, Asterisk cannot open new pipes because
> all has been used.
> 
> 
> Perhaps someone can pointed out which ones aren't closed!
> Thanks for your help,
> el kiki
> 
> 
> 
> 
> On Wed, 2003-12-10 at 16:26, Steven Critchfield wrote:
> > On Wed, 2003-12-10 at 07:01, Areski wrote:
> > > Hi all,
> > > 
> > > Little problem that it's getting bigger.
> > > When I use an EGAI script, I see the number of unclosed pipe going up
> > > all the time. For each EAGI script ran, Asterisk lose 16 pipes.
> > > /usr/sbin/lsof -Rl|grep asterisk|grep pipe|wc -l
> > > 
> > > That's bad because have awhile the system is saturated and asterisk
> > > doesn't work anymore! Impossible to open a new pipe ! 
> > > 
> > > The problem doesn't occur with AGI.
> > > Anyone have an idea how to fix it?
> > 
> > Looks like there could be a problem in launch_script where the fork
> > fails we don't close our file descriptors down. Not the problem you
> > describe, but a small problem anyways. Then again, if you failed to
> > fork, there could be bigger issues about to bring the app down anyways.
> > 
> > Outside of that, I didn't see any problems in the code on a quick look
> > through. I'll look a little deeper in a while. 
> 
> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
-- 
Steven Critchfield  <critch at basesys.com>