Crontab Perl Script/Other Processes going defunct/zombie

[konextu]

Having an issue with agi-VDAD_ALL_outbound having like 15 or more processes showing up defunct/zombie.

Also having random issue with the AST_VDhopper.pl script running from crontab going defunct. This was causing the hooper to be emptied and dialable leads will go to zero. Running the script manually executes fine and shows clean output and works flawlessly but once it runs from crontab it caused the issues.

Rebooting has stopped the hopper script issue but still see zombie processes add up from the VDAD_ALL_outbound.

Ideas/thoughts?

[mflorell]

What Linux distro are you using?

[konextu]

slack 12.0 with 2.6.21.5 kernel

[konextu]

There where 227 zombie process of agi-VDAD_ALL_outbound running when i came in this morning from the campaign they ran yesterday evening. Not sure if that helps?

[mflorell]

I have not seen that happen on Slackware before, what version of Asterisk?

[konextu]

1.4.21.2... After last nights campaign runs we had 202 zombie of vdad_all_outbound

[mflorell]

Might be a known Asterisk 1.4 problem, try Asterisk 1.2.31 and see if the problem still exists.

[konextu]

Its just crazy, if I run the VDhopper manually the hopper loads up. but then after a minute it dumps to 0 and dialable leads goes to 0. only started happening once i started getting zombie processes.

[mflorell]

I have never seen that happen so I'm not sure what could be causing it.

[konextu]

I'm pretty sure i figured it out knock on wood.

I needed to get some huge lead lists imported asap and the leads had 0's in random phone fields (some of which where in the field going to phone_number) which of course would have got dropped, so i ran a find/replace to replace them with 9999999999 to get them in asap. The 9999999999 numbers where hanging up the VDAD_ALL_outbound agi. So that issue is fixed.

Matt, anyway to get the lead loader, API or webbased the ability to check other fields for numbers before marking a lead as bad? I created a cleansing program to clean them for now but its buggy and the API seems to drop the connection if the list being imported is over 2000 leads. Might be a PHP/APACHE setting i missed.

Thanks for the help guys and i'll keep ya posted.

[mflorell]

you can import over 100,000 leads using the web based lead loader providing the php.ini settings are set properly.

Why are you wanting to load in leads with impossible phone numbers?

[konextu]

Because its the way our software exports leads. THe phone number isnt always in the first phone number field. I'm guessing i'll have to make a program to dynamically check and move fields around on the fly to make sure a phone number always ends up in the first phone number.