[Asterisk-Dev] EAGI : Pipe saturation

Areski areski at e-group.org
Mon Dec 15 12:05:17 MST 2003

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 ? 
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. 

More information about the asterisk-dev mailing list