0

So every now and then (once in a month or two) one of our processes, running a critical piece of code that we don't want to touch, is being killed by the Out Of Memory killer. It says so in /var/log/messages.

We are going to address the cause separately. I want to monitor and address the effects right now. I want us (the sysops) to be sent a notification whenever this happens, so that we can wait for an hour or so for the traffic on the cluster to die down a bit and restart the task that was killed.

How do I arrange for such a notification to happen?

I think we run Red Hat Linux on our boxes if it matters.

  • I suggest running cat /etc/*-release | mail <receiver> every once in a while so you guys at least know what OS is running the "critical piece of code"... – confetti Aug 6 '18 at 7:00
  • 1
    This is a abuse of that closure reason. Clearly, a question about the OOM killer and logs in /var/log/messages is talking about a Unix or Linux system. – JdeBP Aug 6 '18 at 7:14
  • I agree. I think it's a very bad question and the problem should be solved by the root of it and therefore might be better off on stack overflow, but in the context of this specific question it does fit on the unix&linux SE imo. – confetti Aug 6 '18 at 7:15

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.