Thanks for your help everyone. I've recompiled with the CPU=generic option, and it's all working again.
On 7 March 2016 at 13:37, SL <[email protected]> wrote: > Hi All, > > Thank you for your quick replies! (I'm grateful that HAproxy has such a > great community). > > >>> - native : use the build machine's specific processor optimizations. > Use with extreme care, and never in virtualized environments (known to > break) > > Yes, I believe I did originally compile with these options (oops). Will > recompile and report back. > > Thank you. > > On 7 March 2016 at 13:35, Lukas Tribus <[email protected]> wrote: > >> Hi SL, >> >> >> > ./haproxy -v >> > Illegal Instruction >> > >> > sudo/haproxy -v >> > [no output] >> > >> > Same thing if I try to check the config with -c -f (though I don't >> > think this is a config issue). >> > >> > Here's what I have in kern.log: >> > >> > Mar 7 11:41:41 rproxyws1 kernel: traps: haproxy[4031] trap invalid >> > opcode ip:4843a0 sp:7fff51856ac8 error:0 in haproxy[400000+cf000] >> > >> > One thing that does seem to have happened is a kernel update during the >> > move (from 4.1.5 to 4.4.0), but I've manually renerted to the old >> > kernel, but the new problems remain. >> > >> > Does anyone have any ideas!? >> >> Probably your new host has a different CPU than the CPU that >> haproxy was compiled with and CPU=native was used during >> the build. >> >> Compile with CPU=generic to avoid this. >> >> Compare /proc/cpuinfo output between the two hosts and >> check the build parameters with haproxy -vv. >> >> >> Also see README: >> - native : use the build machine's specific processor optimizations. >> Use with >> extreme care, and never in virtualized environments (known to break). >> >> >> Note that this only applies to the CPU parameter. Never set TARGET to >> generic. >> >> >> >> Regards, >> >> Lukas >> >> > > >
