making a new reg-test to verify server-state-file, why does it fail at random places?

2018-09-13 Thread PiBa-NL
Hi List, I'm trying to make a reg-test to verify some behavior for server-state-file.. But i cant figure out why it fails at random places if ran like 10 times in a row, can someone provide a clue? I've tried playing with 'delay 0.1' settings in between commands.. but that doesn't fix all..

Re: TLS 1.3 options available with OpenSSL 1.1.1

2018-09-13 Thread Lukas Tribus
Hello Dirkjan, On Thu, 13 Sep 2018 at 16:44, Dirkjan Bussink wrote: > So with a new API call, does that mean adding for example a `ciphersuites` > option that works similar to `ciphers` today that it accepts a string and then > calls `SSL_CTX_set_ciphersuites`? Yes, that's what I'd have in

regtest lua/b00002.vtc fails with 1.9-dev2 / master

2018-09-13 Thread PiBa-NL
Hi List, Olivier, Just tried another run of regtests on FreeBSD, and found that lua/b2.vtc fails (coredump, gdb bt below) with todays snapshot: HA-Proxy version 1.9-dev2-253006d 2018/09/12 While on yesterday's snapshot it works properly, below some tests on different commits, and while

Re: TLS 1.3 options available with OpenSSL 1.1.1

2018-09-13 Thread Dirkjan Bussink
Hi Lukas, > On 13 Sep 2018, at 16:14, Lukas Tribus wrote: > > Definitely not some by string matching, openssl could have done > exactly that, they choose to make a new API call instead, and they > expect applications to introduce new configuration knobs or use the > generic configuration

Re: TLS 1.3 options available with OpenSSL 1.1.1

2018-09-13 Thread Lukas Tribus
Hi Dirkjan, On Thu, 13 Sep 2018 at 15:35, Dirkjan Bussink wrote: > > Hi all, > > With the release of OpenSSL 1.1.1, TLS 1.3 is now also available. It already > is working fine in my testing with HAProxy 1.8, there is however one issue. > Currently there is no way to control the ciphers for

TLS 1.3 options available with OpenSSL 1.1.1

2018-09-13 Thread Dirkjan Bussink
Hi all, With the release of OpenSSL 1.1.1, TLS 1.3 is now also available. It already is working fine in my testing with HAProxy 1.8, there is however one issue. Currently there is no way to control the ciphers for TLS 1.3 from HAProxy, as according to the OpenSSL documentation, ciphers are

Re: BUG: changed server IPs do not get restored from saved state

2018-09-13 Thread Peter Fröhlich
Am Do., 13. Sep. 2018 um 10:06 Uhr schrieb Willy Tarreau : > On Thu, Sep 13, 2018 at 09:29:42AM +0200, Peter Fröhlich wrote: > > Would our use case of setting the backend servers only through the socket, > > and the necessary workaround of setting the server entries to 'localhost' > > be worth a

[PATCH] DOC: Fix typos in lua documentation

2018-09-13 Thread Bertrand Jacquin
Hi, Please find attached a patch to fix some typos in the lua documentation. Cheers, -- BertrandFrom a8c24069246fc6ba6e9a956963158596ec4a0a3b Mon Sep 17 00:00:00 2001 From: Bertrand Jacquin Date: Mon, 10 Sep 2018 21:26:07 +0100 Subject: [PATCH] DOC: Fix typos in lua documentation ---

Re: [ANNOUNCE] haproxy-1.9-dev2

2018-09-13 Thread Aleksandar Lazic
Hi. Am 12.09.2018 um 19:11 schrieb Willy Tarreau: > Hi, > > HAProxy 1.9-dev2 was released on 2018/09/12. It added 199 new commits > after version 1.9-dev1. > > Let's be clear about this one : it's mostly aimed at developers to resync > their ongoing work. We've changed a number of pretty

Re: BUG: changed server IPs do not get restored from saved state

2018-09-13 Thread Willy Tarreau
On Thu, Sep 13, 2018 at 09:29:42AM +0200, Peter Fröhlich wrote: > Would our use case of setting the backend servers only through the socket, > and the necessary workaround of setting the server entries to 'localhost' > be worth a 'Notes:' entry in the 'load-server-state-from-file' section? Yes,

Re: BUG: changed server IPs do not get restored from saved state

2018-09-13 Thread Peter Fröhlich
On Thu, 13 Sep 2018, 07:52 Willy Tarreau, wrote: > On Wed, Sep 12, 2018 at 02:46:52PM +0200, Peter Fröhlich wrote: > > HAProxy does not restore the configured IP address present in the > > state file but falls back to the one in the config file at startup. > > Other information like uptime