Re: dns fails to process response / hold valid? (since commit 2.2-dev0-13a9232)

ge in behaviour)..) Anyhow the current '2.2-dev2-a71667c, released 2020/02/17' is still affected. If someone was already planning to, please don't feel 'pushed' by this mail. i'm just trying to make sure this doesn't fall through the cracks :). Regards, PiBa-N

Re: dns fails to process response / hold valid? (since commit 2.2-dev0-13a9232)

lto:bed...@gmail.com>> wrote: Hi guys, Thx Tim for investigating. I'll check the PCAP and see why such behavior happens. Baptiste On Tue, Feb 18, 2020 at 12:09 AM Tim Düsterhus mailto:t...@bastelstu.be>> wrote: Pieter, Am 09.02.20 um 15

commit 493d9dc makes a SVN-checkout stall..

7;t change anything. Hope you have an idea where to look. Providing captures/logs is a bit difficult without some careful scrubbing.. Regards, PiBa-NL (Pieter) ### Complete config (that still reproduces the issue.. things cant get much simpler than this..): frontend InternalSites.8.6-merged   

Re: commit 493d9dc makes a SVN-checkout stall..

Hi Olivier, Willy, Just to confirm, as expected it (c3500c3) indeed works for me :). Thanks for the quick fix! Regards, PiBa-NL (Pieter) Op 25-3-2020 om 17:16 schreef Willy Tarreau: On Wed, Mar 25, 2020 at 05:08:03PM +0100, Olivier Houchard wrote: That is... interesting, not sure I reached

Re: [PATCHES] dns related

this one. Question though, are you still working on making a non-existing server template go into 'resolution' state? See below/attached picture with some details.. (or see https://www.mail-archive.com/haproxy@formilux.org/msg36373.html ) Regards, PiBa-NL (Pieter)

server-state application failed for server 'x/y', invalid srv_admin_state value '32'

2 servers of x2 are up, and the 3rd is in resolution state, it shouldn't warn on a restart imho as its to be expected for most setups.?. Not sure if its a bug or a feature request, but i do think it should be changed :). Can it be added to some todo list? Thanks. Thanks and regards, PiBa-NL (Pieter)

Re: server-state application failed for server 'x/y', invalid srv_admin_state value '32'

ithub issue and tag me in there? Done: https://github.com/haproxy/haproxy/issues/576 Baptiste Thanks and regards, PiBa-NL (Pieter)

Re: disabling test if ipv6 not supported ?

idea how we can skip such tests ? I think the test or code should get fixed.. not skipped because it fails. Note that this specific test recently got this extra 'addr ::1' server check parameter on srv3. Perhaps that that syntax is written/parsed wrongly? Cheers, Ilya Shipitcin R

haproxy 2.2-dev8-7867525 - 100% cpu usage on 1 core after config 'reload'

ake a closer look.? If more info is needed ill try and provide :). Regards, PiBa-NL (Pieter) *Reproduction (works 99% of the time..):*   haproxy -W -f /var/etc/haproxy-2020/haproxy.cfg   kill -s USR2 17683 *haproxy.cfg* frontend www     bind            127.0.0.1:81     mode            http backend

Re: haproxy 2.2-dev8-7867525 - 100% cpu usage on 1 core after config 'reload'

Hi Christopher, Op 29-5-2020 om 09:00 schreef Christopher Faulet: Le 29/05/2020 à 00:45, PiBa-NL a écrit : Hi List, I noticed a issue with 2.2-dev8-release and with 2.2-dev8-7867525 the issue is still there that when a reload is 'requested' it fails to stop the old worker.. Hi

Re: set ssl ocsp-response working only if we already have an ocsp record

the admin socket. Assuming you do know in advance that you will want to use ocsp.. Regards PiBa-NL

Re: dual check

caciones* Servicio Andaluz de Salud. Consejería de Salud de la Junta de Andalucía _antonio.trujillo.sspa@juntadeandalucia.es_ Tel. +34 670947670 747670) Also i dont get how a healthcheck settings would be relevant to get session affinity? Regards, PiBa-NL

Re: ssl & default_backend

nceador-SSL There is no acl for the backend above? so probably the default_backend below will never be reached. Could it be the above backend returns the 404 your seeing? default_backend CitrixSF-SSL Regards, PiBa-NL

Re: Need to understand logs

ration.html#8 Maybe you have activated http://cbonte.github.io/haproxy-dconv/1.7/configuration.html#4.2-optio n%20log-health-checks in your config. It would be nice to know which haproxy version you use. haproxy -vv -- Best Regards Aleks https://www.me2digital.com/ -- Best Regards Aleks Regards, PiBa-NL

