Le 19/02/2020 à 11:35, Olivier D a écrit :
Hello,

I would like to report a segfault on HAProxy 2.0.11 ; this version has been running fine for two months, and this morning starting segfaulting over and over.
Mitigation was performed by adding "no option http-use-htx" on 'defaults' block.

I know it's not the latest version :) I'll update to 2.0.13 this evening.

Program terminated with signal 11, Segmentation fault.
#0  htx_sl_p2 (sl=<optimized out>) at include/common/htx.h:293
293     include/common/htx.h: No such file or directory.
(gdb) bt
#0  htx_sl_p2 (sl=<optimized out>) at include/common/htx.h:293
#1  htx_sl_req_uri (sl=<optimized out>) at include/common/htx.h:308
#2  assign_server (s=0xdc139f0) at src/backend.c:746
#3  0x0000000000552114 in assign_server_and_queue (s=s@entry=0xdc139f0) at src/backend.c:977 #4  0x00000000005556f8 in assign_server_and_queue (s=0xdc139f0) at src/backend.c:1772
#5  srv_redispatch_connect (s=s@entry=0xdc139f0) at src/backend.c:1705
#6  0x00000000004c2cf8 in sess_prepare_conn_req (s=<optimized out>) at src/stream.c:1250 #7  process_stream (t=t@entry=0xd1db790, context=0xdc139f0, state=<optimized out>) at src/stream.c:2414
#8  0x0000000000594865 in process_runnable_tasks () at src/task.c:412
#9  0x00000000005038f7 in run_poll_loop () at src/haproxy.c:2520
#10 run_thread_poll_loop (data=data@entry=0x0) at src/haproxy.c:2641
#11 0x00000000004653b0 in main (argc=<optimized out>, argv=0x7fff848ae498) at src/haproxy.c:3318



Config file is very long ... If needed, a coredump + binary can be sent on 
private.


Hi,

A bug was fixed in 2.0.12 that could explain such of crashes. The upstream commit id is eec7f8ac0 (or 0ed1e8963 in the 2.0 tree). It is related to the GitHub issue #420.

But I don't know if it is the same bug because I don't know how it is possible to apply an HTTP load-balancing algo on a TCP backend. I must take a look at your configuration. You can send it to me in private. Maybe I'll found something explaining your crashes.

Did you make any recent changes on HAproxy or your servers ? I'm surprised the segaults appear spontaneously after 2 months without any problem.


--
Christopher Faulet

Reply via email to