what process is allocating memory and causing oom-kill?
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
what process is allocating memory and causing oom-kill?
We have a system which periodically (about ones a month) is generating a oom-kill. The server is running an Oracle 10.2.0.3 database and this is the process which is being killed.
The server has 4 GB of memory.
What we find very strange is that 'committed_AS' in /proc/meminfo is very large and seems to be increasing. At the moment it is:
You don't say what version of Linux you're running. Have you already tuned your kernel, per the Oracle install document(s), as they apply to Linux? There are several parameters that you have to tweak first.
If you don't tweak the kernel parameters correctly, you'll have problems. You'll also have problems if you don't have enough swap space defined. There's a whole list of things you have to do to get Oracle running right, along with the correct kernel level. The oom_killer will hit you if things aren't done right, or if your DBA's are doing something incorrect.
We are running Red Hat Enterprise Linux ES release 4 (Nahant Update 4).
I did not install the system so I need to check how the kernel is tuned for Oracle. I dont have access to the system right now, but will update the thread as soon as I have checked it.
Is there a way to see what processes have been committed memory and how much since /proc/meminfo shows Committed_AS: 10364820 kB?
Not that I am aware of, other than the /proc/meminfo file.
Oracle is a bit twitchy if it's not set up right, and if the kernel parameters aren't set. Also, check with your DBA's, and see what they're up to. If they're trying to merge/sort/do-something-with a 200GB database, and you're running off 4 GB of system RAM with 512 MB of swap, chances are you'll have problems.
They have to set parameters within Oracle too, to make it play nice on the host OS.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.