CI question related to openssl matrix

2019-05-08 Thread Илья Шипицин
Hello, does haproxy have some issues when it is built using openssl-1.1.0 and running with openssl-1.1.1, for example ? should we consider such situations in travis-ci openssl matrix ? thanks! Ilya Shipitsin

[PATCH] BUILD: add BoringSSL to travis-ci build matrix

2019-05-08 Thread chipitsine
From: Ilya Shipitsin --- .travis.yml | 3 +++ scripts/build-ssl.sh | 19 +++ 2 files changed, 22 insertions(+) diff --git a/.travis.yml b/.travis.yml index f9a13586..c00725d8 100644 --- a/.travis.yml +++ b/.travis.yml @@ -44,6 +44,9 @@ matrix: - os: linux

RE: cygwin compilation error

2019-05-08 Thread Zakharychev, Bob
Ilya Shipitsin wrote on Wed, 08 May 2019 03:22:20 -0700: >I guess the same would be with BoringSSL. It exposes OPENSSL_VERSION_NUMBER >and it is not openssl itself. > >yes, we can add warning. I wouldn't bother even trying to add support for BoringSSL - they themselves discourage people from

unsubscribe

2019-05-08 Thread Piotr Rybicki

Link error building haproxy-1.9.7

2019-05-08 Thread Chris Packham
Hi, I'm encountering the following linker error when building haproxy-1.9.7 make CC=arm-softfloat-linux-gnueabi USE_OPENSSL=1 ... LD haproxy /usr/bin/../lib/gcc/arm-softfloat-linux-gnueabi/8.3.0/../../../../arm-softfloat-linux-gnueabi/bin/ld: src/fd.o: in function

[PATCH] BUILD: common: Add __ha_cas_dw fallback for single threaded builds

2019-05-08 Thread Chris Packham
__ha_cas_dw() is used in fd_rm_from_fd_list() and when built without USE_THREADS=1 the linker fails to find __ha_cas_dw(). Add a definition of __ha_cas_dw() for the #ifndef USE_THREADS case. Signed-off-by: Chris Packham --- include/common/hathreads.h | 5 + 1 file changed, 5 insertions(+)

Re: [PATCH v2 1/2] MINOR: systemd: Use the variables from /etc/default/haproxy

2019-05-08 Thread Vincent Bernat
❦ 8 mai 2019 16:23 +02, Tim Düsterhus : >> I think, instead of After=rsyslog.service, it should be >> After=syslog.service, then any logger daemon could be used that has >> Alias=syslog.service. >> >> https://www.freedesktop.org/wiki/Software/systemd/syslog/ >> > > The HAProxy provided unit

Re: cygwin compilation error

2019-05-08 Thread Илья Шипицин
ср, 8 мая 2019 г. в 11:06, Willy Tarreau : > On Wed, May 08, 2019 at 10:59:20AM +0500, ??? wrote: > > travis-ci supports windows builds. > > cool! > my current roadmap is 1) patch fixes SSL variants (already sent to list). without it we are NOT building LibreSSL at all (i.e. we use

Re: cygwin compilation error

2019-05-08 Thread Илья Шипицин
small fix ср, 8 мая 2019 г. в 11:12, Willy Tarreau : > On Wed, May 08, 2019 at 11:09:04AM +0500, ??? wrote: > > ??, 8 ??? 2019 ?. ? 11:06, Willy Tarreau : > > > > > On Wed, May 08, 2019 at 10:59:20AM +0500, ??? wrote: > > > > travis-ci supports windows builds. > > > > > > cool!

Re: cygwin compilation error

2019-05-08 Thread Илья Шипицин
travis-ci supports windows builds. I will add such build a bit later (after we settle with current travis-ci fixes) ср, 8 мая 2019 г. в 10:52, Willy Tarreau : > Hi, > > On Mon, May 06, 2019 at 12:54:47PM +0300, Gil Bahat wrote: > > Hi, > > > > is cygwin still supported anymore? > > Well, we

Re: cygwin compilation error

2019-05-08 Thread Илья Шипицин
I messed up with commit message. One more try ср, 8 мая 2019 г. в 11:33, Илья Шипицин : > small fix > > ср, 8 мая 2019 г. в 11:12, Willy Tarreau : > >> On Wed, May 08, 2019 at 11:09:04AM +0500, ??? wrote: >> > ??, 8 ??? 2019 ?. ? 11:06, Willy Tarreau : >> > >> > > On Wed, May 08, 2019

Re: cygwin compilation error

2019-05-08 Thread Willy Tarreau
On Wed, May 08, 2019 at 10:59:20AM +0500, ??? wrote: > travis-ci supports windows builds. cool! > I will add such build a bit later (after > we settle with current travis-ci fixes) ...and this cygwin build issue :-) Willy