Re: confusion regarding usage of haproxy for large number of connections

0.5:9876 <http://192.168.0.5:9876>  maxconn 2000 With this configuration can i undergo my setup with 8000 connection load distribution or do i have to undergo some changes here Thanks, Kushal Add a 'maxconn 8000' in 'global' section? Regards, PiBa-NL

HAProxy 1.7.9 FreeBSD 100% CPU usage

The LetsEncrypt backend that is part of the configuration never got a single request according to stats.. Is it a known issue? Are tcpdump/truss output desired ..? (where should i send em?) Is there any other output that can try to gather next time? Regards, PiBa-NL HA-Proxy version 1.7.9 2017

Re: HAProxy 1.7.9 FreeBSD 100% CPU usage

Hi Willy, Op 9-11-2017 om 5:45 schreef Willy Tarreau: Hi Pieter, On Thu, Nov 09, 2017 at 02:28:46AM +0100, PiBa-NL wrote: Actually haproxy has been running for a few weeks with 100% and i didnt notice.. it does keep working it seems.. Anyhow thought i would try and capture the next event if

Re: HAProxy 1.7.9 FreeBSD 100% CPU usage

haproxy-ss PORTVERSION=    20171017 CATEGORIES=    net www MASTER_SITES=    http://www.haproxy.org/download/1.7/src/snapshot/ And then ran:     make clean build install NO_CHECKSUM=yes Which did 'seem' to download the 'intended?' file.. Thanks, PiBa-NL / Pieter

Re: HAProxy 1.7.9 FreeBSD 100% CPU usage

g with haproxy-ss-20171017 for a day now. Sofar it sticks to <1% cpu usage. Will report if anything changes, cant tell for sure as don't have a clear reproduction of the issue, but my issue 'seems' fixed. Regards, PiBa-NL / Pieter

haproxy-1.8-rc4 - FreeBSD 11.1 - build error: undefined reference, plock.h __unsupported_argument_size_for_pl_try_s__

nything?.. With those lines removed i get the result below from haproxy -vv, looks good :) but i didn't actually start it yet with a proper config. Regards, PiBa-NL / Pieter root@:/usr/ports/net/haproxy-devel # haproxy -vv HA-Proxy version 1.8-rc4-cfe1466 2017/11/19 Copyright 2000-2

Re: haproxy-1.8-rc4 - FreeBSD 11.1 - build error: undefined reference, plock.h __unsupported_argument_size_for_pl_try_s__

uot;WITH_DEBUG=yes" strips the -O2 away and makes it a -g and thus 'changing' the way the compiler works. Without this flags it indeed builds without issue. But any future gdb session wouldn't have symbols.. Thanks, PiBa-NL / Pieter p.s. Not sure if it still matters bu

Re: haproxy-1.8-rc4 - FreeBSD 11.1 - master-worker daemon mode does not bind.?.

xJk9n-mD7vv/vQe/Pj33VRqdju https://0bin.net/paste/sJ955XNt2hE1a9mF#xsMP2tzydlK3BVpxo2nNRl878SRbxZNAUpRw5-YhwdM Op 20-11-2017 om 1:47 schreef PiBa-NL: Hi List, After compiling haproxy 1.8-rc4 (without modifications) on FreeBSD11.1 i'm trying to run it with master-worker option. I can run i

Re: haproxy-1.8-rc4 - FreeBSD 11.1 - master-worker daemon mode does not bind.?.

Hi Willy, Op 20-11-2017 om 21:46 schreef Willy Tarreau: Hi Pieter, On Mon, Nov 20, 2017 at 01:47:48AM +0100, PiBa-NL wrote: Hmmm thinking about it there might be something. Could you start with "-dk" to disable kqueue and fall back to poll ? kqueue registers a post- fork function to

Re: haproxy-1.8-rc4 - FreeBSD 11.1 - master-worker daemon mode does not bind.?.

testedit and it may even break epoll, but one thing at a time :-) Thanks, Willy You patch fixes the issue. If you've got a definitive patch lemme know. Thanks, PiBa-NL

haproxy-1.8-rc4 - FreeBSD 11.1 - master-worker daemon parent staying alive/process-owner

when starting haproxy with -sf it would tell if the (original?) master was successful in reloading the config / starting new workers or how should this be done? Currently a whole new set of master-worker processes seems to be take over.. Or am i taking the wrong approach here? Regards, PiBa-NL

Re: 4xx statistics made useless through health checks?

:) Daniel Regards, PiBa-NL / Pieter

Re: haproxy-1.8-rc4 - FreeBSD 11.1 - master-worker daemon parent staying alive/process-owner

