Will do but SSL is terminated before reaching HAProxy. Still possible it could affect us?
On Mon, Jul 18, 2016 at 4:55 PM, Pavlos Parissis <[email protected]> wrote: > On 18/07/2016 04:17 μμ, Michał Łowicki wrote: > > Hi, > > > > I'm using: > > > > HA-Proxy version 1.6.6 2016/06/26 > > Copyright 2000-2016 Willy Tarreau <[email protected] <mailto: > [email protected]>> > > > > > > on: > > > > cat /proc/version > > Linux version 4.5.0-0.bpo.1-amd64 ([email protected] > > <mailto:[email protected]>) (gcc version 4.9.2 (Debian > > 4.9.2-10) ) #1 SMP Debian 4.5.1-1~bpo8+1 (2016-04-20) > > > > and found core dump (using HAProxy through Marathon-lb > > <https://github.com/mesosphere/marathon-lb>): > > > > [New LWP 20445] > > Core was generated by `/bin/bash ./run'. > > Program terminated with signal SIGSEGV, Segmentation fault. > > #0 0x00000000004b8f97 in action_lookup (keywords=<error reading > variable: > > Cannot access memory at address 0xffffffffffffffe8>, > > kw=<error reading variable: Cannot access memory at address > > 0xffffffffffffffe0>) at include/proto/action.h:38 > > 38include/proto/action.h: No such file or directory. > > > > Is this a known issue or any clue how to debug it futher? > > > > > > Please try 1.6.7 version as it addresses a regression in 1.6.6 which > causes some > segfaults related to SSL config. > > Cheers, > Pavlos > > -- BR, Michał Łowicki