Re: haproxy 2.0 docker images

2019-05-08 Thread Willy Tarreau
Hi Aleks, On Mon, May 06, 2019 at 08:17:23AM +0200, Aleksandar Lazic wrote: > > The outputs below raises some questions to me. > > > > * Should in the OPTIONS output also be the EXTRA_OBJS ? That's a good question. I was hesitating but given that the goal is to be able to easily rebuild a

Re: cygwin compilation error

2019-05-08 Thread Willy Tarreau
On Wed, May 08, 2019 at 11:09:04AM +0500, ??? wrote: > ??, 8 ??? 2019 ?. ? 11:06, Willy Tarreau : > > > On Wed, May 08, 2019 at 10:59:20AM +0500, ??? wrote: > > > travis-ci supports windows builds. > > > > cool! > > > > my current roadmap is > > 1) patch fixes SSL variants

Re: [PATCH 1/1] BUILD: travis-ci bugfixes and improvements

2019-05-08 Thread Willy Tarreau
On Tue, May 07, 2019 at 01:42:43AM +0500, chipits...@gmail.com wrote: > From: Ilya Shipitsin > > Call missing scripts/build-ssl.sh (which actually builds SSL variants) > Enable OpenSSL, LibreSSL builds caching, it saves a bunch of time > LibreSSL builds are not allowed to fail anymore > Add

Re: haproxy-1.9 sanitizers finding

