Adam Conrad wrote: >Geert Nijpels wrote: > > >>It looks like this problem is related to bug #307567. Apache starts >>consuming 100% CPU after some requests. Restarting Apache lets it serve >>pages for a few minutes again. >> >>Downgrading to apache* 2.0.54-2 fixed the problem. We use >>apache2-mpm-prefork on an up-to-date sarge installation. >> >> > >Well, that's just bizarre, since 2.0.54-2 is the version with the new >util_ldap code from upstream, while 2.0.54-4 is completely reverted to the >tried and tested code from 2.0.53 and previous. Everyone else (so far) >has found 2.0.54-4 to be much more stable and useable. > >Are you pushing a LOT of LDAP requests through apache2? If so, I could >see how the 2.0.53 (2.0.54-4) code might eventually lead to a bunch of >hung connections (though, it's always been like this), but you'd have to >be pushing a LOT of LDAP requests through, or have a serious CPU/RAM >shortage for it to spike your system really badly. > > We are not pushing a lot of LDAP requests, something like 10/minute, and CPU / RAM should be enough. It's a dual xeon 2.00GHz with hyperthreading enabled, memory usage:
matrix:/home/geert# cat /proc/meminfo MemTotal: 1035908 kB MemFree: 99436 kB Buffers: 164168 kB Cached: 465308 kB SwapCached: 0 kB Active: 405092 kB Inactive: 388248 kB HighTotal: 130496 kB HighFree: 140 kB LowTotal: 905412 kB LowFree: 99296 kB SwapTotal: 1951888 kB SwapFree: 1951876 kB Dirty: 960 kB Writeback: 0 kB Mapped: 181368 kB Slab: 131984 kB CommitLimit: 2469840 kB Committed_AS: 608536 kB PageTables: 1924 kB VmallocTotal: 114680 kB VmallocUsed: 21152 kB VmallocChunk: 93364 kB I built the same setup on a second server on which I can not reproduce it despite doing 1000's of requests. This server does not do hyperthreading and has a single CPU. So I guess the next thing I will try is disabling hyperthreading and go back to 2.0.54-4. We are running: 2.6.11.11 #1 SMP Geert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
