[prev in list] [next in list] [prev in thread] [next in thread] 

List:       haproxy
Subject:    Re: 1.5-dev22 crash with kernel messages, 1.4.18 is fine
From:       Thomas Heil <heil () terminal-consulting ! de>
Date:       2014-02-28 14:01:26
Message-ID: 531096B6.4020203 () terminal-consulting ! de
[Download RAW message or body]


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

On 28.02.2014 01:33, Federico Iezzi wrote:
> Guys we fix these problems using a kernel >= 3.8
> With Ubuntu 12.04.4 we are using Kernel 3.8 and 3.11 from Canonical
official repository with out any issue. With 3.5 and stock 3.2 we had a
lot trouble.
I can confirm that 3.4.80+ is running fine even with grsec.
>
> Regards,
> Federico
> Il giorno 27/feb/2014, alle ore 13:01, Sander Klein <roedie@roedie.nl>
ha scritto:
>
>> Hi,
>>
>> I can confirm that using grsec kernel with haproxy can sometimes be a
bit tricky.
>>
>> For instance, 3.2.54 with grsec crashes with me after ~8 hours while
3.2.55 and 3.2.52 with grsec do not. Kernels with grsec just need more
testing because their stability can vary.
>>
>> Greets,
>>
>> Sander
>>
>>
>> On 27.02.2014 11:29, Cedric Maion wrote:
>>> I agree that it does indeed look like a kernel issue (in the intel eth
>>> driver?), however 1.5 is doing something new that triggers this.
>>> Any idea of a significant 1.4 -> 1.5 change that can affect what is
>>> happening in the kernel?
>>> This kernel is indeed not the stock Ubuntu kernel, but the default one
>>> provided by the hosting company (OVH in that case)... I would really
>>> like not having to recompile the kernel and play too much with the
>>> production environment (sadly this issue never popped in my dev & lab
>>> environments).
>>> So any haproxy related idea would be very welcome...!
>>> On Thu, Feb 27, 2014 at 11:06:38AM +0100, Lukas Tribus wrote:
>>>> Hi,
>>>>> Just upgraded a production node from 1.4.18 to 1.5-dev22.
>>>>> Ran fine for a couple of minutes then crashed with the following
kernel
>>>>> messages:
>>>>>
>>>>> WARNING: at mm/page_alloc.c:2107 __alloc_pages_nodemask+0x1fd/0x790()
>>>>> Hardware name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
>>>>> Pid: 23190, comm: haproxy Not tainted 3.2.13-grsec-xxxx-grs-ipv6-64 #1
>>>>> Call Trace:
>>>>> [<ffffffff810f1ded>] ? __alloc_pages_nodemask+0x1fd/0x790
>>>>> [<ffffffff81089f3b>] warn_slowpath_common+0x7b/0xc0
>>>>> [<ffffffff81089f95>] warn_slowpath_null+0x15/0x20
>>>>> [<ffffffff810f1ded>] __alloc_pages_nodemask+0x1fd/0x790
>>>> Thats definitely a kernel issue.
>>>> Are you building your own kernel? That doesn't look like the default
>>>> Ubuntu kernel.
>>>> I would suggest to upgrade your kernel to 3.2.55 (of course use an
>>>> updated grsec patch as well). If that doesn't fix the issue, try
>>>> vanilla 3.2.55 (no grsec).
>>>> If the issue persists, report it upstream (either to lkml/netdev or
>>>> grsec, depending whether the vanilla 3.2.55 has the issue or not).
>>>> Regards,
>>>> Lukas
>>
>
>
>


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJTEJa1AAoJEOH/xsXYK8GtvyoQAJXsMyEVXbQWOaa+53MvmA1C
aNs4TruU/Qj3kUZweczH+E/61MWknY7otcOWXHNvrLJkdx2FiLbUSQw6RwnpYcpZ
l6qHBwwx029Al9MNn6uAcTbrAKghx/vgfjYxbtsmExMMbM/el/07GEp/jOMsi5zp
1pkSY9MjbqqlexjTmwKXxkPbp/kIROLRD9CNznCTO8L6j3OYES/b+k7nkXcNWZ6P
OnSswuGvcMNAQtNyzybel1I0nKn7wHfJsApaDlF5IkYXfBc2zotlAvYL1e54uYGx
CqZKpKBcNylzSpC/jFoOSn3ypL2CgJ3OttVeHDLSRPWIUkhrVSGgO2Kl43EhATA2
4mC/RRxOEthmtetsHP9RNU0Pe/igpy/D32o8pOG6E8NyiED9Z7ZfriOIHavoIsbo
FnQ8Lc/BgLYVrsRnbsYFBcv9ODI2D39ROu1Glqrf1jl/t1IkuWKtZQEuKDoQjaVd
khHk4lqpabO/4u13T78n6EoI0DRuUDst+eIsAOiG/5vTnZERGORyGzeXb6JI1V7G
xf6m5f92syA4dqSa7mmtjFxlTa5QaaQqup/kwEL1hjoB5vJyrVP81OCA9xGHnMFG
7OoEl3I1M1L5OJ8msIyA1uehMpbF7O/c8Snr5JY6AZ/X3c8L/vQHUTmlilf+QCmu
s54PVuLFtQlciQ87U7IR
=vU8c
-----END PGP SIGNATURE-----


[prev in list] [next in list] [prev in thread] [next in thread]