Segfault / 1.8.5 / 9a083d1428b

Hi, I just install the 1.8.5 and I encountered some of coredump. Below one of these (Unfortunately, I remove the others before checking their content) #0 0x004a715c in h2_process_mux (h2c=) at src/mux_h2.c:2125 2125 h2s->cs->data_cb->send(h2s->cs); (gdb) bt #0 0x004a715c in

Number of acl-rules

Hi I'm new to HAproxy and have a question that I havent found any answer for. Is there a benchmark regarding number of acl-rules to be evaluated and still have low response time? Scenario is that I'm having a web site that will be moved to a new platform and from a user perspective you wont

Re: [ANNOUNCE] haproxy-1.8.5

Hi. as usual the new images are also available on docker hub. https://hub.docker.com/r/me2digital/haproxy18/ https://hub.docker.com/r/me2digital/openshift-ocp-router-hap18/ Best Regards Aleks Am 23.03.2018 um 17:18 schrieb Willy Tarreau: > Hi, > > HAProxy 1.8.5 was released on 2018/03/23. It

Re: multithreading issuse in haproxy 1.8.5

Hello, On Mon, Mar 26, 2018 at 12:47:02PM +0300, Slawa Olhovchenkov wrote: > On Mon, Mar 26, 2018 at 12:38:57PM +0300, Slawa Olhovchenkov wrote: > > > > Could you check with your previous configuration (nbproc 2 and no > > > nbthread parameter) ? It could help to know if it is a threads related

Re: [PATCH] server-template and allowed chars in the name

Hi Thierry, On Mon, Mar 26, 2018 at 12:00:48PM +0200, Thierry Fournier wrote: > Hi list, > > The name of the "server" directive allows [A-Za-Z0-9_.:-] (see > function invalid_char()). > > The name allowed for the "server-template" directive only allows [A-Za-Z_.-], > the chars [0-9:] disappear.

Re: patch: fix build when USE_THREAD is not defined

On Sat, Mar 24, 2018 at 07:02:32PM +0100, Christopher Faulet wrote: > Le 24/03/2018 à 13:19, ??? a écrit : > > please review attached patch > > Good catch. But instead of using #ifdef in queue.c, there are macros in > hathreads.h. Here is the updated patch. Now applied, thanks! Willy

email alert not working with 1.8.5

I just updated haproxy to 1.8.5 on my FreeBSD 11-Stable server. I just noticed we do not receive any email notifications anymore when a server goes down. We did not change the config. This is what i have in my config (relevant part) default # Mailer config     mailers alert-mailers     timeout

Re: patch: fix build when USE_THREAD is not defined

ok, let's use your approach 2018-03-25 16:52 GMT+05:00 Tim Düsterhus : > Илья, > > Am 24.03.2018 um 19:42 schrieb Илья Шипицин: > > in your patch comparision + empty loop will be executed even if > USE_THREADS > > is not defined. > > not very big performance overhead actually.

%tr or %trg in unix time?

Hi, Is there a way to get variables %tr or %trg in unix timestamp with milliseconds? Thanks Elias

Re: [PATCH] server-template and allowed chars in the name

On 03/26/2018 12:00 PM, Thierry Fournier wrote: Hi list, Hi Thierry, The name of the "server" directive allows [A-Za-Z0-9_.:-] (see function invalid_char()). The name allowed for the "server-template" directive only allows [A-Za-Z_.-], the chars [0-9:] disappear. I do not remember if

Rejected connections not getting counted in stats

Hello, I have a frontend whitelisted by IP with the following rules: acl whitelist src -f /etc/haproxy/whitelist.lst tcp-request connection reject unless whitelist and while documentation suggests I

[PATCH] server-template and allowed chars in the name

Hi list, The name of the "server" directive allows [A-Za-Z0-9_.:-] (see function invalid_char()). The name allowed for the "server-template" directive only allows [A-Za-Z_.-], the chars [0-9:] disappear. This limitation forces the modifications of all the server names which contains numbers and

Re: multithreading issuse in haproxy 1.8.5

On Mon, Mar 26, 2018 at 12:38:57PM +0300, Slawa Olhovchenkov wrote: > > Could you check with your previous configuration (nbproc 2 and no > > nbthread parameter) ? It could help to know if it is a threads related > > problem or not. > > > > Then, try to disable kqueue (nokqueue option in

Re: Segmentation faults (1.8.4-de425f6 2018/02/26)

Hi, No, i'am not using threads. Med venlig hilsen *Peter Lindegaard Hansen* *Softwareudvikler / Partner* Telefon: +45 96 500 300 | Direkte: 69 14 97 04 | Email: p...@tigermedia.dk Tiger Media A/S | Gl. Gugvej 17C | 9000 Aalborg | Web: www.tigermedia.dk For supportspørgsmål kontakt os da

Re: multithreading issuse in haproxy 1.8.5

On Mon, Mar 26, 2018 at 11:03:42AM +0200, Christopher Faulet wrote: > Le 26/03/2018 à 03:10, Slawa Olhovchenkov a écrit : > > I am try to use multithreading w/ haproxy 1.8.5 (on FreeBSD > > 11-stable) and see high and saw-tooth CPU consume. > > > > I am use next config: > > > > global > >

Re: Segmentation faults (1.8.4-de425f6 2018/02/26)

Hi, So what I found in Holger's trace is that the H2 connection has no more streams and was present in the wait queue. The state of the task being deleted doesn't make sense, indicating a memory corruption possibly caused by a use-after-free or a double free or by a wrong wakeup when a buffer is

Re: lua socket api settimeout in seconds vs. milliseconds

On Mon, Mar 26, 2018 at 12:40:19AM +0200, Willy Tarreau wrote: > > did you miss these patches from Thierry to the Lua subsystem? > > Hmmm seems so, I'll recheck tomorrow. Thanks. Now applied. Thanks for notifying! Willy

Re: multithreading issuse in haproxy 1.8.5

Le 26/03/2018 à 03:10, Slawa Olhovchenkov a écrit : I am try to use multithreading w/ haproxy 1.8.5 (on FreeBSD 11-stable) and see high and saw-tooth CPU consume. I am use next config: global nbproc 1 nbthread 2 cpu-map auto:1/1-2 0-1 I am use for comprassion

Re: segfault in haproxy=1.8.4

On Mon, Mar 26, 2018 at 08:53:07AM +0300, ?? ? wrote: > Hi! > > It's been almost 2 weeks since I've installed the patch and there were no > segfaults since then. It seems that the problem is fixed now. Thank you! Thank you Maxim for the report, it's much appreciated! Willy

Why maxconn value can have a negative value?

Hi, When negative value is given for maxconn(-1,-2...-9, 10.) parameter in global section of haproxy.cfg. It is observed that haproxy service starts with successful health check up of backend servers. But when larger negative value is given then haproxy fails to start and Alert message is