similar to: Asterisk 12 - zombie processes

Hello all, We have recently upgraded some of our services to Asterisk 12 with PJSIP. We have 2 issues related to DTMF: 1. in the regular SIP channel we had DTMF auto mode, which adapted the DTMF settings according to the incoming INVITE - RFC2833 or inband. The is no such settings in PJSIP. Do you know is there is a plan to develop it? 2. When we setup 2 peers, one RFC4733 and the other inband,

Hello everyone, I am trying to activate Music On Hold using DB on Asterisk 13. It works fine but in order to use new Music On hold definitions I have to reload the moh module. - The following is my configuration in extconfig.conf - I added the following line: musiconhold.conf => mysql,asterisk,bit_ast_config - The following is the table in the database: mysql> select * from

Hi everyone, I am running asterisk with release 12.1.0.rc3 and PJSIP. I have a peer which sends OPTIONS method for session keep-alive, and the asterisk is not responding to it. That of course disconnects the call after a few minutes. Is there a settings in the PJSIP.conf to respond to in dialog OPTIONS method? Looking at the documentation I haven't seen it. Does anybody know a workaround?

Hello Asterisk Users, I have been looking for similar auto dtmf mode implementation on pjsip, but didn't see it coming, so I decided to give it a try. My basic plan was to do it as simple as possible with minimum changes because I am not familiar with all Asterisk code. My idea is to use rfc4733 settings, but when going over the codecs check if telephone-event appear and if not set the dtmf

Hi Yaron, Not sure I understand your question. Wasn't <mutex> one of the more important C++11 features that LLVM would like to use? On Thu, Sep 25, 2014 at 1:24 AM, Yaron Keren <yaron.keren at gmail.com> wrote: > Vadim, > > Thanks for the feedback on the -win32. A dependency on a small DLL with > BSD license does not sound too bad, but performance regression is

When LLVM's configure finds a usable <pthread.h>, it prefers to use that rather than the home-grown stuff. However if LLVM is configured with --disable-pthreads, both mingw flavors produce the same results. BTW, I've tried to quantify the slowdown: a quick test indicates that LLVM build that uses pthreads is about 10% slower than the one which doesn't. This is less that I

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 an issue with our Asterisk install where Asterisk produces many Zombie processes (on the order of several hundred per minute) until either the Asterisk server is restarted (and the zombies die a natural death), or the kernel runs out of PID space (happens within hours) and brings the system to a halt. This problem only happens when the server is under some non-trivial load. We were

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 all- Thanks to Mark Spencer for finding this patch: If you are experiencing leftover zombie processes from your AGI scripts that have terminated, this is apparently due to a RedHat 9 threading issue introduced in a recent update.... To get rid of this, try entering the following line before you start asterisk: export LD_ASSUME_KERNEL=2.4.1 It works for me - I'm still checking to

Hello Asterisk users and developers, The last few weeks we had several crashes on live asterisks running versions 12.2.0rc1 / 12.6.1 with PJPROJECT versions 2.1.0 / 2.2.1. We opened a ticket - ASTERISK-24471. After investigating the issue I can say that the scenario is a CANCEL being received while handling ANSWER and before generating the 200OK response. Looking at the core file we see that

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

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

On Fri, Jan 29, 2016 at 10:25:08AM -0800, Peter Steele wrote: >On 01/29/2016 05:08 AM, Peter Steele wrote: >> 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 >>

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

each scp or ssh I do to a 4.8-stable machine I have gives me two 'zombie' processes: root 282 0.0 0.4 5236 2184 ?? I 7:41AM 0:00.05 sshd: imp [priv] (sshd) imp 284 0.0 0.4 5252 2260 ?? I 7:41AM 0:00.01 sshd: imp@notty (sshd) I had been running 4.8-RC when I first noticed it and reported it. People here said this had been fixed shortly after 4.8, but it is

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

Hello, I am running a Samba 4 DC, recently upgraded to the latest version and I have just installed a member server to run as a File Server (Samba 4.1.9). While it seems to be working properly, we are getting a lot of zombie nmbd processes on the member server, running the command *pidof nmbd* results in: *[root at BHFS01 etc]# pidof nmbd* *12861 12644 12404 12236 12071 11885 11720 11553 11388

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.

https://bugzilla.mindrot.org/show_bug.cgi?id=2646 Bug ID: 2646 Summary: zombie processes when using privilege separation Product: Portable OpenSSH Version: 7.2p2 Hardware: ix86 OS: Linux Status: NEW Severity: minor Priority: P5 Component: sshd Assignee: unassigned-bugs at