Hi, sorry for topposting, but Outlook is notoriously bad at inlining..
In reply to Lukas Tribus:
Uptime is some 200 days
jedc@web8:/home/jedc>$ free -m
total used free shared buffers cached
Mem: 48253 47843 410 0 2747 24841
-/+ buffers/cache: 20254 27998
Swap: 32767 368 32399
Acording to RHEL network, the kernel I'm running now is the latest available,
so upgrading is not really an option at this time.
Alas a reboot is not really an option right now (downtime scheduling,
announcement etc etc..), but I will prioritize it in our plans.
Med venlig hilsen,
Jens Dueholm Christensen
Survey IT
-----Original Message-----
From: Lukas Tribus [mailto:[email protected]]
Sent: Thursday, September 12, 2013 3:50 PM
To: Jens Dueholm Christensen; [email protected]
Subject: RE: Page allocation failure
Hi!
> A few days ago one of our machines logged this:
>
>
>
> Sep 10 10:54:29 web8 kernel: haproxy: page allocation failure.
> order:1,
> mode:0x20
The kernel has problems allocating memory to haproxy. Since we don't see the
OOM killer in action, I guess your memory is heavily fragmented.
I guess this box has a long uptime?
How much free RAM does "free -m" show?
> Should I be worried?
Memory allocation failure will lead to application failures. I would take this
seriously.
> An upgrade to 1.4.24 is planned Real Soon(TM), but I am unsure if it's
> a known error that's fixed in a later version.
Upgrading to 1.4.24 is important, there are several issues with 1.4.22.
However, it will not fix this problem, as this is not a bug in haproxy.
The problem mostly depends on your kernel.
A quick fix is to reboot the box, which will make the problem go away for now.
I suggest upgrading OS/kernel to a more recent version.
You can read more about this here:
http://www.cyberciti.biz/faq/linux-page-allocation-failure-erro/
Regards,
Lukas
