Hey Lukas, Indeed this is an AWS instance, its a custom AMI, the interesting thing about this is that the image has been cloned many times for different deployments and none of the other ones have experienced this, some are actually running with a ton of traffic through them.
Today I prepared a fresh instance (2.6.18-308.16.1.el5.centos.plusxen #1 SMP Tue Oct 2 23:25:27 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux) and voila, problem solved, replicating this image to the rest of the environments. I'm curious as to why this happen on those boxes though... Thank you for all your help, can't wait for the next release willy! On Mon, Mar 11, 2013 at 8:02 PM, Lukas Tribus <[email protected]> wrote: > > > Linux ip-x.x.x.x 2.6.21.7-2.fc8xen #1 SMP Fri Feb 15 12:34:28 EST 2008 > x86_64 x86_64 x86_64 GNU/Linux > > [...] > > CentOS release 5.4 (Final) > > This seems to be a weird config, you have CentOS 5.4 (released 2009 with a > 2.6.18 kernel), but you are running a xenified Fedora kernel compiled in > 2008. > > Is this some kind of Amazon instance, like EC2 or something? Did you > cloned this from a community provided AMI, like @ [1]? > > A fresh, updated and vendor supported (!) OS would certainly not hurt. > Just think of what kernel exploits you have in a kernel from 5 years ago, > a part from the problems you are seeing with haproxy. > > > [1] > https://aws.amazon.com/amis/64bit-fedora-8-xenified-kernel-2-6-21-7-2-fc8xen > >
