unfortunately, for now you'll have to repeat the acl in each frontend :)
Baptiste
On Tue, Apr 7, 2015 at 9:14 PM, Florin Andrei wrote:
> I have a few ACLs that are identical for several frontends. I tried to
> define the ACLs in the defaults section, but I got an error (quote at the
> end).
>
>
Hi haproxy@formilux.org
I'd like to connect with you on LinkedIn.am a new buyer
Yusuf Alim
Manager at
KAHN TRADING CO. LLC | DUBAI
popular
On 09/04/2015 02:52 μμ, Dieter van Zeder wrote:
> Here's the the stripped-down configuration. Http-server-close is required in
> order to use leastconn. The frontend actually contains various acl rules,
> thus mode http.
>
I had a look at the doc and it isn't mentioned that http-server-close i
I think you want ACL-driven "stats scope" statements, which don't
exist to the best of my knowledge.
In your case, rather than open a bunch of different ports, I'd give
people different FQDNs to hit, and point a wildcard DNS record at a
single port 80. (Well, a :443 with TLS, if I were doing it, b
Hi, Jonathan.
Thank you for your very fast feedback: I realize that I could better
explain my question.
One configuration I could use, is to add be some "listen" sections like
these...
listen stats81 XX.XX.XX.XX:81
mode http
option httplog
compression algo gzip
stats scope F
Hi all.
I currently give access to the stats page using a simple profiling by groups
. amministratori that have admin access to everything
. readonly that have no admin acces to everything
All users see the full set of "listen", "frontend" and "backend" sections.
userlist stats-auth
Here's the the stripped-down configuration. Http-server-close is required in
order to use leastconn. The frontend actually contains various acl rules, thus
mode http.
Thank you!
Dieter
defaults
option abortonclose
balance leastconn
backend apache
mode http
Hi Simon!
On Thu, Apr 09, 2015 at 03:47:13PM +0900, Simon Horman wrote:
> There are some similarities between a weight of zero and the
> administratively set drain state: both allow existing connections
> to continue while not accepting any new ones.
>
> However, when reporting a server state gen
Hi Willy -
Apologies if this comes through multiple times; I'm having some mail
difficulties.
On Tue, Apr 7, 2015 at 7:11 PM, Willy Tarreau wrote:
> Just a question, did you find any benefit in doing it with a new tag
> compared to %[path] ? It may just be a matter of convenience, I'm just
> won
Greetings, I hope the rewrite from C->Lua is going well...
I'm looking to trace down a weird scenario that might be a bug. We're
running: 1.5.2. Our backend is configured w/ a 500ms timeout queue and we
consistent hash on uri for load balancing.
For requests logged as termination 'SQ' that trigge
Hi Cyrill,
Thanks for the update. Please find the attached configuration. Also please
respond to below my queries.
In our configuration client time out set as 50sec. What will be the result
if the user remain inactive more than 50sec?
lets say a user hits goes to App1 server. if user remains a
Willy / Simon,
I think I've got a bit confused myself -
I've just installed the patches and tested and it fixes the issues we
seeing with HAProxy getting stuck in DRAIN mode when the agent
temporarily responds with 0% idle.
i.e. when the load on the server decreases HAProxy should
automatically s
Hello
That's an error from tomcat?
Up the nofiles in etc security limits is normal way to do that
Neil
On 9 Apr 2015 18:50, "ballu balram" wrote:
> Hi,
>After installing haproxy in ubuntu i get error ;-
>
> *29-Mar-2015 06:47:43.963 SEVERE [http-nio-9191-Acceptor-0]
> org.apache.tomcat.ut
On 09/04/2015 02:11 μμ, Dieter van Zeder wrote:
> It's not about idle connections, it's about connections closed by the client
> before the server fully sent the response. I have an apache module which can
> detect client disconnects and then stops processing. Having haproxy before
> those serv
Have you looked at "stats scope"?
https://cbonte.github.io/haproxy-dconv/configuration-1.5.html#stats%20scope
Jonathan
It's not about idle connections, it's about connections closed by the client
before the server fully sent the response. I have an apache module which can
detect client disconnects and then stops processing. Having haproxy before
those servers, a process keeps running, even though the client has
Hi Klavs,
Please give a try to the configuration below:
frontend nocache
mode http
..
option httplog
option accept-invalid-http-request
stick-table type ip size 100k expire 30s store conn_cur
tcp-request inspect-delay 5s
tcp-request content accept if HTTP
tcp-request content trac
Hi,
After installing haproxy in ubuntu i get error ;-
*29-Mar-2015 06:47:43.963 SEVERE [http-nio-9191-Acceptor-0]
org.apache.tomcat.util.net.NioEndpoint$Acceptor.run Socket accept failed*
* java.io.IOException: Too many open files*
*at sun.nio.ch.ServerSocketChannelImpl.accept0(Native
Hi Malcolm,
On Thu, Apr 09, 2015 at 02:31:16PM +0100, Malcolm Turnbull wrote:
> Willy / Simon,
>
> I think I've got a bit confused myself -
>
> I've just installed the patches and tested and it fixes the issues we
> seeing with HAProxy getting stuck in DRAIN mode when the agent
> temporarily res
--==70534229969561414=Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Si no puedes ver bien esta newsletter haz click [aquÃ
](http://gerentesquality.acmtrk.com/envio/ver/75938/ec18d17e-de3b-11e4-bf3c-0050569a455d/3aed88d8-decf-
Hi all -
A bit of lunchtime playing around today has exposed the fact that a
"stats uri" in a defaults section has no effect on backends to which
the defaults section /should/ apply. Stats-serving backends only obey
the compile-time default ("/haproxy?stats") in my tests, until an
explicit "stats
Hi David,
If you're in SQ state, it means the request never reached a server, so
you can't have any response header value.
Baptiste
On Thu, Apr 9, 2015 at 11:11 PM, David Birdsong
wrote:
> Greetings, I hope the rewrite from C->Lua is going well...
>
> I'm looking to trace down a weird scenario
On 09/04/2015 12:52 μμ, Dieter van Zeder wrote:
> Hi there, is it possible to forward packets indicating a client
> disconnect, with haproxy running in http mode? The webserver is able to
> cancel long running requests, but the disconnect cannot be detected at
> the backend.
>
I don't quite under
On Thu, Apr 9, 2015 at 7:03 AM, Jonathan Matthews
wrote:
> Hi all -
>
> A bit of lunchtime playing around today has exposed the fact that a
> "stats uri" in a defaults section has no effect on backends to which
> the defaults section /should/ apply. Stats-serving backends only obey
> the compile-
Hi there, is it possible to forward packets indicating a client disconnect, with haproxy running in http mode? The webserver is able to cancel long running requests, but the disconnect cannot be detected at the backend.Kind regardsDieter
Haproxy closes the connection with an RST.
Baptiste
Le 9 avr. 2015 16:54, "Pavlos Parissis" a
écrit :
> On 09/04/2015 02:52 μμ, Dieter van Zeder wrote:
> > Here's the the stripped-down configuration. Http-server-close is
> required in order to use leastconn. The frontend actually contains vario
26 matches
Mail list logo