[asterisk-users] Defunct / zombie AGI after some execution time
Mark
mark at pyme.net
Mon Nov 13 08:29:59 MST 2006
Hello,
We are running Asterisk-1.0.12 in a CentOS 4-4.2 system, kernel
2.6.9-42.0.3.ELsmp.
We have some custom AGI, and when we launch Asterisk the system works fine.
But **after some time**, each AGI execution generates a zombie <defunct> process.
We believe that it's not a problem in the AGI code, because Asterisk+AGI is
working fine in the first "n" minutes/hours. This is a pstree sample:
init-+-asterisk---asterisk---48*[asterisk]
But after some execution time, this is the pstree output:
init-+-asterisk---asterisk-+-28*[asterisk]
| |-asterisk-+-21*[xxxxxxxxx.agi]
| | `-40*[xxxxxxxxx.agi]
| |-5*[asterisk-+-yyyyyyyyy.agi]
| | |-zzzzzzzzz.agi]
(...)
Each agi is a defunct process. It dies when the call (parent) finishes.
When the first zombie appears, then ALL next AGI launched from Asterisk
generates a zombie.
We have tested some improvements to solve the problem, with no success:
- Upgrade from RedHat 8 to Centos 3.x
- Upgrade from Centos 3.x to Centos 4.x
- LD_ASSUME_KERNEL=2.4.1
- ulimit -n 65535
- Upgrade from asterisk 1.0.7 to 1.0.12
Currenly we can not easily migrate from asterisk-1.0.x to 1.2.x
Any ideas?. Could be Debian a solution?
Thank you.
More information about the asterisk-users
mailing list