Re: Table sticky counters decrementation problem

based on it. Thanks! Willy -- Thomas SIMON Responsable Infrastructures Neteven

Re: Table sticky counters decrementation problem

and not something like 2.2 or 2.0 ? Can you provide the full output of haproxy -vv? Thanks, Lukas -- Thomas SIMON Responsable Infrastructures Neteven

Table sticky counters decrementation problem

Hi all, Since version 2.3.8, I've noticed problem with come sticky counters, which only increments, and never decrements. The behavior was OK in 2.3.7 frontend web     bind *:443 ssl crt /etc/ssl/certs/...     http-request track-sc0 src table global_limits backend global_limits

Integration of modsecurity v3 with haproxy

Hi all, Is there a way to use some mecanism (spoe or other) to use modsecurity v3 with haproxy (2.x) ? I found documentation on modsecurity v2 integration with spoe , but nothing on v3. My goal is to protect backends with modsecurity using owasp CRS. I've setup a nginx with modsecurity v3 on

Re: QUIC and the PROXY protocol

On Friday, October 9, 2020 4:28 PM, Frederic Lecaille wrote: > > > The IETF-QUIC transport protocol spec [1] hasn't been ratified, but > > > there exists a number of QUIC deployments in the wild. I'm writing a > > > proxy and I'd like to add support for QUIC. Are there any plans to add > > >

QUIC and the PROXY protocol

Hi all, The IETF-QUIC transport protocol spec [1] hasn't been ratified, but there exists a number of QUIC deployments in the wild. I'm writing a proxy and I'd like to add support for QUIC. Are there any plans to add QUIC4/QUIC6 to the list of PROXY transport protocols? Thanks, Simon Ser [1

Re: req.body_param([])

-request     declare capture request len 4     http-request capture req.body_param(customerId) id 0 As my haproxy version differs from yours I'm unsure where I might made a configuration error. Thanks for your help, best Simon Am 11.05.2018 um 12:43 schrieb Jarno Huuskonen: Hi,

req.body_param([])

req.body_param([]) on any HTTP method type instead of restricting it to HTTP POST? Best Simon -- SEMKNOX GmbH Simon Schabel Webergasse 1, Haus B/1 · 01067 Dresden simon.scha...@semknox.com · +49-351-32 123 102 · www.semknox.com

Re: AW: Load balancing a single page application

ache < Expires: -1 < Last-Modified: 0 < Content-Type: text/html;charset=utf-8 < Transfer-Encoding: chunked < Vary: Accept-Encoding < Date: Fri, 27 Apr 2018 10:20:07 GMT So, yes, it is still being set by the application. Simon On 27/04/18 10:59, Maximilian Boehm wrote: H

Re: AW: Load balancing a single page application

Interesting - the vendor didn't notify us about such a change. I'll have to investigate. Simon On 27/04/18 10:59, Maximilian Boehm wrote: Hi, Sessions are managed on haproxy with a stick table which stores a JSESSIONID Just to make sure: Are you sure this application still uses JSESSIONID

Load balancing a single page application

front_jsessionid     stick-table type string len 52 size 10m expire 30m There is a further backend which is the server used for authentication; the session cookie is not shared with that. Thanks, Simon

Re: [PATCH 0/2] MEDIUM: stats: Add JSON output option to show (info|stat)

Hi Willy, this patchset seems to have stalled. I'd like to find a way to revive it. On Sun, Jan 08, 2017 at 11:52:46AM +0100, Simon Horman wrote: > Hi Willy, > > On Sun, Jan 08, 2017 at 07:37:24AM +0100, Willy Tarreau wrote: > > Hi Simon, > > > > On Wed, Jan 04, 2017

Rate limit by country

ent limits for different countries. Is this possible with HAProxy, and if so, how? TIA for your guidance. -- Simon [1] where "country" is defined by MaxMind's GeoIP list. It's not perfect, but better than nothing. [2] and along with src -f TLD.lst can set different limits for different countries.

Re: [PATCH 0/2] MEDIUM: stats: Add JSON output option to show (info|stat)