new master-worker with -sf, it's not supposed to be used that way but it should work too if you don't mind having a new PID. I kinda expected this to indeed be 'as intended' -sf will fully replace the old processes. Thanks for your reply. Regards, PiBa-NL / Pieter

Re: haproxy-1.8-rc4 - FreeBSD 11.1 - master-worker daemon parent staying alive/process-owner

eds. Could you check? Regards, PiBa-NL #!/usr/local/bin/php-cgi -f    0 => array("pipe", "r"),  // stdin is a pipe that the child will read from    1 => array("pipe", "w"),  // stdout is a pipe that the child will write to    2 => array("

Re: haproxy-1.8-rc4 - FreeBSD 11.1 - master-worker daemon parent staying alive/process-owner

mmediately everything stops running.. Anyhow looking forward to your replies. Regards, PiBa-NL Op 22-11-2017 om 17:48 schreef PiBa-NL: Hi William, I'm not 100% sure but i think the stdout and errout files should be closed before process exit? It seems to me they are not. At least with th

Re: haproxy-1.8-rc4 - FreeBSD 11.1 - master-worker daemon mode does not bind.?.

orker. So no problem or missing advantages for myself or users of that package if haproxy 1.8 gets released as it currently is. I'm not sure if other folks are using some service management tool like systemd on FreeBSD... But i guess time will tell, i'm sure 1.8 wont be the last release ever so fixes when required will come :). Regards, PiBa-NL / Pieter

Re: haproxy-1.8-rc4 - FreeBSD 11.1 - master-worker daemon parent staying alive/process-owner

Hi Willy, Op 25-11-2017 om 8:33 schreef Willy Tarreau: Hi Pieter, On Tue, Nov 21, 2017 at 04:34:16PM +0100, PiBa-NL wrote: Hi William, I was intending to use the new feature to pass open sockets to the next haproxy process. And thought that master-worker is a 'requirement' to make

haproxy-1.8.0, sending a email-alert causes 100% cpu usage, FreeBSD 11.1

g to send a mail for that.. that never seems to happen though.. no mail is received. I tried using nokqueu and nopoll, but that did not result in any improvement.. Anything else i can provide? Regards, PiBa-NL / Pieter haproxy -f /root/hap.conf -V [WARNING] 330/204605 (14771) : config : missing

Re: haproxy-1.8.0, sending a email-alert causes 100% cpu usage, FreeBSD 11.1

Hi Christopher / Willy, On Tue, Nov 28, 2017 at 10:28:20AM +0100, Christopher Faulet wrote: Here is a patch that should fix the deadlock. Could you confirm it fixes your bug ? Fix confirmed. Thanks, PiBa-NL / Pieter

[PATCH] BUG/MINOR: Check if master-worker pipe getenv succeeded, also allow pipe fd 0 as valid.

ntinues and tries to use it? - wont the rd wr char* values leak memory? Anyhow the biggest part that should be noticed of the bug is the sometimes wrongful alert when the fd is actually '0'... If anything needs to be changed let me know. Regards, PiBa-NL / Pieter From 486d7c759af03f

[PATCH] BUG/MINOR: when master-worker is in daemon mode, detach from tty

intended to solve my previously reported 'issue' : https://www.mail-archive.com/haproxy@formilux.org/msg27963.html Let me know if something about it needs fixing.. Thanks PiBa-NL / Pieter From 06224a3fcf7b39bf1bf0128a5bac3d0209bc2aab Mon Sep 17 00:00:00 2001 From: PiBa-NL Date: Tue, 2

Re: [PATCH] BUG/MINOR: Check if master-worker pipe getenv succeeded, also allow pipe fd 0 as valid.

in()] Cannot create master pipe.\n", argv[0]); exit(1); } This code will guarantee that the whole master-worker quit if there is a problem. Thanks for the review, new patch attached that basically incorporates all your comments. Regards, PiB

Re: [PATCH] BUG/MINOR: when master-worker is in daemon mode, detach from tty

do not 'need' the feature urgently or perhaps won't need it at all.. Anyhow when you have time to look into it, i look forward to your feedback :) . Thanks in advance. Regards, PiBa-NL / Pieter From c103dbd7837d49721ccadfb1aee9520e821a020f Mon Sep 17 00:00:00 2001 From: PiBa

haproxy 1.8.1 email-alert with log-health-checks, 100% cpu usage / mailbomb

e any bind's then..) If a mailserver is listening, then 800+ mails are received.. Regards, PiBa-NL / Pieter defaults     option log-health-checks listen HAProxyLocalStats     bind 127.0.0.1:42200 name localstats     mode http     stats enable mailers globalmailers     mailer ex01 127.0.0.1:33