2019-05-08 Thread Илья Шипицин
I would like to run sanitizers before new 1.9 release is out On Wed, May 8, 2019, 10:54 AM Willy Tarreau wrote: > Hi Ilya, > > On Tue, May 07, 2019 at 11:47:54AM +0500, ??? wrote: > > Hello, > > > > when running regtests against 1.9 branch there are findings (not seen in > > master

Re: cygwin compilation error

2019-05-08 Thread Willy Tarreau
Hi Ilya, On Wed, May 08, 2019 at 11:34:57AM +0500, ??? wrote: > From ad9961e92c692430272c9088a49759c889dac6f1 Mon Sep 17 00:00:00 2001 > From: Ilya Shipitsin > Date: Wed, 8 May 2019 11:32:02 +0500 > Subject: [PATCH] BUILD: do not use "RAND_keep_random_devices_open" when > building

Re: cygwin compilation error

2019-05-08 Thread Илья Шипицин
Frederic, can you help with some "haproxy reg test getting started" doc ? ср, 8 мая 2019 г. в 13:13, Илья Шипицин : > > > ср, 8 мая 2019 г. в 13:03, Willy Tarreau : > >> Hi Ilya, >> >> On Wed, May 08, 2019 at 11:34:57AM +0500, ??? wrote: >> > From

Re: cygwin compilation error

2019-05-08 Thread Илья Шипицин
ср, 8 мая 2019 г. в 13:03, Willy Tarreau : > Hi Ilya, > > On Wed, May 08, 2019 at 11:34:57AM +0500, ??? wrote: > > From ad9961e92c692430272c9088a49759c889dac6f1 Mon Sep 17 00:00:00 2001 > > From: Ilya Shipitsin > > Date: Wed, 8 May 2019 11:32:02 +0500 > > Subject: [PATCH] BUILD: do not

Re: cygwin compilation error

2019-05-08 Thread Willy Tarreau
On Wed, May 08, 2019 at 01:13:56PM +0500, ??? wrote: > > libressl ? My understanding of this thing is that this problem is not > > easy to detect by accident and causes a mess for people who reload often. > > If libressl is affected by this we probably need to find a different > > fix.

Re: cygwin compilation error

2019-05-08 Thread Илья Шипицин
ср, 8 мая 2019 г. в 13:55, Willy Tarreau : > On Wed, May 08, 2019 at 01:13:56PM +0500, ??? wrote: > > > libressl ? My understanding of this thing is that this problem is not > > > easy to detect by accident and causes a mess for people who reload > often. > > > If libressl is affected by

Re: cygwin compilation error

2019-05-08 Thread Willy Tarreau
On Wed, May 08, 2019 at 02:06:31PM +0500, ??? wrote: > > Ilya, could you please instead change the test like this and test again : > > > > -#if defined(USE_OPENSSL) && (OPENSSL_VERSION_NUMBER >= 0x10101000L) > > +#if defined(USE_OPENSSL) && (OPENSSL_VERSION_NUMBER >= 0x1010100fL) > > > >

Re: [1.9 HEAD] HAProxy using 100% CPU

2019-05-08 Thread Willy Tarreau
On Wed, May 08, 2019 at 03:03:23PM +0200, Olivier Houchard wrote: > > > I can't seem to remember :) > > > > Given the number of bugs we've dealt with in the last few weeks, you're > > forgiven :-) > > > > I'm afraid I'm getting old :/ Ah! you see how it feels! > > > I think that patch is safe

Re: [1.9 HEAD] HAProxy using 100% CPU

2019-05-08 Thread Maciej Zdeb
Ok, thanks! śr., 8.05.2019, 16:50 użytkownik Willy Tarreau napisał: > On Wed, May 08, 2019 at 04:48:55PM +0200, Maciej Zdeb wrote: > > I'll gladly test Olivier patch after backporting. :) > > Thank you Maciej. I still have other stuff to deal with before going back > to the pending 1.9

Re: [1.9 HEAD] HAProxy using 100% CPU

2019-05-08 Thread Willy Tarreau
On Wed, May 08, 2019 at 01:56:05PM +0200, Olivier Houchard wrote: > > > One of processes stuck in infinite loop, admin socket is not responsive so > > > I've got information only from gdb: > > > > > > 0x00484ab8 in h2_process_mux (h2c=0x2e8ff30) at src/mux_h2.c:2589 > > > 2589

Re: [1.9 HEAD] HAProxy using 100% CPU

2019-05-08 Thread Olivier Houchard
Hi, On Wed, May 08, 2019 at 07:11:27AM +0200, Willy Tarreau wrote: > Hi Maciej, > > On Tue, May 07, 2019 at 07:08:47PM +0200, Maciej Zdeb wrote: > > Hi, > > > > I've got another bug with 100% CPU on HAProxy process, it is built from > > HEAD of 1.9 branch. > > > > One of processes stuck in

Re: [PATCH v2 1/2] MINOR: systemd: Use the variables from /etc/default/haproxy

2019-05-08 Thread Tim Düsterhus
Veiko, Am 08.05.19 um 15:44 schrieb Veiko Kukk: > I think, instead of After=rsyslog.service, it should be > After=syslog.service, then any logger daemon could be used that has > Alias=syslog.service. > > https://www.freedesktop.org/wiki/Software/systemd/syslog/ > The HAProxy provided unit file

Re: [1.9 HEAD] HAProxy using 100% CPU

2019-05-08 Thread Olivier Houchard
On Wed, May 08, 2019 at 02:30:07PM +0200, Willy Tarreau wrote: > On Wed, May 08, 2019 at 01:56:05PM +0200, Olivier Houchard wrote: > > > > One of processes stuck in infinite loop, admin socket is not responsive > > > > so > > > > I've got information only from gdb: > > > > > > > >

Re: cygwin compilation error

2019-05-08 Thread Илья Шипицин
ср, 8 мая 2019 г. в 14:50, Willy Tarreau : > On Wed, May 08, 2019 at 02:06:31PM +0500, ??? wrote: > > > Ilya, could you please instead change the test like this and test > again : > > > > > > -#if defined(USE_OPENSSL) && (OPENSSL_VERSION_NUMBER >= 0x10101000L) > > > +#if

Re: [1.9 HEAD] HAProxy using 100% CPU

2019-05-08 Thread Maciej Zdeb
I'll gladly test Olivier patch after backporting. :) śr., 8.05.2019, 15:29 użytkownik Willy Tarreau napisał: > On Wed, May 08, 2019 at 03:03:23PM +0200, Olivier Houchard wrote: > > > > I can't seem to remember :) > > > > > > Given the number of bugs we've dealt with in the last few weeks,

Re: [PATCH v2 1/2] MINOR: systemd: Use the variables from /etc/default/haproxy

2019-05-08 Thread Veiko Kukk
On 2019-05-06 11:00, Tim Duesterhus wrote: From: Apollon Oikonomopoulos This will allow seamless upgrades from the sysvinit system while respecting any changes the users may have made. It will also make local configuration easier than overriding the systemd unit file. Note by Tim: This