On Thu, Oct 07, 2010 at 11:11:13AM -0400, MK wrote: > Two minutes then a seg fault, together with the infinite recursion > possibility, imply something is eating a lot of memory then getting > killed. Since the server apparently survives, that could be a single > apache processes if you are running it forked not threaded, or it could > be something else. > > So here's a suggestion in addition to strace: before you make your > request, fire up "top" in a console. Press shift-f to select sort > field order and choose 'n', "memory usage". If this is a dedicated > server, apache should be at the top to begin with -- watch and see if > the mem usage grows rapidly and then the process gets killed by the > kernel.
The following will confirm it: dmesg | tail -30 | grep killer Look for 'oom-killer' which is the Out of Memory Killer process. If you find this, than your apache processes are slowly growing (over the two minutes) and the kernel is killing them off. Alfie ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
