Yes, but no memory ever gets freed. The system stops responding and is too busy dumping information to the console screen to respond to anything at the console or network.
And a system-wide panic would provide me with a core file to analyze and send off; though the progress we've made thanks to this group has helped a bit (swappiness = 0) has helped it remain stable longer.. right now we're using 18GB of swap instead of the 35 we were before. i haven't tried panic_on_oom, but thats a good idea and i was braindead not to think of it. On Mon, Jul 26, 2010 at 8:48 PM, Shane G <[email protected]> wrote: > Some more info please. > ... you get a OOM condition ?. > ... the/a large consumer gets killed ? > ... the system "halts" (explain) ?. > > You *want* a system-wide panic ?. If so, setting /proc/sys/vm/panic_on_oom to > "1" will > have the desired effect on non zLinux. > > Shane ... > > On Tue, Jul 27th, 2010 at 1:24 AM, Daniel Tate <[email protected]> wrote: > >> When websphere starts, it consumes all the memory eventually and >> halts, but not panics, the system. > <snip> ... >> At this point i see two problems: >> >> 1) Why is OOM Kill not functioning properly > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
