Hi Have you verified that your new VM host exposes the same cpu features?
If your haproxy binary is compiled expecting one set of features, it might not work well if that suddenly disappear. (for example if you moved from AMD to INTEL cpu, or your hypervisor exposes different CPU model) /Björn Zettergren On Mon, Mar 7, 2016 at 1:08 PM, SL <[email protected]> wrote: > Hi, > > I hope someone can offer some insight here, as I'm currently at a bit of a > loss, and our service is down. We are running HAproxy 1.6.1 on Debian 8 > virtuial machines. I was moving our 2 instances to a different size VM, > however, when I rebooted they did not come back up. > > I can't even run the haproxy binary file. Here's what I get when I try: > > ./haproxy > Illegal Instruction > > sudo ./haproxy > [no output] > > ./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!? > > Thank you! > > Scott >
