vicidial.org

Anyone knows how or why i get these?

8987 ? Z 0:00 [agi-VDAD_ALL_ou] <defunct>
9147 ? Z 0:00 [agi-VDAD_ALL_ou] <defunct>
9293 ? Z 0:00 [agi-VDAD_ALL_ou] <defunct>
9481 ? Z 0:00 [agi-VDAD_ALL_ou] <defunct>
9483 ? Z 0:00 [agi-VDAD_ALL_ou] <defunct>
9635 ? Z 0:00 [agi-VDAD_ALL_ou] <defunct>
9769 ? Z 0:00 [agi-VDAD_ALL_ou] <defunct>
9771 ? Z 0:00 [agi-VDAD_ALL_ou] <defunct>
10473 ? Z 0:00 [agi-VDAD_ALL_ou] <defunct>
10634 ? Z 0:00 [agi-VDAD_ALL_ou] <defunct>
10637 ? Z 0:00 [agi-VDAD_ALL_ou] <defunct>
10699 ? Z 0:00 [agi-VDAD_ALL_ou] <defunct>
10726 ? Z 0:00 [agi-VDAD_ALL_ou] <defunct>
14762 ? Z 0:00 [VD_amd.agi] <defunct>
14808 ? Z 0:00 [VD_amd.agi] <defunct>
15260 ? Z 0:00 [VD_amd.agi] <defunct>
15317 ? Z 0:00 [VD_amd.agi] <defunct>
15383 ? Z 0:00 [VD_amd.agi] <defunct>
15611 ? Z 0:00 [VD_amd.agi] <defunct>
15678 ? Z 0:00 [VD_amd.agi] <defunct>
15689 ? Z 0:00 [VD_amd.agi] <defunct>
15731 ? Z 0:00 [VD_amd.agi] <defunct>
15844 ? Z 0:00 [VD_amd.agi] <defunct>
20781 tty1 Ss+ 0:00 /sbin/getty 38400 tty1
21424 ? Ss 0:03 /usr/bin/SCREEN -d -m -S ASTVDadapt /usr/share/astguiclient/AST_VDadapt.pl --debug
21426 pts/6 Ss+ 2:17 /usr/bin/perl /usr/share/astguiclient/AST_VDadapt.pl --debug
26096 ? Z 0:00 [agi-VDAD_ALL_ou] <defunct>
26387 ? Z 0:00 [agi-VDAD_ALL_ou] <defunct>
29500 ? Z 0:00 [agi-VDAD_ALL_ou] <defunct>

when you post, please post your entire configuration including (but not limited to) your installation method, vicidial version and build, asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box.

Similar to This:
Vicibox X.X from .iso | Vicidial X.X.X Build XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation

this IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

_______

AMD?

looks like it was caused due to bad numbers in the database i believe, but this is as.

vicidial 2.0.5rc5 asterisk 1.4.21.2 dedicated db server and stock vicidial setup no special things. Also using software for timing not a digium card or anything

vicidial version and build

the "rc5" is nice, but doesn't directly link to the code base anywhere. (Vicidial version and build are on all the Admin pages on the bottom left corner)

1) consider at least upgrading via svn to the latest "2.0.5", this has been known to squish some bugs

2) does this happen WITHOUT AMD?

This is an issue within asterisk. More over how it handles AGI scripts. It does not directly clean up after them once they are done launching. It has a reaper process that goes through and removes them. How many defunct processes are showing up at any given time? If the number is really high it is possible you are using a version of asterisk from before the reaper process was added.

using asterisk version 1.4.21.2. what version was the reaper added to?

Not entirely sure, but if you are using the version from our website:

http://download.vicidial.com/required-a ... ici.tar.gz

It definitely has the patch applied.

Thank you for the link.

i also see in that directory 1.4.27 and 1.4.30

which is best to use? and why?

whats the svn link for the latest version of 2.0.5 ?

We haven't updated 2.0.5 in a long time, we are on 2.2.1 now(branched it in January) and trunk is 2.4

bobbymc wrote:whats the svn link for the latest version of 2.0.5 ?

if you are starting with a "fresh" vicibox installation:

Code: Select all

cd /usr/src/astguiclient
ls
mkdir 2.0.5
mv * 2.0.5


Warning: mv: cannot move `2.0.5' to a subdirectory of itself, `2.0.5/2.0.5' (this is expected)

Code: Select all

ls

Should be empty except for the 2.0.5 folder with all the old (2.0.5) stuff in it

Code: Select all

cd /usr/src/astguiclient
svn co svn://svn.eflo.net:43690/agc_2-X/branches/agc_2.0.5
cd agc_2.0.5
perl ./install.pl


Copy sample configuration files to /etc/asterisk/ ? [n] y

Code: Select all

reboot