Re: [PATCH 2/2] MEDIUM: checks: provide environment variables to the external checks

Hi Cyril, I'm fine with applying your series except a minor detail to fix here : On Sun, Nov 30, 2014 at 11:51:09PM +0100, Cyril Bonté wrote: > +static int external_check_add_env(struct check *check, const char *envname, > const char *value, int *idx) > +{ > + if (*idx % EXTCHECK_ENV_ROOM ==

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 > > > o

ROHNER chaussettes sports d'hiver -40

Version en ligne Ajouter nous à votre carnet d’adresses LA KOURSE AUX BONS PLANS Vente du Lundi 1er Décembre Chaussettes sports d'hiver -40% à partir de 5,94€-40%Durée : 48H BIENTÔT Ouverture Mardi 02/12 Textile et accessoires à partir de 3.90€Jusqu'à -70%Durée : 48H E

Re: [PATCH 2/2] MEDIUM: checks: provide environment variables to the external checks

Hi all, this one is more to open the discussion than to be applied as is. But if it's ok to everyone, let's apply it ;-) It is also to revive this work, because it's something I started maybe 2 monthes ago but I couldn't find time to rework on it until now... Once it's OK, I'll work on the do

[PATCH 2/2] MEDIUM: checks: provide environment variables to the external checks

The external command accepted 4 arguments, some with the value "NOT_USED" when not applicable. In order to make the exernal command more generic, this patch also provides the values in environment variables. This allows to provide more information. Currently, the supported environment variables ar

[PATCH 1/2] MINOR: checks: allow external checks in backend sections

Previously, external checks required to find at least one listener in order to pass the and arguments to the external script. It prevented from declaring external checks in backend sections and haproxy rejected the configuration. The listener is now optional and values "NOT_USED" are passed if n

A minor bug in documentation ("show stat") and a request to add another metric there

Hi, The documentation states: stot [LFBS]: cumulative number of connections The issue is that it's a "cumulative number of *SESSIONS*". And the actual value of cumulative number of connections is not available in CSV "show stat" output at all. It's only available in the web UI. Could you please

Re: http-keep-alive with SSL backend

On 30/11/2014 01:17 μμ, Cyril Bonté wrote: > > Hi again Sachin, > > Le 30/11/2014 13:01, Sachin Shetty a écrit : >> Thanks Cyril, but no luck, I still see no connection reuse. For every new >> connection from the same client, haproxy make a new connection to the >> server and terminates it right

Re: Better understanding of nbproc vs distributing interrupts for cpu load management

On 28/11/2014 05:19 μμ, Lukas Tribus wrote: > Hi, > > >> you're right. >> If you need to scale *a lot* your SSL processing capacity in HAProxy, >> you must use multiple processes. >> That said, multiproc model has some counter parts (stats, server >> status, health checks are local to each proces

Re: Better understanding of nbproc vs distributing interrupts for cpu load management

On 28/11/2014 01:19 μμ, Baptiste wrote: > On Wed, Nov 26, 2014 at 9:48 PM, Pavlos Parissis > wrote: >> On 25/11/2014 07:08 μμ, Lukas Tribus wrote: Hi, > > Thanks for your reply. We have tried this approach and while >>> it gives > some benefit, the haproxy process itself > remains cpu-bound,

Re: add response header based on presence of request header

On 28/11/2014 02:44 μμ, Pavlos Parissis wrote: > Hi, > > I want HAProxy to add a response header if request includes a specific > header. I implemented the logic [1] but I get the following > > parsing [/etc/haproxy/haproxy.cfg:77] : acl 'lb_debug' will never match > because it only involves key

Re: http-keep-alive with SSL backend

Thanks Cyril, appreciate your help on this. I will take this up internally on how we could workaround it. Thanks again. Thanks Sachin On 11/30/14 5:47 PM, "Cyril Bonté" wrote: > >Hi again Sachin, > >Le 30/11/2014 13:01, Sachin Shetty a écrit : >> Thanks Cyril, but no luck, I still see no conne

Re: http-keep-alive with SSL backend

Hi again Sachin, Le 30/11/2014 13:01, Sachin Shetty a écrit : Thanks Cyril, but no luck, I still see no connection reuse. For every new connection from the same client, haproxy make a new connection to the server and terminates it right after. Then, ensure that it can't be due to a explicit b

Re: http-keep-alive with SSL backend

Thanks Cyril, but no luck, I still see no connection reuse. For every new connection from the same client, haproxy make a new connection to the server and terminates it right after. Lukas, as per the documentation, the 1.5 dev version does support server side pooling. http://cbonte.github.io/hapr

Re: http-keep-alive with SSL backend

Hi all, Le 30/11/2014 11:54, Lukas Tribus a écrit : Hi Sachin, Hi, We have SSL backends which are remote, so we want to use http-keep-alive to pool connections Connection pooling/multiplexing is simply not (yet) supported. Its is therefor expected behavior that 1 frontend connection equals

Boss Capital

Hi there, My name is David and I have personally been working with Boss Capital Trading for quite some time. They are very well reviewed online and have excellent customer service. If you are interested in becoming a binary trader please click the following link to start trading today! It is g

Re: http-keep-alive with SSL backend

Hi Sachin, > Hi, > > We have SSL backends which are remote, so we want to > use http-keep-alive to pool connections Connection pooling/multiplexing is simply not (yet) supported. Its is therefor expected behavior that 1 frontend connection equals 1 backend connection. Regards, Lukas