Re: resolvers - resolv.conf fallback

On Fri, Apr 13, 2018 at 03:48:19PM -0600, Ben Draut wrote: > How about 'parse-resolv-conf' for the current feature, and we reserve > 'use-system-resolvers' for the feature that Jonathan described? Perfect! "parse" is quite explicit at least! Willy

[PATCH] BUG/MINOR: lua: Socket.send causing 'close' needs 1 arguments.

--- src/hlua.c | 14 ++ 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/src/hlua.c b/src/hlua.c index 60cf8f94..0585a1e7 100644 --- a/src/hlua.c +++ b/src/hlua.c @@ -1629,14 +1629,12 @@ __LJMP static int hlua_socket_gc(lua_State *L) /* The close function send shutdown

[PATCH][MINOR]: config: Warn if resolvers section has no namerservers configured

This implements a simple warning for 'resolvers' sections that have no nameservers. Previously discussed here: https://www.mail-archive.com/haproxy@formilux.org/msg29600.html Thanks, Ben From fc6a36dabec89eef0eba13146cecbf157f0675b9 Mon Sep 17 00:00:00 2001 From: Ben Draut

Re: resolvers - resolv.conf fallback

How about 'parse-resolv-conf' for the current feature, and we reserve 'use-system-resolvers' for the feature that Jonathan described? On Fri, Apr 13, 2018 at 3:46 PM, Willy Tarreau wrote: > Hi Jonathan, > > On Fri, Apr 13, 2018 at 09:24:54PM +, Jonathan Matthews wrote: > > On

Re: resolvers - resolv.conf fallback

Hi Jonathan, On Fri, Apr 13, 2018 at 09:24:54PM +, Jonathan Matthews wrote: > On Fri, 13 Apr 2018 at 15:09, Willy Tarreau wrote: > > > On Fri, Apr 13, 2018 at 08:01:13AM -0600, Ben Draut wrote: > > > How about this: > > > > > > * New directive: 'use_system_nameservers' > > > >

Re: resolvers - resolv.conf fallback

On Fri, 13 Apr 2018 at 15:09, Willy Tarreau wrote: > On Fri, Apr 13, 2018 at 08:01:13AM -0600, Ben Draut wrote: > > How about this: > > > > * New directive: 'use_system_nameservers' > > OK, just use dashes ('-') instead of underscores as this is what we mostly > use on other

Re: Health Checks not run before attempting to use backend

Well after having read your thread that's disappointing. An alternative solution to forcing healthchecks before the bind It would be nice to have an option to initially start all servers in the down state unless explicitly loaded as up via a "show servers state /load-server-state-from-file"

haproxy.org & jooble

Good day, My name is Emma Vang and I am Jooble representative. Jooble is a worldwide job search engine that operates in 65 countries. Every day more than 2,5 million people all over the world visit our website: https://jooble.org/. We would like to offer haproxy.org free banner advertisement on

Re: Segfault in haproxy v1.8 with Lua

I see your point. Thanks for your help. On Fri, Apr 13, 2018 at 4:20 AM, Christopher Faulet wrote: > Le 12/04/2018 à 17:41, Hessam Mirsadeghi a écrit : > >> But using an applet on a request will prevent the request from being sent >> to the backend servers; I still want

Re: Health Checks not run before attempting to use backend

On Fri, 13 Apr 2018 at 00:01, Dave Chiluk wrote: > Is there a way to force haproxy to not use a backend until it passes a > healthcheck? I'm also worried about the side affects this might cause as > requests start to queue up in the haproxy > I asked about this in

Re: HAProxy 1.8.X crashing

Hi Praveen, On Fri, Apr 13, 2018 at 02:03:47PM +, UPPALAPATI, PRAVEEN wrote: > Hi Oliver, > > The crash got fixed with the patch you provided before. Thanks for this useful feedback! > Do you thing the latest patch will be the right solution? It should, and if it doesn't, it means we

Re: HAProxy 1.8.X crashing

Hi Praveen, On Fri, Apr 13, 2018 at 02:03:47PM +, UPPALAPATI, PRAVEEN wrote: > Hi Oliver, > > The crash got fixed with the patch you provided before. > > Do you thing the latest patch will be the right solution? > > Thanks, > Praveen. > It should be fine. Regards, Olivier

Re: resolvers - resolv.conf fallback

On Fri, Apr 13, 2018 at 08:01:13AM -0600, Ben Draut wrote: > How about this: > > * New directive: 'use_system_nameservers' OK, just use dashes ('-') instead of underscores as this is what we mostly use on other keywords, except a few historical mistakes. > * Parse /etc/resolv.conf for

RE: HAProxy 1.8.X crashing

Hi Oliver, The crash got fixed with the patch you provided before. Do you thing the latest patch will be the right solution? Thanks, Praveen. -Original Message- From: Olivier Houchard [mailto:ohouch...@haproxy.com] Sent: Friday, April 13, 2018 8:57 AM To: Willy Tarreau

Re: HAProxy 1.8.X crashing

On Fri, Apr 13, 2018 at 03:56:31PM +0200, Olivier Houchard wrote: > Ok, here is a patch that does exactly what you suggest. I'm not entirely > happy with it, but it'll do the job, as a stopgap. I want this crash > fixed :) Great, now merged, thank you! If you don't mind, I changed the tag to

Re: resolvers - resolv.conf fallback

How about this: * New directive: 'use_system_nameservers' * Parse /etc/resolv.conf for nameservers when new directive is seen when parsing resolvers. * Make check_config_validity issue a warning for each resolvers section that has an empty nameservers list. Thoughts? On Tue, Apr 10, 2018 at

Re: HAProxy 1.8.X crashing

Hi, On Thu, Apr 12, 2018 at 11:33:43PM +0200, Willy Tarreau wrote: > That may be the problem. But if a mux fails to initialize, then we can't > destroy them either ? Is cs_destroy() the problem here maybe ? If so, I > suspect that this approach would be more robust and would better match > the

MINOR: proxy: Add fe_defbe fetcher

Hi, New fetcher which adds ability to retrieve default backend name for frontend. Should cleanly apply to both 1.8 & 1.9 branches. Regards, Marcin Deranek >From b2eeddea4859ab247b5315fb470706175797d434 Mon Sep 17 00:00:00 2001 From: Marcin Deranek Date: Fri, 13 Apr

Re: Problem installing 1.8.7 -- systemd changes

On 13-04-2018 03:58, Shawn Heisey wrote: I have a script on my system that I use to handle compiling and installing a new haproxy version.  That script has "EXTRA=haproxy-systemd-wrapper"on the line that does the install. It looks like that's no longer part of haproxy, and that the systemd

Re: 1.8.7 http-tunnel doesn't seem to work? (but default http-keep-alive does)

On Fri, Apr 13, 2018 at 06:50:50AM +, Pi Ba wrote: > Using poll (startup with -dk) the request works properly. Thank you Pieter! Willy

Haproxy 1.8 with OpenSSL 1.1.1-pre4 stops working after 1 hour

Hi all, I built Haproxy (1.8.7) against openssl 1.1.1-pre4, and now after 1 hour running haproxy stops accepting new SSL connections. When I restart it works again for almost(?) exactly 1 hour, then stops. Any idea what might be causing this, or where I should look # haproxy -vv HA-Proxy version

Re: Segfault in haproxy v1.8 with Lua

Le 12/04/2018 à 17:41, Hessam Mirsadeghi a écrit : But using an applet on a request will prevent the request from being sent to the backend servers; I still want backend servers to receive the request. So, there is nothing much to do apart writing a filter. As I said, this is not trivial at

Re: Problem installing 1.8.7 -- systemd changes

Hi shawn. Am 13.04.2018 um 03:58 schrieb Shawn Heisey: > I have a script on my system that I use to handle compiling and > installing a new haproxy version.  That script has > "EXTRA=haproxy-systemd-wrapper"on the line that does the install. > > It looks like that's no longer part of haproxy,

Re: 1.8.7 http-tunnel doesn't seem to work? (but default http-keep-alive does)

Using poll (startup with -dk) the request works properly. Op vr 13 apr. 2018 08:29 schreef Willy Tarreau : > Hi Pieter, > > On Fri, Apr 13, 2018 at 01:12:41AM +0200, PiBa-NL wrote: > > To clarify the issue is not that haproxy uses cpu by looping, the issue > is > > that haproxy

Re: 1.8.7 http-tunnel doesn't seem to work? (but default http-keep-alive does)

Hi Pieter, On Fri, Apr 13, 2018 at 01:12:41AM +0200, PiBa-NL wrote: > To clarify the issue is not that haproxy uses cpu by looping, the issue is > that haproxy prevents the page from loading in the browser. The 'fix' on the > old version after the commit introducing the issue was to call the