Bug 89249 - size-512 in /proc/slabinfo keeps growing and machine dies after 10 day
Summary: size-512 in /proc/slabinfo keeps growing and machine dies after 10 day
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.3
Hardware: i586
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-04-21 21:55 UTC by Francois Romieu
Modified: 2007-04-18 16:53 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-04-14 21:34:57 UTC
Embargoed:


Attachments (Terms of Use)
slab-512 output samples for 25 minutes (16.26 KB, text/plain)
2003-04-21 22:03 UTC, Francois Romieu
no flags Details
/proc/slabinfo (3.40 KB, text/plain)
2003-04-21 22:04 UTC, Francois Romieu
no flags Details
/proc/meminfo (601 bytes, text/plain)
2003-04-21 22:05 UTC, Francois Romieu
no flags Details
ps auwx output (8.43 KB, text/plain)
2003-04-21 22:06 UTC, Francois Romieu
no flags Details
lsmod output (954 bytes, text/plain)
2003-04-21 22:07 UTC, Francois Romieu
no flags Details
/proc/cpuinfo (318 bytes, text/plain)
2003-04-21 22:08 UTC, Francois Romieu
no flags Details
/sbin/ifconfig output (1.12 KB, text/plain)
2003-04-21 22:09 UTC, Francois Romieu
no flags Details
Shaping script (3.28 KB, text/plain)
2003-04-21 22:17 UTC, Francois Romieu
no flags Details

Description Francois Romieu 2003-04-21 21:55:35 UTC
Description of problem:  
  
Machine serves http/dns/smtp. After 10 days, services stop responding while  
ping is still ok. fork/vfork error appear in the logs. Machine ends  
unusable. apache is configured to regularly restart and no process shows 
significant memory usage. 
  
Version-Release number of selected component (if applicable):  
  
2.4.18-27.7.x  
  
How reproducible:  
  
The machine should stop within 2/3 days for the third time.  
  
Steps to Reproduce:  
1.  
2.  
3.  
      
Actual results:  
  
  
Expected results:  
  
  
Additional info:

Comment 1 Arjan van de Ven 2003-04-21 22:01:35 UTC
so something is leaking memory; and since you're the first report of this I have
to assume it's something uncommon in your configuration; could you post lsmod
output and maybe describe things that could be uncommon in your setup ?

Comment 2 Francois Romieu 2003-04-21 22:03:01 UTC
Created attachment 91214 [details]
slab-512 output samples for 25 minutes

Comment 3 Francois Romieu 2003-04-21 22:04:02 UTC
Created attachment 91215 [details]
/proc/slabinfo

Comment 4 Francois Romieu 2003-04-21 22:05:01 UTC
Created attachment 91216 [details]
/proc/meminfo

Comment 5 Francois Romieu 2003-04-21 22:06:31 UTC
Created attachment 91217 [details]
ps auwx output

Comment 6 Francois Romieu 2003-04-21 22:07:32 UTC
Created attachment 91218 [details]
lsmod output

Comment 7 Francois Romieu 2003-04-21 22:08:25 UTC
Created attachment 91219 [details]
/proc/cpuinfo

Comment 8 Francois Romieu 2003-04-21 22:09:34 UTC
Created attachment 91220 [details]
/sbin/ifconfig output

Comment 9 Arjan van de Ven 2003-04-21 22:12:26 UTC
sch_sfq                 4288   6 (autoclean)
cls_u32                 5444   1 (autoclean)
sch_cbq                13248   1 (autoclean)

are 3 modules that are "uncommon" a bit; are you actively using them?

Comment 10 Francois Romieu 2003-04-21 22:16:28 UTC
The machine is limiting bandwidth at ~1.8Mbps. Setup script sent as attachment.  

Comment 11 Francois Romieu 2003-04-21 22:17:26 UTC
Created attachment 91221 [details]
Shaping script

Comment 12 Francois Romieu 2003-04-21 22:27:59 UTC
> sch_sfq                 4288   6 (autoclean) 
> cls_u32                 5444   1 (autoclean) 
> sch_cbq                13248   1 (autoclean) 
> 
> are 3 modules that are "uncommon" a bit; are you actively using them? 
 
Yes, see http://pulsar.zoreil.com/rrdtool/eth0-weekly.gif. 
 
Previous setup (2.4.18-3) didn't show these symptoms but I can't claim that 
the bandwidth was limited in the exact same way. 


Note You need to log in before you can comment on or make changes to this bug.