[PATCH] BUG/MEDIUM: email-alert: don't set server check status from a email-alert task

/msg28158.html Please let me know if it is OK, or should be done differently. Thanks in advance, PiBa-NL / Pieter From bf80b0398c08f94bebec30feaaddda422cb87ba1 Mon Sep 17 00:00:00 2001 From: PiBa-NL Date: Wed, 6 Dec 2017 01:35:43 +0100 Subject: [PATCH] BUG/MEDIUM: email-alert: don't set server

crash with regtest: /reg-tests/connection/h00001.vtc after commit f157384

Hi List, Willy, Current 1.9-dev master ( 6e0d8ae ) crashes with regtest: /reg-tests/connection/h1.vtc stack below, it fails after commit f157384. Can someone check? Thanks. Regards, PiBa-NL (Pieter) Program terminated with signal 11, Segmentation fault. #0  0x0057f34f in

stdout logging makes syslog logging fail.. 1.9-dev10-6e0d8ae

operation on non-socket (errno=38), which apparently modifies the syslog behavior.? Tested with version 1.9-dev10-6e0d8ae, but i think it never worked since stdout logging was introduced. Regards, PiBa-NL (Pieter) # commit d02286d # BUG/MINOR: log: pin the front connection when front ip/ports

Re: Quick update on 1.9

atures that used to work. So even current new commits are still introducing new breakage, while shortly before release i would expect mostly little fixes to issues to get committed. That 'new' features arn't 100% stable, that might not be a blocker. But existing features that used to work properly should imho not get released in a broken state.. my 2 cent. Regards, PiBa-NL (Pieter)

Re: Quick update on 1.9

atest commit and the .vtc file still produces files with different hashes for the 3 curl commands for me. Besides that and as usual thanks for your elaborate response on all the other subjects :). Regards, PiBa-NL (Pieter)

regtests - with option http-use-htx

ype: ip, size:1024, used:(0|1\n0x[0-9a-f]*: key=127\.0\.0\.1 use=0 exp=[0-9]* gpt0=0 gpc0=0 gpc0_rate\(1\)=0 conn_rate\(1\)=1 http_req_cnt=1 http_req_rate\(1\)=1 http_err_cnt=0 http_err_rate\(1\)=0)\n$" Regards, PiBa-NL (Pieter) #commit b406b87 # BUG/MEDIUM: connection: do

Re: regtests - with option http-use-htx

Hi Willy, Op 15-12-2018 om 17:06 schreef Willy Tarreau: Hi Pieter, On Sat, Dec 15, 2018 at 04:52:10PM +0100, PiBa-NL wrote: Hi List, Willy, Trying to run some existing regtests with added option: option http-use-htx Using: HA-Proxy version 1.9-dev10-c11ec4a 2018/12/15 I get the below issues

Re: corruption of data with compression in 1.9-dev10

Hi Christopher, Fix confirmed. top   2.5 shell_out|File1 all OK top   2.5 shell_out|File2 all OK top   2.5 shell_out|File3 all OK Thank you! Regards, PiBa-NL (Pieter)

d94f877 causes timeout in a basic connection test 1.9-dev11_d94f877

./PB-TEST/basic_connection.vtc FAILED (120.236) signal=9 Please can you take a look :) Thanks in advance. Regards, PiBa-NL (Pieter) # Checks a simple request varnishtest "Checks a simple request" feature ignore_unknown_macro server s1 { rxreq txresp -bodylen 42202 } -start haproxy h1 -conf

[PATCH] REG-TEST: mailers: add new test for 'mailers' section

