| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <87k5orf5kv.fsf@suzuka.mcnaught.org> Date: Fri, 09 Nov 2007 16:54:08 -0500 From: Douglas McNaught <doug@...aught.org> To: "Tobias Brox" <tobixen@...il.com> Cc: linux-kernel@...r.kernel.org Subject: Re: OOM killer problem - how to read the kernel log? "Tobias Brox" <tobixen@...il.com> writes: > We have a database server which we've had some problems with, we've > had some serious crashes (particularly during postgres vacuuming) > which couldn't be fixed without hardware reboot. We assumed that the > problem would go away by itself after upgrading the server to a new > box with 32G of RAM ... but, alas, one of the first days in operation > it first killed lots of postgres children during the evening, and > finally it crashed and required hardware reboot. The box is certainly > not out of memory, but after reading some posts here, I've understood > that memory management is a complex issue. > > We're running 32 bits linux, maybe it would help to upgrade to 64 bits? Big-time. There are a lot of "artificial" internal kernel memory limits in the 32-bit architecture, so you can run up against those (triggering the OOM killer) even if you have plenty of application memory. 32GB in the box actually might be counter-productive unless you're running 64-bit, because just tracking that much memory will consume precious low kernel RAM. -Doug - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists