Re: HAProxy 1.7.9 FreeBSD 100% CPU usage

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 it would happen > again. It did after a few

Re: Error in `haproxy': munmap_chunk(): invalid pointer:

Hi Tim, On Thu, Nov 09, 2017 at 01:00:22AM +0100, Tim Düsterhus wrote: > Hi > > I get the following crash when running: > > [timwolla@/t/h/haproxy-1.8-rc2]./haproxy -V > HA-Proxy version 1.8-rc2-a8d8d6e 2017/11/03 > Copyright 2000-2017 Willy Tarreau > > with the

HAProxy 1.7.9 FreeBSD 100% CPU usage

Hi List, I've experienced a issue where its using 100% cpu usage with haproxy 1.7.9 on FreeBSD 11.1p3 / pfSense 2.4.2dev. There is very little traffic actually hitting this haproxy instance. But it happened for the second time in a few days now. Actually haproxy has been running for a few

Re: Error in `haproxy': munmap_chunk(): invalid pointer:

Hi Tim Can you try a make install first please or mkdir -p '/etc/haproxy/state/ so the state directory exists and then re-test. The above is a guess, can you supply the build commands and clarify this line in the config " bind :::80 v4v6" ? Dont you want to "bind *:80" and use IPv4 only Andruw

Error in `haproxy': munmap_chunk(): invalid pointer:

Hi I get the following crash when running: [timwolla@/t/h/haproxy-1.8-rc2]./haproxy -V HA-Proxy version 1.8-rc2-a8d8d6e 2017/11/03 Copyright 2000-2017 Willy Tarreau with the configuration at the bottom of this email as follows: root@node42:/tmp/haproxy/haproxy-1.8-rc2#

AFM in Focus Dailies November 8

**Follow us on the social networks and filmfestivals.com. **

Re: Diagnose a PD-- status

Christopher, We couldn’t had the error reproduced today : both dataset and client tool were updated. However, I keep the configuration options at hand if I ever need to debug this issue further again. Thanks for your time on this. Regards, Mildis > Le 7 nov. 2017 à 10:14, Christopher Faulet

Re: [Working update]: Request rate limiting on the backend section

To remove the reported "margin of error", the config needed a fix: acl within_limit sc2_gpc0_rate() lt 1000 since the first request was at rate==0, and last one is at 999. On Wed, Nov 8, 2017 at 3:11 PM, Krishna Kumar (Engineering) < krishna...@flipkart.com> wrote: > I finally got

[Working update]: Request rate limiting on the backend section

I finally got the backend rate limiting working pretty well. Here is the configuration settings in case it helps anyone else do the same: frontend http-fe bind default_backend http-be backend http-be http-request track-sc2 fe_id stick-table type integer size 1k

Re: lua socket api settimeout in seconds vs. milliseconds

On 11/07/2017 08:49 PM, Nick Galbreath wrote: > I have a question regarding the socket:settimeout function. > > It appears to only accept an integer value for seconds, but internally > converts to milliseconds (see below). > > Is there a reason to enforce whole seconds, or could this be relaxed