uot;: "HAProxy" > } > }, > { > "field": { > "name": "Version", > "pos": 1 > }, > "processNum": 1, > "tags": { > "natu

Re: [PATCH 0/2] MEDIUM: stats: Add JSON output option to show (info|stat)

On Thu, Jan 12, 2017 at 01:27:37PM +, Scott McKeown wrote: > Hi Simon, > > Output below: ... Thanks > On 12 January 2017 at 13:23, Simon Horman <si...@horms.net> wrote: > > > Hi Scott, > > > > could you send the output of the following? >

Re: [PATCH 0/2] MEDIUM: stats: Add JSON output option to show (info|stat)

hed with Simons git repo pull. > Simon are you sure this is correct as I thought this was for a 1.8-dev > build which could be why I had problems on Tuesday. > > # haproxy -v > HA-Proxy version 1.6-dev1 2015/03/11 > Copyright 2000-2015 Willy Tarreau <w...@1wt.eu> > >

Re: [PATCH 0/2] MEDIUM: stats: Add JSON output option to show (info|stat)

Hi Scott, thanks for testing. For reference the code I am using is here: https://github.com/horms/haproxy.git show-json And my minimal config file is as follows. Would it be possible for you to share you config with me (privately) ? global daemon stats socket /tmp/haproxy.stat

Re: [PATCH 0/2] MEDIUM: stats: Add JSON output option to show (info|stat)

Hi Willy, On Sun, Jan 08, 2017 at 07:37:24AM +0100, Willy Tarreau wrote: > Hi Simon, > > On Wed, Jan 04, 2017 at 09:37:24AM +0100, Simon Horman wrote: > > Hi, > > > > this short series is an RFC implementation of adding JSON format > > output to show (info|stat

[PATCH 1/2] MEDIUM: stats: Add JSON output option to show (info|stat)

t routines to only insert a "," between elements when needed. I would value any feedback on how this might be done better. Signed-off-by: Simon Horman <ho...@verge.net.au> --- For the simple configuration below a comparison of the size of info and stats output i

[PATCH 0/2] MEDIUM: stats: Add JSON output option to show (info|stat)

in first patch * Possible automatic generation of (part) of schema in 2nd patch * Improved documentation Some discussion of the size of JSON output is included as an appendix to the changelog of the first patch. Changes since RFC noted in per-patch changelogs. Simon Horman (2): MEDIUM: stats: Add

[PATCH 2/2] MEDIUM: stats: Add show json schema

chema.txt $ echo "show info json" | socat /var/run/haproxy.stat stdio > instance.txt python ./jschema.py $ echo "show stats json" | socat /var/run/haproxy.stat stdio > instance.txt python ./jschema.py Signed-off-by: Simon Horman <ho...@verge.net.au> --- In this case

Re: [PATCH/RFC 2/2] MEDIUM: stats: Add show json schema

than > 2^64), it requires 23 years of traffic at 100 Gbps to have that high a > byte count instead of 46 years, so we have some margin. I agree this could be a sticky point. I believe the limits are left up to the implementation. But I'll do a bit of research and see if I can find a better number.

Re: [PATCH/RFC 0/2] MEDIUM: stats: Add JSON output option to show (info|stat)

On Tue, Nov 29, 2016 at 08:01:53AM +0100, Willy Tarreau wrote: > Hi Simon, > > On Mon, Nov 28, 2016 at 04:18:52PM +0100, Simon Horman wrote: > > Hi, > > > > this short series is an RFC implementation of adding JSON format > > output to show (info|stat). It

[PATCH/RFC 1/2] MEDIUM: stats: Add JSON output option to show (info|stat)

t routines to only insert a "," between elements when needed. I would value any feedback on how this might be done better. Signed-off-by: Simon Horman <ho...@verge.net.au> --- For the simple configuration below a comparison of the size of info and stats output i

[PATCH/RFC 2/2] MEDIUM: stats: Add show json schema

$ echo "show info json" | socat /tmp/haproxy.stat stdio > instance.txt python ./jschema.py $ echo "show stats json" | socat /tmp/haproxy.stat stdio > instance.txt python ./jschema.py Signed-off-by: Simon Horman <ho...@verge.net.au> --- In this case the pretty pri

[PATCH/RFC 0/2] MEDIUM: stats: Add JSON output option to show (info|stat)

in first patch * Possible automatic generation of (part) of schema in 2nd patch * Improved documentation Some discussion of the size of JSON output is included as an appendix to the changelog of the first patch. Simon Horman (2): MEDIUM: stats: Add JSON output option to show (info|stat) MEDIUM

[PATCH] MINOR: stats: correct documentation of process ID for typed output

The process ID appears at the end of the first column rather than the line. --- doc/management.txt | 12 +++- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/doc/management.txt b/doc/management.txt index 751621c0392b..f42c0712012e 100644 --- a/doc/management.txt +++

Re: Getting JSON encoded data from the stats socket.

On Mon, Nov 14, 2016 at 08:50:54AM -0500, hapr...@stormcloud9.net wrote: > Might help to see an example of what the results look like when using > this schema, however I do have one comment below. Yes, agreed. I plan to work on making that so. > On 2016/11/14 03:09, Simon Horman wrot

Re: Getting JSON encoded data from the stats socket.

Hi Willy, On Mon, Nov 14, 2016 at 03:10:18PM +0100, Willy Tarreau wrote: > On Mon, Nov 14, 2016 at 11:34:18AM +0100, Simon Horman wrote: > > > Sometimes a description like above appears in your example, is it just > > > for a few fields or do you intend to describe all

Re: Getting JSON encoded data from the stats socket.

Hi Willy, Hi All, On Thu, Nov 10, 2016 at 04:52:56PM +0100, Willy Tarreau wrote: > Hi Simon! > > On Thu, Nov 10, 2016 at 04:27:15PM +0100, Simon Horman wrote: > > My preference is to take things calmly as TBH I am only just getting > > started on this and I think the schem

Re: Getting JSON encoded data from the stats socket.

On Thu, Nov 10, 2016 at 04:12:31PM +0100, Willy Tarreau wrote: > Hi Malcolm, > > On Thu, Nov 10, 2016 at 12:53:13PM +, Malcolm Turnbull wrote: > > Georg, > > > > That's a timely reminder thanks: > > I just had another chat with Simon Horman who has

Re: HAProxy reloads lets old and outdated processes

On 24 October 2016 at 13:46, Pierre Cheynier wrote: > Hi, > > Sorry, wrong order in the answers. > > > Yes it has something to do with it because it's the systemd-wrapper which > > delivers the signal to the old processes in this mode, while in the > normal > > mode the

Re: haproxy does not correctly handle MSS on Freebsd

Thank you, Lukas. I would investigate it a bit more. Simon 20160821

Re: haproxy does not correctly handle MSS on Freebsd

Hi Lukas, Hi Simon, Am 19.08.2016 um 12:41 schrieb k simon: Hi,List: Haproxy's throughput is much less than nginx or squid on FreeBSD and it's high cpu usage often. When I investigate it a bit more, I found haproxy does not correctly handle MSS on FreeBSD. Your kernel decides

Re: haproxy does not correctly handle MSS on Freebsd

path_mtu_discovery set to 0 or 1, it worked weird . 3. MSS option is invalid on FreeBSD. I'm running haproxy instance inside a vimage jail, and it should act the same as runing on bare box. It's really a serious problem and easily to reproduced. Regards Simon P.S. 1. FreeBSD ha-l0-j2 10.3

haproxy does not correctly handle MSS on Freebsd

instance inside a vimage jail, and it should act the same as runing on bare box. It's really a serious problem and easily to reproduced. Regards Simon P.S. 1. FreeBSD ha-l0-j2 10.3-STABLE FreeBSD 10.3-STABLE #0 r303988: Fri Aug 12 16:48:21 CST 2016 root@cache-farm-n2:/usr/obj/usr/src/sys/10

Does haproxy use regex for balance url_param lookup?

't confirm it. And does haproxy support wildcard in acl string match ? I can rewrite my acls to avoid the pcre lib totally. Simon 20160626

subscribe

Re: external-check stdout ends up in load-balanced traffic, destroying tcp sessions

On Tue, Jun 07, 2016 at 08:18:21PM +0200, Willy Tarreau wrote: > On Tue, Jun 07, 2016 at 12:01:31PM +0200, Benoit Garnier wrote: > > You can always open /dev/null before chrooting and dup() it into FD 0 and 1 > > after chroot() has been called. > > I'd be more tempted to simply close those FDs

Re: external-check stdout ends up in load-balanced traffic, destroying tcp sessions

Hi Cyril, Hi Lukas, On Mon, Jun 06, 2016 at 08:21:46PM +0200, Cyril Bonté wrote: > Hi Lukas, > > I add Malcolm and Simon to the thread. > > Le 06/06/2016 à 08:36, Lukas Erlacher a écrit : > >Additional info: The output only ends up in the *first* client connection.

Re: [PATCH 1/4] mailer: increase default timeout to 10 seconds this allows the TCP connection to retry connecting when a packet is lost on the network

Hi Pieter, Hi Willy, On Tue, Feb 16, 2016 at 10:11:34PM +0100, P.Baauw wrote: > Hi Willy, Simon, > > Op 16-2-2016 om 21:56 schreef Willy Tarreau: > >Simon, > > > >are you OK with this series from Pieter ? Yes, they look good to me. Thanks Pieter for the fixes/enh

Re: [PATCH] MEDIUM: mailer: try sending a mail up to 3 times

On Fri, Nov 20, 2015 at 11:58:19PM +0100, PiBa-NL wrote: > Hi Willy, > > Op 16-11-2015 om 19:57 schreef Willy Tarreau: > >I agree with you since we don't know the timeout value nor what it applies > >to (connection or anything). Thus I think that we should first find and > >change that value, and

[SPAM] Water Retaining Gel-Reduce Irrigation And Increase Yield

Good Day!Glad to know you replied to my message and I am writing this email to give you more details about our products.SOCO Water Gel--A amazing material absorbing water for plants!Advantages:–Improve seed germination and emergence to give plants an early, health start.–Save the irrigation,

Re: [PATCH] MEDIUM: mailer: try sending a mail up to 3 times

On Mon, Nov 09, 2015 at 11:11:53AM +0100, Willy Tarreau wrote: > Hi Pieter, > > > Hi Ben, Willy, Simon, > > > > Ben, thanks for the review. > > Hoping 'release pressure' has cleared for Willy i'm resending the > > patch now, with with your comments

Restarted backend not picked up

with ping, telnet, etc. After restarting haproxy, those backends were recognized as up again. I looked briefly at the 1.5.x release notes after 1.5.4, and didn't see anything obviously related. Has anyone had the same problem? Thanks! -Simon

Re: [PATCH 1/2] MEDIUM: Do not send email alerts corresponding to log-health-checks messages

On Tue, Apr 28, 2015 at 09:24:42AM +0200, Willy Tarreau wrote: On Tue, Apr 28, 2015 at 02:25:02PM +0900, Simon Horman wrote: On Tue, Apr 28, 2015 at 06:43:38AM +0200, Willy Tarreau wrote: Hi Simon, On Tue, Apr 28, 2015 at 10:58:56AM +0900, Simon Horman wrote: This seems only

Re: [PATCH v2 0/3] MEDIUM: Change verbosity of email alerts

On Thu, Apr 30, 2015 at 07:31:28AM +0200, Willy Tarreau wrote: Hi Simon, On Thu, Apr 30, 2015 at 01:10:32PM +0900, Simon Horman wrote: Hi, the aim of this series is to make the send more email alerts when they are likely to be useful and less when they are likely to be unwanted

[PATCH v2 0/3] MEDIUM: Change verbosity of email alerts

sending them * Added documentation patch Simon Horman (3): MEDIUM: Lower priority of email alerts for log-health-checks messages MEDIUM: Send email alerts when servers are marked as UP or enter the drain state MEDIUM: Document when email-alerts are sent doc/configuration.txt | 9

[PATCH v2 3/3] MEDIUM: Document when email-alerts are sent

Document the influence of email-alert level and other configuration parameters on when email-alerts are sent. Signed-off-by: Simon Horman ho...@verge.net.au --- doc/configuration.txt | 9 + 1 file changed, 9 insertions(+) diff --git a/doc/configuration.txt b/doc/configuration.txt index

[PATCH v2 2/3] MEDIUM: Send email alerts when servers are marked as UP or enter the drain state

should be set to 'notice', 'info' or 'debug'. e.g: email-alert level notice email-alert mailers and email-alert to settings are also required in order for any email alerts to be sent. A follow-up patch will document the above. Signed-off-by: Simon Horman ho...@verge.net.au --- src/server.c | 2

[PATCH v2 1/3] MEDIUM: Lower priority of email alerts for log-health-checks messages

state changes log-health-checks needs to be set and email-alert level needs to be 'info' or lower. email-alert mailers and email-alert to settings are also required in order for any email alerts to be sent. A follow-up patch will document the above. Signed-off-by: Simon Horman ho...@verge.net.au

[PATCH 0/2] MEDIUM: Change verbosity of email alerts

Hi, the aim of this series is to make the send more email alerts when they are likely to be useful and less when they are likely to be unwanted. Simon Horman (2): MEDIUM: Do not send email alerts corresponding to log-health-checks messages MEDIUM: Send email alerts when servers

[PATCH 2/2] MEDIUM: Send email alerts when servers are marked as UP or enter the drain state

should be set to 'notice', 'info' or 'debug'. e.g: email-alert level notice email-alert mailers and email-alert to settings are also required in order for any email alerts to be sent. Signed-off-by: Simon Horman ho...@verge.net.au --- src/server.c | 2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH 1/2] MEDIUM: Do not send email alerts corresponding to log-health-checks messages

This seems only to lead to excessive verbosity which seems much more appropriate for logs than email. Signed-off-by: Simon Horman ho...@verge.net.au --- src/checks.c | 1 - 1 file changed, 1 deletion(-) diff --git a/src/checks.c b/src/checks.c index 3702d9a4b0fe..efcaff20219b 100644 --- a/src

Re: [PATCH 1/2] MEDIUM: Do not send email alerts corresponding to log-health-checks messages

On Tue, Apr 28, 2015 at 06:43:38AM +0200, Willy Tarreau wrote: Hi Simon, On Tue, Apr 28, 2015 at 10:58:56AM +0900, Simon Horman wrote: This seems only to lead to excessive verbosity which seems much more appropriate for logs than email. Signed-off-by: Simon Horman ho...@verge.net.au

Re: [PATCH v2 0/4] MEDIUM: Enhancements to reporting of drain in stats

On Thu, Apr 23, 2015 at 10:01:19AM +0200, Willy Tarreau wrote: Hi Simon, On Thu, Apr 23, 2015 at 02:51:25PM +0900, Simon Horman wrote: (...) This series attempts to address that problem by first disentangling the state and colour of servers in the first two patches, which are new

[PATCH v2 0/4] MEDIUM: Enhancements to reporting of drain in stats

of the drain state, as described above. Patches have been lightly tested. Simon Horman (4): MEDIUM: Add enum srv_stats_state MEDIUM: Separate server state and colour in stats MEDIUM: Only report drain state in stats if server has SRV_ADMF_DRAIN set MEDIUM: Differentiate between DRAIN

[PATCH v2 1/4] MEDIUM: Add enum srv_stats_state

not make any functional changes. Signed-off-by: Simon Horman ho...@verge.net.au --- v2 * First post --- src/dumpstats.c | 104 +++- 1 file changed, 57 insertions(+), 47 deletions(-) diff --git a/src/dumpstats.c b/src/dumpstats.c index

[PATCH v2 4/4] MEDIUM: Differentiate between DRAIN and DRAIN (agent)

Differentiate between DRAIN and DRAIN (agent) when reporting stats. This is consistent with the distinction made between DOWN and DOWN (agent). Signed-off-by: Simon Horman ho...@verge.net.au --- v2 * Reworked to use SRV_STATS_STATE_* --- src/dumpstats.c | 7 ++- 1 file changed, 6 insertions

[PATCH v2 3/4] MEDIUM: Only report drain state in stats if server has SRV_ADMF_DRAIN set

=*. This patch makes stats reporting consistent in this regard. This patch does not alter the behaviour that if a server's weight is zero then its stats row is blue when accessed via HTML. This remains the case regardless of if the state is UP or DRAIN. Signed-off-by: Simon Horman ho...@verge.net.au

[PATCH v2 2/4] MEDIUM: Separate server state and colour in stats

distinguish between DRAIN states and DRAINING colours. Signed-off-by: Simon Horman ho...@verge.net.au --- v2 * First post --- src/dumpstats.c | 134 +++- 1 file changed, 83 insertions(+), 51 deletions(-) diff --git a/src/dumpstats.c b/src/dumpstats.c

[PATCH 0/2] Minor enhancements to drain state

=DRAIN,weight=* when reporting stats. 2. Differentiate between DRAIN and DRAIN (agent) The motivation here is to make DRAIN consistent with DOWN. Patches have been lightly tested. Simon Horman (2): MEDIUM: Only report drain state in stats if server has SRV_ADMF_DRAIN set MEDIUM

[PATCH 2/2] MEDIUM: Differentiate between DRAIN and DRAIN (agent)

Differentiate between DRAIN and DRAIN (agent) when reporting stats. This is consistent with the distinction made between DOWN and DOWN (agent). Signed-off-by: Simon Horman ho...@verge.net.au --- src/dumpstats.c | 21 ++--- 1 file changed, 14 insertions(+), 7 deletions(-) diff

[PATCH 1/2] MEDIUM: Only report drain state in stats if server has SRV_ADMF_DRAIN set

=*. This patch makes stats reporting consistent in this regard. Signed-off-by: Simon Horman ho...@verge.net.au --- src/dumpstats.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/dumpstats.c b/src/dumpstats.c index d82ce8538841..9f5a4349d231 100644 --- a/src/dumpstats.c +++ b

Re: Availability of HAProxy on Windows Server

I'm afraid Windows isn't a supported platform, please see http://www.haproxy.org/#plat On 26 March 2015 at 21:38, Abhijit Damle abhijit.da...@beca.com wrote: Hi, Do you have any version of HAProxy supported on Windows Server editions (server 2008, server 2012 etc). if so from

Re: Public Key for free Open souce install

On 28 February 2015 at 18:28, vad...@yahoo.com wrote: Hi, Where can I get a Key for free Open source installation, please let me have a link to it. (Of course, replace the tag YOURKEYHERE by the key that has been delivered to you.) HAProxy Technologies HAPEE public key import Packages

Re: [PATCH] BUG/MEDIUM: Do not consider an agent check as failed on L7 error

On Thu, Feb 26, 2015 at 07:09:25AM +0100, Willy Tarreau wrote: Hi Simon, On Thu, Feb 26, 2015 at 11:26:17AM +0900, Simon Horman wrote: As failure to connect to the agent check is not sufficient to mark it as failed it stands to reason that an L7 error shouldn't either. Without

[PATCH 2/2] MEDIUM: Allow suppression of email alerts by log level

configuration option to set the maximum level to notice or greater. email-alert level notice Signed-off-by: Simon Horman ho...@verge.net.au --- doc/configuration.txt | 36 ++-- include/proto/checks.h | 4 ++-- include/types/proxy.h | 3 +++ src/cfgparse.c

[PATCH 0/2] Allow suppression of email alerts by log level

configuration option to set the maximum level to notice or greater. email-alert level notice The first patch in the series provides a contextual dependency of the second patch. Simon Horman (2): LOW: Remove trailing '.' from email alert messages MEDIUM: Allow suppression of email

[PATCH 1/2] LOW: Remove trailing '.' from email alert messages

This removes the trailing '.' from both the header and the body of email alerts. The main motivation for this change is to make the format of email alerts generated from srv_set_stopped() consistent with those generated from set_server_check_status(). Signed-off-by: Simon Horman ho

Re: [PATCH/RFC 0/8] Email Alerts

On Tue, Feb 03, 2015 at 05:13:02PM +0100, Baptiste wrote: On Tue, Feb 3, 2015 at 4:59 PM, Pavlos Parissis pavlos.paris...@gmail.com wrote: On 01/02/2015 03:15 μμ, Willy Tarreau wrote: Hi Simon, On Fri, Jan 30, 2015 at 11:22:52AM +0900, Simon Horman wrote: Hi Willy, Hi All

[PATCH] MEDIUM: Document email alerts

Signed-off-by: Simon Horman ho...@verge.net.au --- doc/configuration.txt | 104 ++ 1 file changed, 104 insertions(+) diff --git a/doc/configuration.txt b/doc/configuration.txt index c829590..aa3f30f 100644 --- a/doc/configuration.txt +++ b/doc

Re: [PATCH/RFC 0/8] Email Alerts

Hi Willy, On Sun, Feb 01, 2015 at 03:15:27PM +0100, Willy Tarreau wrote: Hi Simon, On Fri, Jan 30, 2015 at 11:22:52AM +0900, Simon Horman wrote: Hi Willy, Hi All, the purpose of this email is to solicit feedback on an implementation of email alerts for haproxy the design of which

[PATCH/RFC 7/8] MEDIUM: Allow configuration of email alerts

This currently does nothing beyond parsing the configuration and storing in the proxy as there is no implementation of email alerts. Signed-off-by: Simon Horman ho...@verge.net.au --- include/types/mailers.h | 6 +-- include/types/proxy.h | 10 + src/cfgparse.c | 109

[PATCH/RFC 1/8] MEDIUM: Remove connect_chk

Remove connect_chk and instead call connect_proc_chk() and connect_conn_chk(). There no longer seems to be any value in having a wrapper function here. Signed-off-by: Simon Horman ho...@verge.net.au --- src/checks.c | 25 ++--- 1 file changed, 2 insertions(+), 23 deletions

[PATCH/RFC 4/8] MEDIUM: Move proto and addr fields struct check

-by: Simon Horman ho...@verge.net.au --- include/types/checks.h | 2 ++ include/types/server.h | 5 - src/checks.c | 14 +++--- src/server.c | 14 +++--- 4 files changed, 16 insertions(+), 19 deletions(-) diff --git a/include/types/checks.h b/include/types

[PATCH/RFC 6/8] MEDIUM: Add parsing of mailers section

As mailer and mailers structures and allow parsing of a mailers section into those structures. These structures will subsequently be freed as it is not yet possible to use reference them in the configuration. Signed-off-by: Simon Horman ho...@verge.net.au --- Makefile| 2

[PATCH/RFC 5/8] MEDIUM: Attach tcpcheck_rules to check

This is to allow checks to be established whose tcpcheck_rules are not those of its proxy. Signed-off-by: Simon Horman ho...@verge.net.au --- include/types/checks.h | 1 + src/checks.c | 34 +- src/server.c | 1 + 3 files changed, 19

[PATCH/RFC 2/8] MEDIUM: Refactor init_check and move to checks.c

Refactor init_check so that an error string is returned rather than alerts being printed by it. Also init_check to checks.c and provide a prototype to allow it to be used from multiple C files. Signed-off-by: Simon Horman ho...@verge.net.au --- include/proto/checks.h | 2 ++ src/checks.c

[PATCH/RFC 8/8] MEDIUM: Support sending email alerts

Signed-off-by: Simon Horman ho...@verge.net.au --- include/proto/checks.h | 2 + include/types/checks.h | 2 +- include/types/proxy.h | 18 ++- src/cfgparse.c | 26 ++-- src/checks.c | 321 + src/server.c | 1

[PATCH/RFC 0/8] Email Alerts

. For reference this patchset is available in git https://github.com/horms/haproxy devel/email-alert This patchset is based on the current mainline master branch: the 1.6 development branch. The current head commit there is 32602d2 (BUG/MINOR: checks: prevent http keep-alive with http-check expect). Simon

Re: [PATCH 1/2] BUG/MEDIUM: Do not set agent health to zero if server is disabled in config

On Thu, Jan 22, 2015 at 08:24:57PM +0100, Willy Tarreau wrote: Hi Simon, On Tue, Jan 20, 2015 at 01:22:38PM +0900, Simon Horman wrote: (...) This seems to have slipped through the cracks. I'm wondering if we could revisit it and the other patch in this series. Hmmm sorry for that. You

Re: [PATCH 1/2] BUG/MEDIUM: Do not set agent health to zero if server is disabled in config

Hi Willy, On Mon, Dec 01, 2014 at 09:18:05AM +0900, Simon Horman wrote: On Wed, Nov 12, 2014 at 05:11:27PM +0900, Simon Horman wrote: On Wed, Nov 12, 2014 at 08:22:05AM +0100, Willy Tarreau wrote: Hi Simon, On Wed, Nov 12, 2014 at 03:55:53PM +0900, Simon Horman wrote: disable

Re: [PATCH 1/2] BUG/MEDIUM: Do not set agent health to zero if server is disabled in config

On Wed, Nov 12, 2014 at 05:11:27PM +0900, Simon Horman wrote: On Wed, Nov 12, 2014 at 08:22:05AM +0100, Willy Tarreau wrote: Hi Simon, On Wed, Nov 12, 2014 at 03:55:53PM +0900, Simon Horman wrote: disable starts a server in the disabled state, however setting the health of an agent

Re: [PATCH 1/2] BUG/MEDIUM: Do not set agent health to zero if server is disabled in config

On Wed, Nov 12, 2014 at 08:22:05AM +0100, Willy Tarreau wrote: Hi Simon, On Wed, Nov 12, 2014 at 03:55:53PM +0900, Simon Horman wrote: disable starts a server in the disabled state, however setting the health of an agent implies that the agent is disabled as well as the server

Re: Problems with agent check

6618300e13 [1] Both checks and agent checks are using a common transport layer (xprt in struct check_common from this commit). IMHO, we should split the transport layer for each check, and enforce raw_sock for agent checks. I add Simon to the discussion, as he worked on it. Simon, do you

[PATCH 1/2] BUG/MEDIUM: Do not set agent health to zero if server is disabled in config

Signed-off-by: Simon Horman ho...@verge.net.au --- src/cfgparse.c | 1 - src/server.c | 1 - 2 files changed, 2 deletions(-) diff --git a/src/cfgparse.c b/src/cfgparse.c index 09a0fd3..820fbf4 100644 --- a/src/cfgparse.c +++ b/src/cfgparse.c @@ -6982,7 +6982,6 @@ out_uri_auth_compat

[PATCH 2/2] MEDIUM/BUG: Only explicitly report DOWN (agent) if the agent health is zero

by agent prior to reporting up). Note that DOWN (agent) may also be reported by a more generic conditional which immediately follows the code changed by this patch. Reported-by: Mark Brooks m...@loadbalancer.org Signed-off-by: Simon Horman ho...@verge.net.au --- src/dumpstats.c | 2 +- 1 file