6/1.7/1.8 but can be 'fixed' there by adding a 'timeout mail 200ms'.. (except on 1.6 which doesn't have that setting.) I don't think that should be needed though if everything was working properly? If the test could be committed, and related issues exposed fixed th

[PATCH] REGTEST: filters: add compression test

bigger? As you mentioned needing a 10MB output to reproduce the original issue on your machine? Regards, PiBa-NL (Pieter) From 64460dfeacef3d04af4243396007a606c2e5dbf7 Mon Sep 17 00:00:00 2001 From: PiBa-NL Date: Sun, 23 Dec 2018 21:21:51 +0100 Subject: [PATCH] REGTEST: filters: add compression

Re: [PATCH] REG-TEST: mailers: add new test for 'mailers' section

Changed subject of patch requirement to 'REGTEST'. Op 23-12-2018 om 21:17 schreef PiBa-NL: Hi List, Attached a new test to verify that the 'mailers' section is working properly. Currently with 1.9 the mailers sends thousands of mails for my setup... As the test is rathe

Re: [PATCH] REGTEST: filters: add compression test

Added LUA requirement into the test.. Op 23-12-2018 om 23:05 schreef PiBa-NL: Hi Frederic, As requested hereby the regtest send for inclusion into the git repository. Without randomization and with your .diff applied. Also outputting expected and actual checksum if the test fails so its

htx with compression issue, "Gunzip error: Body lacks gzip magics"

match **   c1    0.1 === expect resp.http.content-encoding == "gzip" c1    0.1 EXPECT resp.http.content-encoding (gzip) == "gzip" match **   c1    0.1 === gunzip c1    0.1 Gunzip error: Body lacks gzip magics Can someone take a look? Thanks in advance. Regards, PiBa-NL

Re: htx with compression issue, "Gunzip error: Body lacks gzip magics"

Hi Christopher, Willy, Op 2-1-2019 om 15:37 schreef Christopher Faulet: Le 29/12/2018 à 01:29, PiBa-NL a écrit : compression with htx, and a slightly delayed body content it will prefix some rubbish and corrupt the gzip header.. Hi Pieter, In fact, It is not a bug related to the compression

compression in defaults happens twice with 1.9.0

in advance. Regards, PiBa-NL (Pieter) s1    0.0 txresp|!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_ s1    0.0 txresp|"#$%&'()*+,-./0123456789:;<=>?@ABCD ***  s1    0.0 shutting fd 4 **   s1    0.0 Ending ***  h1    0.0 debug

Re: [PATCH] REG-TEST: mailers: add new test for 'mailers' section

kay. Just making sure it aint forgotten about :). The 23654 mails received for a failed server is a bit much.. c2    7.5 EXPECT resp.http.mailsreceived (23654) == "16" failed Regards, PiBa-NL (Pieter) Op 23-12-2018 om 23:37 schreef PiBa-NL: Changed subject of patch requireme

Re: [PATCH] REG-TEST: mailers: add new test for 'mailers' section

Hi Willy, Op 7-1-2019 om 15:25 schreef Willy Tarreau: Hi Pieter, On Sun, Jan 06, 2019 at 04:38:21PM +0100, PiBa-NL wrote: The 23654 mails received for a failed server is a bit much.. I agree. I really don't know much how the mails work to be honest, as I have never used them. I remember

Re: compression in defaults happens twice with 1.9.0

Hi Christopher, Op 7-1-2019 om 16:32 schreef Christopher Faulet: Le 06/01/2019 à 16:22, PiBa-NL a écrit : Hi List, Using both 1.9.0 and 2.0-dev0-909b9d8 compression happens twice when configured in defaults. This was noticed by user walle303 on IRC. Seems like a bug to me as 1.8.14 does not

Re: regtests - with option http-use-htx

Hi Frederic, Op 8-1-2019 om 16:27 schreef Frederic Lecaille: On 12/15/18 4:52 PM, PiBa-NL wrote: Hi List, Willy, Trying to run some existing regtests with added option: option http-use-htx Using: HA-Proxy version 1.9-dev10-c11ec4a 2018/12/15 I get the below issues sofar: based on

Re: [PATCH] REGTEST: filters: add compression test

Hi Frederic, Op 7-1-2019 om 10:13 schreef Frederic Lecaille: On 12/23/18 11:38 PM, PiBa-NL wrote: As requested hereby the regtest send for inclusion into the git repository. It is OK like that. Note that you patch do not add reg-test/filters/common.pem which could be a symlink to ../ssl

coredump in h2_process_mux with 1.9.0-8223050

the moment, lets see if something strange happens again. Might take a few days though, IF it still occurs.. Regards, PiBa-NL (Pieter) Core was generated by `/usr/local/sbin/haproxy -f /var/etc/haproxy/haproxy.cfg -p /var/run/haproxy.pid'. Program terminated with signal SIGSEGV, Segmentation

Re: [PATCH] REGTEST: filters: add compression test

Thank you Christopher & Frederic. Op 9-1-2019 om 14:47 schreef Christopher Faulet: Le 09/01/2019 à 10:43, Frederic Lecaille a écrit : On 1/8/19 11:25 PM, PiBa-NL wrote: Hi Frederic, Hi Pieter, Op 7-1-2019 om 10:13 schreef Frederic Lecaille: On 12/23/18 11:38 PM, PiBa-NL wrote:

Re: Lots of mail from email alert on 1.9.x

0.html a 'regtest' is added in that mail thread also to aid developers in reproducing the issue and validating a possible fix. @Olivier, Willy, may i assume this mailbomb feature is 'planned' to get fixed in 1.9.2 ? (perhaps a bugtracker with a 'target version' would be nice ;) ?) Regards, PiBa-NL (Pieter)

Re: Lots of mail from email alert on 1.9.x

after 11 seconds.. So i guess the patch needs a bit more tweaking. Regards, PiBa-NL (Pieter) Core was generated by `haproxy -d -f /tmp/vtc.37274.4b8a1a3a/h1/cfg'. Program terminated with signal SIGSEGV, Segmentation fault. #0  0x00500955 in chk_report_conn_err (check=0x802616a10, err

