I recompiled with explicit disabling threads: root@ubuntu-xenial:~/4/haproxy-1.8-rc1# ./haproxy -vv HA-Proxy version 1.8-rc1-901f75c 2017/10/31 Copyright 2000-2017 Willy Tarreau <[email protected]>
Build options : TARGET = linux2628 CPU = native CC = gcc CFLAGS = -O2 -march=native -g -fno-strict-aliasing -Wdeclaration-after-statement -fwrapv -Wno-unused-label OPTIONS = USE_LINUX_SPLICE=1 USE_LINUX_TPROXY=1 USE_LIBCRYPT=1 USE_THREAD=0 USE_OPENSSL=1 Problem persists. On Thu, Nov 2, 2017 at 8:52 PM, Lukas Tribus <[email protected]> wrote: > Hi, > > > 2017-11-02 14:33 GMT+01:00 Pavlos Parissis <[email protected]>: > > On 02/11/2017 02:24 μμ, Mihail Samoylov wrote: > >> Hi. > >> > >> I've tried 1.8-RC1 and in my case it ate 100% CPU and didn't work. I > found out that this is caused > >> by option httpchk. When I commented this line everything became fine. > Some details: > >> > > > > Willy mentioned in the announcement that checks ares broken, so the > behavior you observed is expected. > > Only when threads are enabled. Without threads, health checking works > fine in -rc1. > > Mihail are you sure you did not enable threads? > > > Lukas > -- С уважением, Михаил Самойлов телефон: +7-903-936-2664 электронная почта: [email protected]
