similar to: Asterisk 1.6 produces *many* zombie processes on Debian.

We have two Asterisk servers. One is a live server supporting our customers, and the other is a backup server that's being upgraded and pressed into service. Both servers have a Digium TE405P T1 card in them, and in order to test the T1 service on the backup server, I've created a T1 crossover cable (as per http://www.voip-info.org/wiki/view/crossover+T1+cable) that goes from port 4 on the

Dear listers, I'm facing a puzzling situation with Digium TDM2400 card (12 FXO / 12 FXS). Once a day or so we detect 1 or 2 zombie FXO channels. These can be either outbound or inbound calls. I thought this could be related to obsolete DAHDI or Asterisk versions, so I upgraded to 2.4.0 and 1.6.2.15 respectively (OS: Ubuntu 10.04 64 bits). To no avail; the zombie channels keep showing up.

This past holiday weekend has resulted in some real groaners when it comes to bugs in our dialplan, making obvious the need for some changes in our procedures. First, our hours of operation for Christmas Eve, Christmas, Boxing Day and New Year's Eve had changed with little to no notice. Okay, fine, whatever, I fix. Our Christmas Eve hours (made worse by being Monday this year) dialplan

On 2016-02-17 15:32, Richard Mudgett wrote: > On Wed, Feb 17, 2016 at 5:15 PM, Ernie Dunbar <maillist at lightspeed.ca> > wrote: > >> Hi everyone. >> >> We have an Asterisk server running Debian Squeeze, with Asterisk >> v1.8.13.1 (basically, the Debian Stable version for Squeeze, but >> with some minor source code changes specific to our site).

Okay, so here's the configuration I have for MySQL Realtime (Asterisk version 1.6.2.17): In /etc/asterisk/extconfig.conf: sipusers => mysql,mya2billing,cc_sip_buddies In /etc/asterisk/res_mysql.conf: [mya2billing] dbhost = localhost dbname = mya2billing dbuser = a2billinguser dbpass = REDACTED dbport = 3306 And here's the error messages I get: voip2*CLI> realtime mysql status

Hi, How can I figure why some domain is still in zombie state, like these ones: master-xen root /vm/ttylinux# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 574 1 r----- 90.5 Zombie-small-11 28 0 1 ---s-d 0.9 Zombie-small-17 34 0 1 ---s-d

Hi: i have a hosted server with asterisk and a2billing as a billing plattform, when i am trying to enter the server remotely by ssh, memory error message displayed: -bash: fork: Cannot allocate memory i have 1GB RAM on the system ,and there is 15 to 25 concurrent calls on the system is'nt 1GB of RAM sufficient for this volume of calls on Asterisk. and when iam using "top"

I'm monitoring Asterisk with Nagios. Nagios constantly alerts because of too many zombie processes. I eventually had to disable the notification for the alert but why does Asterisk create so many zombie processes, I've see more than 30 at times and it generally stays in the 20s... just seems unusual and wondering if it's harmful, thanks in advance. -------------- next part

We have been researching stuck zombie processes in our libvirt lxc containers. What we found was: 1) Each zombie’s parent was pid 1. init which symlinks to systemd. 2) In some cases, the zombies were launched by systemd, in others the zombie was inherited. 3) While the child is in the zombie state, the parent process (systemd) /proc/1/status shows no pending signals. 4) Attaching gdb to

Hi everyone. We have an Asterisk server running Debian Squeeze, with Asterisk v1.8.13.1 (basically, the Debian Stable version for Squeeze, but with some minor source code changes specific to our site). We're trying to upgrade to 11.13.1 (The Debian Stable version for Jessie), but I've run into a snag when compiling res_fax_spandsp (and yes, we really need that module). The old

This *should* be something that's easy to fix, but apparently I'm not doing something right. Our SIP long distance provider is telling us to only use formats G.723 and G.729, so I've set up their trunk configuration in sip.conf as such: [t564] type=friend host=XXX.XX.56.4 context=default disallow=all allow=g723 allow=g729 However, the Dial application gives the following error:

Hello I just updated the kernel, dahdi-linux and dahdi-tools Im also using now asterisk 1.4.26.1 And im still with a red light (not RED/YELLOW anymore): [root at catumbela ~]# /etc/rc.d/init.d/dahdi status ### Span 1: TE4/0/1 "T4XXP (PCI) Card 0 Span 1" (MASTER) HDB3/ RED 1 PRI CAS RED 2 PRI CAS RED 3 PRI CAS RED 4 PRI

I have a problem that sometimes lines will go into what I call never never land. The Asterisk system will put a line with <Zombi> on it when you type show channels it will make the analog phone line dead. And on the CLI it says: astsvr*CLI>Zap/1-2<ZOMBIE>(macro-twoline-exten,s,1)Up Dial Zap/1-2|20|r I have tried to release it with soft hangup Zap/1 & also soft hangup

Hi- Asterisk (CVS 7/30/03) seems to leave my AGI processes (written in Perl) as "zombies", even though they exit normally with exit(0). I am running Red Hat 9. I tried the same AGI etc with an older CVS (7/1/03) and this does not happen. I think a zombie process is a process that doesn't release some resource (shared memory, etc), so I'm worried about this since I call my AGI

You need to ensure that traffic to the SIP box is sent to the correct IP. Also if you use split-tunnel (eg: not redirect-gateway def1) you must make sure NAT and traffic redirection works as is so the Asus router knows it should send the traffic through tunnel and not via WAN. IMPORTANT: Then you must, in the ASUS RT-N66U make a port forward inwards from TUN to the phone client. I would suggest

I am using a2billing as billing software ,and I make an 800 call service which means that the destination extension should be build I put this code at extensions.conf exten => 99909994,1,SetAccount(2704714849) exten => 99909994,2,Wait,2 exten => 99909994,3,DeadAGI(a2billingp.php) exten => 99909994,4,Wait,2 exten => 99909994,5,Hangup its not stable ,its works for 3 times

Can you try with this systemd unit file. Restarting does not close all prosesses with that one. ( you need : ExecReload=/bin/kill -HUP $MAINPID ) Jessie used probely sysv and not systemd, which should explain why there are so many zombies. [Unit] Description=Samba AD Daemon Documentation=man:samba(8) man:samba(7) man:smb.conf(5) After=network.target [Service] Type=notify NotifyAccess=all

Hello, I've compiled Samba 4.7 from repository using a Debian 9 machine and I've noticed that the system started to create zombie processes of samba: # ps aux |grep "Z" USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 502 0.0 0.0 0 0 ? Z 13:01 0:00 [samba] <defunct> root 1346 0.0 0.0 0 0 ? Z