[PATCH 0/2] Do not incorrectly report status as DOWN (agent)

Hi, this short series is intended to address to cases where the status of a backend is incorrectly reported as DOWN (agent). Simon Horman (2): BUG/MEDIUM: Do not set agent health to zero if server is disabled in config MEDIUM/BUG: Only explicitly report DOWN (agent) if the agent health

Re: Problem with external healthchecks and haproxy-ss-20140720

could do the same for checks in a backend section. Willy, Simon, is it OK for you ? After some thoughts, I'd like to suggest a new implementation. I tried to imagine in which use case sysadmins in my company would need the first listener address/port of the proxy but I couldn't find one

Re: Problem with external healthchecks and haproxy-ss-20140720

On Fri, Aug 15, 2014 at 09:12:56AM +0100, Malcolm Turnbull wrote: I agree as well.. :-). Our original specification was to match the way that ldirectord does its external health checks (so that the customer scripts are compatible). We could just change ldirectord to be compatible with the

single or many haproxy instances

on which way to go? Is there a recommended max number of haproxy instances per node/core? Thanks. -Simon

Re: Email Alert Proposal

On Tue, Jun 24, 2014 at 07:29:15AM +0200, Willy Tarreau wrote: Hi Simon, On Tue, Jun 24, 2014 at 09:15:13AM +0900, Simon Horman wrote: Hi Willy, Malcolm has asked me to open a discussion with you regarding adding email alerts to haproxy and that is the purpose of this email

