Re: lua socket api settimeout in seconds vs. milliseconds

2017-11-09 Thread Nick Galbreath
thanks wily. re: " CONTRIBUTING in the sources directory," - yes, that is what I was looking for! thanks for the tip. re: least it seems important to round up non-null values to the next millisecond. Definitely, we can and should add some checks for invalid values, etc. I'll read

Re: lua socket api settimeout in seconds vs. milliseconds

2017-11-09 Thread Willy Tarreau
Hi Nick, On Thu, Nov 09, 2017 at 08:27:29PM -0800, Nick Galbreath wrote: > Hello Adis, > > We could certainly add another API/Lua function but it might be easier to > change > > luaL_checkinteger(L, 2) in > > tmout = MAY_LJMP(luaL_checkinteger(L, 2)) * 1000; > > to luaL_checknumber(L, 2),

Re: HAProxy 1.7.9 FreeBSD 100% CPU usage

2017-11-09 Thread Willy Tarreau
On Fri, Nov 10, 2017 at 05:25:11AM +0100, Willy Tarreau wrote: > I just checked the contents and its OK. I think we have something wrong > on the script which generates the snapshots. The git version and the date > are normally updated on the fly by git when building the archive, thanks > to

Re: lua socket api settimeout in seconds vs. milliseconds

2017-11-09 Thread Nick Galbreath
Hello Adis, We could certainly add another API/Lua function but it might be easier to change luaL_checkinteger(L, 2) in tmout = MAY_LJMP(luaL_checkinteger(L, 2)) * 1000; to luaL_checknumber(L, 2), along with appropriate cast to int. Then we have backwards compatibility, less documentation

Re: HAProxy 1.7.9 FreeBSD 100% CPU usage

2017-11-09 Thread PiBa-NL
Hi Willy, List, Is it correct that when i build a haproxy-ss-20171017 snapshot that the version still shows up as: "HAProxy version 1.7.9, released 2017/08/18" on both haproxy -vv and stats page.? Or did i do it wrong? p.s. I changed the Makefile like this: PORTNAME=    haproxy-ss

AWS re:Invent Exibitors - Attendees List

2017-11-09 Thread Laura Smith
Hi, Hope this email finds you doing great. I see that your company is one of the promising exibitors at AWS re:Invent 2017, Nov 27th - Dec 1st, Las Vegas. I was wondering if you would be interested in acquiring the attendees list ( Double verified, Opt-In Contacts ) for your pre and post event

Re: HAProxy 1.7.9 FreeBSD 100% CPU usage

2017-11-09 Thread PiBa-NL
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

HA_PROXY multiline tcp payload

2017-11-09 Thread Michael Lopez
I am utilizing HA_Proxy for TCP load balancing and my configuration is (Keepalive Virtual IP -> Ha_Proxy -> syslog-ng -> source_ip.log). When receiving TCP payloads which are multi line the first line is forwarded appropriately to the source IP log file and rest of the payload goes to a secondary

Re: [RFC] Wireshark dissector for SPOP

2017-11-09 Thread Frederic Lecaille
On 11/05/2017 09:27 AM, my.card@web.de wrote: Hi all, Hi, I've implemented a very basic wireshark (https://www.wireshark.org) dissector for SPOP. I've stumbled over the following issue, that I couldn't figure out, yet. ACTION-ARGS should be multiple TYPED-DATA items, but the data sent

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

2017-11-09 Thread Tim Düsterhus
Andrew, Am 09.11.2017 um 02:00 schrieb Andrew Smalley: > 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 While Willy already replied that the bug is fixed (and no matter how wrong

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

2017-11-09 Thread Tim Düsterhus
Willy, Am 09.11.2017 um 05:33 schrieb Willy Tarreau: > It is harmless (despite annoying for your tests) since it dies when freeing > everything on exit. If you want to get rid of it, it's fixed in the latest > daily snapshot. > I ran across it while creating an early pull request to add support

Re: No TIME-WAIT socket when using Haproxy with Redis

2017-11-09 Thread Moemen MHEDHBI
Hi, If you are talking about TCP health checks, this is a normal behaviour because we take care of closing the connection with a RST after the handshake. And when closing the connection with RST there is no TIME_WAIT because  RFC 793 explicitly says that on |RST| reception no response is to be

No TIME-WAIT socket when using Haproxy with Redis

2017-11-09 Thread Fei Ding
Hi: I am confused about why there is no TIME-WAIT socket when using Haproxy to check Redis living status. Could any one give me some hit, or even get me to the specific source code? Thanks a lot.