Re: Lots of mail from email alert on 1.9.x

the server i took out to test has a health-check with a 60 second interval..) Anyhow its been like this for years afaik, i guess it wont matter much if stays like this a bit longer. Regards, PiBa-NL (Pieter)

stats webpage crash, htx and scope filter, [PATCH] REGTEST is included

in advance. A regtest is attached that reproduces the behavior, and which i think could be included into the haproxy repository. Regards, PiBa-NL (Pieter) Program terminated with signal SIGSEGV, Segmentation fault. #0  0x00564fe7 in strnistr (str1=0x802631048 "fe1", len_str1

Re: Get client IP

Best regards Aleks Thanks & Best Regards! * VU XUAN HOC Regards, PiBa-NL (Pieter)

Re: stats webpage crash, htx and scope filter, [PATCH] REGTEST is included

Hi Christopher, Op 14-1-2019 om 11:17 schreef Christopher Faulet: Le 12/01/2019 à 23:23, PiBa-NL a écrit : Hi List, I've configured haproxy with htx and when i try to filter the stats webpage. Sending this request: "GET /?;csv;scope=b1" to '2.0-dev0-762475e 2019/01/10

Re: stats webpage crash, htx and scope filter, [PATCH] REGTEST is included

Hi Christopher, Op 15-1-2019 om 10:48 schreef Christopher Faulet: Le 14/01/2019 à 21:53, PiBa-NL a écrit : Hi Christopher, Op 14-1-2019 om 11:17 schreef Christopher Faulet: Le 12/01/2019 à 23:23, PiBa-NL a écrit : Hi List, I've configured haproxy with htx and when i try to filter the

Re: stats webpage crash, htx and scope filter, [PATCH] REGTEST is included

-2019 om 11:17 schreef Christopher Faulet: If it's ok for you, I'll also merge your regtest. Can you add the regtest as well into the git repo? Regards, PiBa-NL (Pieter)

Re: [PATCH] REG-TEST: mailers: add new test for 'mailers' section

patch. Without needing the 'timeout mail' setting. I think we can call it fixed once committed. Thanks, PiBa-NL (Pieter)

Re: haproxy 1.9.2 with boringssl

ls under certain configuration circumstances existed for years before it was spotted with the regtest. https://www.mail-archive.com/haproxy@formilux.org/msg32190.html http://git.haproxy.org/?p=haproxy.git;a=commit;h=774c486cece942570b6a9d16afe236a16ee12079 Regards, PiBa-NL (Pieter)

h1-client to h2-server host header / authority conversion failure.?

