Bug 208345

Summary: Hundreds of zombies on my system
Product: [Fedora] Fedora Reporter: ptomblin
Component: glibcAssignee: Jakub Jelinek <jakub>
Status: CLOSED WORKSFORME QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 5   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
URL: http://xcski.com/munin/xcski.com/allhats.xcski.com-processes.html
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-09-30 07:23:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
ps auwwfx none

Description ptomblin 2006-09-27 22:22:21 UTC 
Description of problem:
Since yum installed glibc 2.4-11 on the 16th of this month, my system has been
accumulating zombies at a horrific rate.

Version-Release number of selected component (if applicable):
glibc-2.4-11

How reproducible:
Very

Steps to Reproduce:
1. Use the system
2. Note the number of processes creeping up at a fairly fast clip.
3.
  
Actual results:
Over 700 processes on my system, and increasing at a constant rate.

Expected results:
Approximately 200-250 processes on my system at any given time.

Additional info:
See the above munin graph showing the number of processes increasing.

I'm attaching the results of a "ps auwwfx".
Comment 1 ptomblin 2006-09-27 22:22:21 UTC 
Created attachment 137260 [details]
ps auwwfx
Comment 2 ptomblin 2006-09-28 00:33:36 UTC 
An additional symptom: when I try to shutdown, I get the following:

shutdown: timeout opening/writing control channel /dev/initctl

init: timeout opening/writing control channel /dev/initctl

I had to hit the reset button to reboot.
Comment 3 ptomblin 2006-09-28 11:00:40 UTC 
Rebooting appears to have fixed the problem.  It appears that upgrading
something, probably glibc, without rebooting was the cause.
Comment 4 Jakub Jelinek 2006-09-30 07:23:48 UTC 
Couldn't reproduce this on any of the 6 boxes I have upgraded FC5 glibc to.
If anything, it would be a kernel issue.