> On 6 Dec 2019, at 10:36, Sander Hoentjen <[email protected]> wrote: > > > On 12/6/19 10:20 AM, Pavlos Parissis wrote: >> On Παρασκευή, 6 Δεκεμβρίου 2019 9:23:24 Π.Μ. CET Sander Hoentjen wrote: >>> Hi list, >>> >>> After updating from 1.8.13 to 2.0.5 (also with 2.0.10) we are seeing >>> kernel panics on our production servers. I haven't been able to trigger >>> them on a test server, and we rollbacked haproxy to 1.8 for now. >>> >>> I am attaching a panic log, hope something useful is in there. >>> >>> Anybody an idea what might be going on here? >>> >> Have you noticed any high CPU utilization prior the panic? >> > Nothing out of the ordinary, but I have only minute data, so I don't know for > sure things about seconds before crash. > > Also of interest might be that at all the crashes I checked there were 2 > haproxy instances running. One of them has-sf <pid of the other>, so the > other is in "finishing mode". > >
Sander, can you try with “nosplice”? https://cbonte.github.io/haproxy-dconv/2.0/configuration.html#nosplice <https://cbonte.github.io/haproxy-dconv/2.0/configuration.html#nosplice> It should be enough to put in in “global” section. Kind regards, D. -- Dinko Korunic ** Standard disclaimer applies ** Sent from OSF1 osf1v4b V4.0 564 alpha