this is the main problem, but it seems suspicious to me.. Regards, PiBa-NL (Pieter) varnishtest "Check H1 client to H2 server with HTX." feature ignore_unknown_macro syslog Slog_1 -repeat 1 -level info { recv } -start server s1 -repeat 2 { rxpri stream 0 { txsettings

Re: h1-client to h2-server host header / authority conversion failure.?

Hi Willy, List, Just a little check, was below mail received properly with the 6 attachments (vtc/vtc/log/png/png/pcapng) .? (As it didn't show up on the mail-archive.) Regards, PiBa-NL (Pieter) Op 26-1-2019 om 21:04 schreef PiBa-NL: Hi Willy, Op 25-1-2019 om 17:04 schreef Willy Ta

Re: h1-client to h2-server host header / authority conversion failure.?

Hi Willy, Op 2-2-2019 om 0:01 schreef Willy Tarreau: On Fri, Feb 01, 2019 at 09:43:13PM +0100, PiBa-NL wrote: The 'last' part is in TCP mode, and is intended like that to allow me to run tcpdump/wireshark on the un-encrypted traffic, and being certain that haproxy would not modify

regtest, response lenght check failure for /reg-tests/http-capture/h00000.vtc with HTX enabled, using 2.0-dev1

a=commit;h=b8d2ee040aa21f2906a4921e5e1c7afefb7e I 'think' the syslog output for a single request/response should remain the same with/without htx? Or should the size check be less strict or accept 1 of 2 possible outcomes with/without htx.? Regards, PiBa-NL (Pieter) S 0.0 syslog|<134>Feb 26 20

Re: haproxy reverse proxy to https streaming backend

othing else. Could someone send me such a lua-script example and how to include in haproxy. Thanks I personally think this is ugly compared to trying to fix the faulty client. Maybe you can report your issue to the author(s) and share your config to help them reproduce it ? Regards, Willy Regards, PiBa-NL (Pieter)

Re: haproxy reverse proxy to https streaming backend

sequence..[=[ #EXT-X-TARGETDURATION:2 ]=] print("Result:\n"..result) Result: #EXTM3U #EXT-X-VERSION:3 #EXT-X-MEDIA-SEQUENCE:01234 #EXT-X-TARGETDURATION:2 Thanks, Thomas Am 15.03.2019 um 00:27 schrieb PiBa-NL: Hi Thomas, Op 14-3-2019 om 20:28 schreef Thomas Schmiedl: Hello,

Re: DNS Resolver Issues

ly a good feature request to support re-resolving a dns name for the addr setting as well ? Regards, PiBa-NL (Pieter) Op 21-3-2019 om 20:37 schreef Daniel Schneller: Hi! Thanks for the response. I had looked at the "hold" directives, but since they all seem to have reasonab

Re: How to allow Client Requests at a given rate

ed.. So depending on expected runtime of a request and when the server will start to have trouble the current 10/minute might be perfectly fine.. or make it a 1 per 10 seconds.?. So to sum things up.. the limiting is working, and its allowing 10 request in the first minute, just as specified. So in that regard its working correctly already.. Regards, PiBa-NL (Pieter)

2.0-dev5-ea8dd94 - conn_fd_handler() - dumps core - Program terminated with signal 11, Segmentation fault.

e the following: - gdb# bt full  of one of the crashed tests.. - summary of failed tests Regards, PiBa-NL (Pieter) gdb --core /tmp/haregtests-2019-06-05_20-40-20.7ZSvbo/vtc.65353.510907b0/h1/haproxy.core ./work/haproxy-ea8dd94/haproxy GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation

Re: 2.0-dev5-ea8dd94 - conn_fd_handler() - dumps core - Program terminated with signal 11, Segmentation fault.

Hi Olivier, Op 6-6-2019 om 18:20 schreef Olivier Houchard: Hi Pieter, On Wed, Jun 05, 2019 at 09:00:22PM +0200, PiBa-NL wrote: Hi Olivier, It seems this commit ea8dd94  broke something for my FreeBSD11 system. Before that commit (almost) all vtest's succeed. After it several cause core-

Re: haproxy 2.0-dev5-a689c3d - A bogus STREAM [0x805547500] is spinning at 100000 calls per second and refuses to die, aborting now!

anks. Regards, PiBa-NL (Pieter)

slow healthchecks after dev6+ with added commit "6ec902a MINOR: threads: serialize threads initialization"

the 20ms connect/server timeouts to also to fail the test fairly often but not always.. Seems like something isn't quite right there. Can you check? Regards, PiBa-NL (Pieter) Log can be seen below (p.s. i added milliseconds output also to the vtest log.. ): ***  h2    0.299 debug|[WARN

Re: slow healthchecks after dev6+ with added commit "6ec902a MINOR: threads: serialize threads initialization"

Hi Willy, Op 10-6-2019 om 11:09 schreef Willy Tarreau: Hi Pieter, On Sat, Jun 08, 2019 at 06:07:09AM +0200, Willy Tarreau wrote: Hi Pieter, On Fri, Jun 07, 2019 at 11:32:18PM +0200, PiBa-NL wrote: Hi Willy, After the commit "6ec902a MINOR: threads: serialize threads initialization&quo

Re: slow healthchecks after dev6+ with added commit "6ec902a MINOR: threads: serialize threads initialization"

Hi Willy, Op 10-6-2019 om 16:14 schreef Willy Tarreau: Hi Pieter, On Mon, Jun 10, 2019 at 04:06:13PM +0200, PiBa-NL wrote: Things certainly look better again now regarding this issue. Ah cool! Running the test repeatedly, and manually looking over the results its pretty much as good as it

Re: slow healthchecks after dev6+ with added commit "6ec902a MINOR: threads: serialize threads initialization"

during SSL handshake I think together with the really short timeouts in the testcase itself this is an excellent result. I'm considering this one fully fixed, thanks again. Regards, PiBa-NL (Pieter)

haproxy -v doesn't show commit used when building from 2.0 repository?

ugh. If its caused by the contents of the repository, can it be changed? I find it really useful to see which commit a certain compiled haproxy binary was based upon. Thanks in advance :). Regards, PiBa-NL (Pieter)

haproxy -v doesn't show commit used when building from 2.0 repository?

ugh. If its caused by the contents of the repository, can it be changed? I find it really useful to see which commit a certain compiled haproxy binary was based upon. Thanks in advance . Regards, PiBa-NL (Pieter)

Re: haproxy -v doesn't show commit used when building from 2.0 repository?

Hi Willy, Op 1-8-2019 om 6:21 schreef Willy Tarreau: Hi Pieter, On Wed, Jul 31, 2019 at 10:56:54PM +0200, PiBa-NL wrote: Hi List, I have build haproxy 2.0.3-0ff395c from sources however after running a 'haproxy -v' it shows up as: 'HA-Proxy version 2.0.3 2019/07/23 - http

Re: freebsd builds are broken for few days - 30ee1ef, proxy_protocol_random_fail.vtc fails because scheme and host are now present in the syslog output.

second regext attempt its still using accolades around the IPv6 address.. not sure if all machines would use ipv6 for their localhost connection..) Regards, PiBa-NL (Pieter)

commit 246c024 - breaks loading crt-list with .ocsp files present

cert-list.. Which has its own .ocsp as well.. Can you take a look? Thanks in advance. Regards, PiBa-NL (Pieter)

Re: freebsd builds are broken for few days - 30ee1ef, proxy_protocol_random_fail.vtc fails because scheme and host are now present in the syslog output.

Hi Christopher, It seems you fixed/changed the issue i noticed below a few minutes ago in commit 452e578 :) , thanks. One question remaining about this on my side is if it is expected that some platforms will use 'normalized' URI and others platforms just the regular / ? Regard

Re: commit 246c024 - breaks loading crt-list with .ocsp files present

Op 15-10-2019 om 13:52 schreef William Lallemand: I pushed the fix. Thanks Fix confirmed. Thank you.

Re: freebsd ci is broken - commit 08fa16e - curl download stalls in reg-tests/compression/lua_validation.vtc

tention.. Do you (Willy or anyone), need more information from my side? Or is there a patch i can try to validate? Regards, PiBa-NL (Pieter) Yes im running a somewhat outdated OS here:   FreeBSD freebsd11 11.1-RELEASE FreeBSD 11.1-RELEASE #0 r321309: Fri Jul 21 02:08:28 UTC 2017 r...@releng

Re: freebsd ci is broken - commit 08fa16e - curl download stalls in reg-tests/compression/lua_validation.vtc

ems certainly higher with many cores.. * Using commit 0eae632 it works OK* Just to be sure i re-tested on 16 cores with 2.2-dev0-0eae632 but that does nicely pass: 0 tests failed, 0 tests skipped, 20 tests passed Regards, PiBa-NL (Pieter)

Re: freebsd ci is broken - commit 08fa16e - curl download stalls in reg-tests/compression/lua_validation.vtc

9:20 schreef Olivier Houchard: Hi guys, On Tue, Jan 14, 2020 at 09:45:34PM +0100, Willy Tarreau wrote: Hi guys, On Tue, Jan 14, 2020 at 08:02:51PM +0100, PiBa-NL wrote: Below a part of the output that the test generates for me. The first curl request seems to succeed, but the second one runs i

mcli vtest broken by commit.?. MEDIUM: connections: Get ride of the xprt_done callback.

Hi Olivier, Just to let you know, seems this commit has broken a few regtests: http://git.haproxy.org/?p=haproxy.git;a=commit;h=477902bd2e8c1e978ad43d22dba1f28525bb797a https://api.cirrus-ci.com/v1/task/5885732300521472/logs/main.log Testing with haproxy version: 2.2-dev1 #top TEST reg-test

dns fails to process response / hold valid? (since commit 2.2-dev0-13a9232)

is i would be happy to provide a vtest with a reproduction of the issue though i guess it will be kinda 'slow' if it needs to test for hold valid timings.. Regards, PiBa-NL (Pieter) haproxy config: resolvers globalresolvers     nameserver pfs_routerbox 192.168.0.18:53     resolve_r

Re: [PATCH] BUG/MEDIUM: email-alert: don't set server check status from a email-alert task

atch description. Or perhaps Christopher can create it under his own name? Either way is fine for me. :) Regards, PiBa-NL / Pieter From 3129e1ae21e41a026f6d067b3658f6643835974c Mon Sep 17 00:00:00 2001 From: PiBa-NL Date: Wed, 6 Dec 2017 01:35:43 +0100 Subject: [PATCH] BUG/MEDIUM: email-alert

Re: Status change from MAINT to UP

27; is always appreciated. Regards, PiBa-NL

  1   2   3   4   >