[PATCH] BUG/MEDIUM: Consistently use 'check' in process_chk

I am not entirely sure that this is a bug, but it seems to me that it may cause a problem if there agent-check is configured and there is some kind of error making a connection for it. Signed-off-by: Simon Horman ho...@verge.net.au --- src/checks.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH] MEDIUM: Add external check

Add an external check which makes use of an external process to check the status of a server. --- v8 * Rebase onto v1.6-dev0 v7 * Manual Rebase * Make option external-check configuration parameter boolean * Add external-check command configuration parameter * Add external-check path

Re: [PATCH] BUG/MEDIUM: Consistently use 'check' in process_chk

On Fri, Jun 20, 2014 at 07:07:56AM +0200, Willy Tarreau wrote: On Fri, Jun 20, 2014 at 12:29:47PM +0900, Simon Horman wrote: I am not entirely sure that this is a bug, but it seems to me that it may cause a problem if there agent-check is configured and there is some kind of error making

Re: [PATCH] MEDIUM: Add external check

On Fri, Jun 20, 2014 at 07:10:55AM +0200, Willy Tarreau wrote: On Fri, Jun 20, 2014 at 12:30:16PM +0900, Simon Horman wrote: Add an external check which makes use of an external process to check the status of a server. --- v8 * Rebase onto v1.6-dev0 Looks fine, applied to 1.6

Re: [PATCH v8] MEDIUM: Add port_to_str helper

On Mon, Jun 16, 2014 at 10:11:10AM +0200, Willy Tarreau wrote: On Mon, Jun 16, 2014 at 09:39:41AM +0900, Simon Horman wrote: This helper is similar to addr_to_str but tries to convert the port rather than the address of a struct sockaddr_storage. This is in preparation for supporting

Re: [PATCH v7 1/3] MEDIUM: Add port_to_str helper

On Mon, Jun 16, 2014 at 08:55:52AM +0900, Simon Horman wrote: On Fri, Jun 13, 2014 at 06:39:18PM +0200, Willy Tarreau wrote: On Fri, Jun 13, 2014 at 04:18:15PM +0900, Simon Horman wrote: This helper is similar to addr_to_str but tries to convert the port rather than the address

[PATCH v8] MEDIUM: Add port_to_str helper

This helper is similar to addr_to_str but tries to convert the port rather than the address of a struct sockaddr_storage. This is in preparation for supporting an external agent check. Signed-off-by: Simon Horman ho...@verge.net.au -- v8 * Correct endian problem by calling ntohs(port) v7

  1   2   3   4   >