DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=38065>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38065 ------- Additional Comments From [EMAIL PROTECTED] 2005-12-30 02:10 ------- (In reply to comment #2) [..cut..] > > I've added this two lines: > > ulimit -S -m 25600 > ulimit -H -m 25600 > > on top of apache2ctl script (which actually only calls "/usr/sbin/apache2 -k > start"), without any result. Top still shows apache2 processes with resident > size >= 30Mb. It already crashed our server two times, here's top output in > last Ups. I just traced ulimit of bash and it does not seem to set the correct limit. It sets RLIMIT_RSS. ulimit -v sets RLIMIT_AS which also does not seem completely correct to me, but this is at least checked by the brk syscall. So please try again with ulimit -v. Anyway it may be hard to find out the cause for this as you are using a fastcgi module as a third party module. [..cut..] > > We have some info that may be useful though. From time to time appear apache > processes consuming a lot of memory. They grow in time, mostly exiting > normally, > so I'm not sure they're related to this bug. But I guess that's better than > nothing. Below is a trace of one of this kind of processes. Can you catch such processes with gdb and sent a backtrace or even better try to catch the whole flow with ltrace? [..cut..] -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
