similar to: dovecot-auth zombie procs

Yesterday a user reported to me that she received a bunch of emails that were not addressed to her. I'm using dovecot version 0.99.11 along with postfix and amavisd-new. I don't know how this happened because each mail file in /var/mail/ is only readable by the user. Has anyone ever heard of this happening before?

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

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 >>

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

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 > zombie was inherited. > 3) While the child is in the zombie state, the parent

Folks- Hans Morten Kind was kind enough to confirm the issue I'm having with large mailboxes and the mail-cache-fields.c file (line 26: unreached error in logs when the imap process crashes out on large Maildirs). Has anyone implemented a fix for this that is both tested and applicable without making manual code changes myself, since I don't trust myself slashing about in source files?

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

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

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.

Hi all, Some time ago I posted an issue regarding the hangup of active calls from the CLI and someone told me that "soft hangup" should work. Well, in fact it does work, but only if the channel is known, i.e. it doesn't work for zombie channels. For example, I have this scenario (CLI output of command "iax2 show channels") IP-AM-PBX*CLI> iax2 show channels Channel

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

Hello Asterisk users, We noticed that on Asterisk 12 zombie processes are being generated - They are released after a while, but we have around 10-20 zombie processes running. We are not sure if this is a normal behavior or an issue. We saw in the documentation that the bridging module creates zombie processes - is it related? Thank you, Yaron. -------------- next part -------------- An HTML

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

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

Hi, I am using SHARED() function to push destination channel info (i.e. audio codec) into "source" channel, in order to record into a customer CDR field. My dialplan looks like: [default] exten => _X.,1,Set(_X-SRC_CHANNEL=${CHANNEL}) exten => _X.,n,Dial(SIP/user at domain.net,30,M(getCalledInfo)) exten => h,1,Set(CDR(DST_CODEC)=${SHARED(X-DST-CODEC,${CHANNEL})})

Hi all, I'm experiencing a problem with SIP channels going ZOmBIE after the following sequence of events: - IAX2 client calls SIP client - SIP client consultive transfers (using sip REFER) the call to a MeetMe extension, and hangs up. At this point, the IAX2 client will indeed be in the meetme room, but a 'show channels' at the * CLI reveals that the SIP channels that were involved

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

Hi, We encounter a problem in VDSM project that virt-v2v become zombie task while importing vm from vmware. When virt-v2v is in 'copy disk' mode and we someone deletes the vm at vmware the process hang in read() method, I am pretty sure that its not virt-v2v problem because when I run it from the shell virt-v2v exit with an error, still maybe someone have an idea.... I wrote a small

At the moment xm shutdown --all --wait hangs with a zombie domain. This means it hangs xend stop on dom0 shutdown.. I see no use for this behaviour, it would be better to skip Zombie-Domain-* domains. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

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