Re: Question on stats socket values

documentation of a library. >For example, I know I can use the Golang client’s runtime api to access the “Econ” value from the stats socket. Does this value only ever increase for a backend server, or will it be reset at some point? In this case, as you're concerned about *econ*, refer to the offic

Question on stats socket values

Hello, I have a question re: HAProxy’s stats socket. I would like to know how often / if their values are reset. Are they monotonically increasing, or will they be reset after some period of time if a backend server is not taking traffic? For example, I know I can use the Golang client’s

Re: show errors from stats socket

Hi Elias, On Mon, Sep 28, 2020 at 12:51:18PM +0200, Elias Abacioglu wrote: > Hi > > I'm trying to get details about some errors in one of my backends. > Looking at the stats, there are a bunch of errors per server. > However, when I try to get details about the errors via t

show errors from stats socket

Hi I'm trying to get details about some errors in one of my backends. Looking at the stats, there are a bunch of errors per server. However, when I try to get details about the errors via the stats socket. # echo "show errors -1" | socat stdio /var/lib/haproxy/stats.sock Total event

Stats socket set map errors out if key does not exist

Hi, As per the documentation ( https://cbonte.github.io/haproxy-dconv/1.8/configuration.html#4.2-http-request) stats socket set map should handle adding a new key as well as a updating an existing key, but my tests show otherwise echo "set map /somemap.txt abcKey abcValue" | socat stdi

Re: Is there a way to extract list of bound IPs via stats socket ?

On Fri, 1 Sep 2017 19:07:58 +0200, Willy Tarreau wrote: > On Fri, Sep 01, 2017 at 05:49:38PM +0200, Lukas Tribus wrote: > > Hello, > > > > > > Am 01.09.2017 um 15:46 schrieb Mariusz Gronczewski: > > > Hi, > > > > > > I've been working on a piece of code to announce IPs (via

Re: Is there a way to extract list of bound IPs via stats socket ?

On Fri, 1 Sep 2017 17:49:38 +0200, Lukas Tribus wrote: > Hello, > > > Am 01.09.2017 um 15:46 schrieb Mariusz Gronczewski: > > Hi, > > > > I've been working on a piece of code to announce IPs (via ExaBGP) only if: > > > > * HAProxy is running > > * HAProxy actually uses a given

Re: Is there a way to extract list of bound IPs via stats socket ?

On Fri, Sep 01, 2017 at 05:49:38PM +0200, Lukas Tribus wrote: > Hello, > > > Am 01.09.2017 um 15:46 schrieb Mariusz Gronczewski: > > Hi, > > > > I've been working on a piece of code to announce IPs (via ExaBGP) only if: > > > > * HAProxy is running > > * HAProxy actually uses a given IP > > * a

Re: Is there a way to extract list of bound IPs via stats socket ?

Hello, Am 01.09.2017 um 15:46 schrieb Mariusz Gronczewski: > Hi, > > I've been working on a piece of code to announce IPs (via ExaBGP) only if: > > * HAProxy is running > * HAProxy actually uses a given IP > * a frontend with given IP is up for few seconds. > > I could do that via lsof but

Is there a way to extract list of bound IPs via stats socket ?

(or, running config) via stats socket ? I found a way to do that with backend server IPs but I can't seem to find a way to do it for frontends. Cheers, Mariusz -- Mariusz Gronczewski, Administrator Efigence S. A. ul. Wołoska 9a, 02-583 Warszawa T: [+48] 22 380 13 13 F: [+48] 22 380 13 14 E

Re: in-house vulnerability scan vs. stats socket

methods, etc. > > The many requests, even though the request paths were not valid at the > stats socket, made for a DoS attack (with haproxy's CPU consumption > often pegging at 100% generating stats pages). > > Since it looks like the only valid stats socket requests are GETs >

RE: in-house vulnerability scan vs. stats socket

What scanner did you use? -Original Message- From: Jim Freeman [sovr...@gmail.com] Received: Monday, 19 Jun 2017, 3:36PM To: HAProxy [haproxy@formilux.org] Subject: in-house vulnerability scan vs. stats socket FWIW / FYI - # haproxy -v HA-Proxy version 1.5.18 2016/05/10 An in-house

in-house vulnerability scan vs. stats socket

FWIW / FYI - # haproxy -v HA-Proxy version 1.5.18 2016/05/10 An in-house vulnerability scanner found our haproxy stats sockets and started probing, sending bogus requests, HTTP_* methods, etc. The many requests, even though the request paths were not valid at the stats socket, made for a DoS

[PATCH v3 4/9] MEDIUM: mworker: try to guess the next stats socket to use with -x

In master worker mode, you can't specify the stats socket where you get your listeners FDs on a reload, because the command line of the re-exec is launched by the master. To solve the problem, when -x is found on the command line, its parameter is rewritten on a reexec with the first stats socket

[PATCH 4/9] MEDIUM: mworker: try to guess the next stats socket to use with -x

In master worker mode, you can't specify the stats socket where you get your listeners FDs on a reload, because the command line of the re-exec is launched by the master. To solve the problem, when -x is found on the command line, its parameter is rewritten on a reexec with the first stats socket

Re: server FQDN changes from stats socket + server-state file

On Tue, May 02, 2017 at 04:49:50PM +0200, Frederic Lecaille wrote: > Here is an update of my patch which integrates your fix. Now applied, thanks to you both! Willy

Re: server FQDN changes from stats socket + server-state file

:02 +0200 Subject: [PATCH] MINOR: server: cli: Add server FQDNs to server-state file and stats socket. This patch adds a new stats socket command to modify server FQDNs at run time. Its syntax: set server / fqdn This patch also adds FQDNs to server state file at the end of each line for

Re: server FQDN changes from stats socket + server-state file

Appart the bug, the new feature works smoothly! Great job, Fred @haproxy.com :p Baptiste

Re: server FQDN changes from stats socket + server-state file

On 05/02/2017 03:45 PM, Baptiste wrote: Here is a new patch version which takes into an account Baptiste remarks. Thank you again Baptiste. Hi Fred, Hello Baptiste, I gave a try to your code today and found a segfault at the next DNS request following the fqdn change. I

Re: server FQDN changes from stats socket + server-state file

> > >> Here is a new patch version which takes into an account Baptiste remarks. > > Thank you again Baptiste. > > Hi Fred, I gave a try to your code today and found a segfault at the next DNS request following the fqdn change. I attached a patch to this email to fix it, simply merge it into

Re: server FQDN changes from stats socket + server-state file

Please find attached to this mail a patch proposal which allows server FQDNs changes from stats socket. These FQDNs are also added to server-state file. Regards, Fred. A new version of this

Re: server FQDN changes from stats socket + server-state file

patch proposal which allows server FQDNs changes from stats socket. These FQDNs are also added to server-state file. Regards, Fred. A new version of this patch which fixes a memleak (server ho

Re: server FQDN changes from stats socket + server-state file

rote: >> >> On 04/27/2017 10:47 AM, Frederic Lecaille wrote: >> >> Hello HAProxy ML, >> >> Please find attached to this mail a patch proposal which allows >> server FQDNs changes from stats socket. >> >> These FQ

Re: server FQDN changes from stats socket + server-state file

tch proposal which allows server FQDNs changes from stats socket. These FQDNs are also added to server-state file. Regards, Fred. A new version of this patch which fixes a memleak (server hostname was strdup() both in srv_set_fqdn() and srv_alloc_dn

Re: server FQDN changes from stats socket + server-state file

On Thu, Apr 27, 2017 at 11:22 AM, Frederic Lecaille <flecai...@haproxy.com> wrote: > On 04/27/2017 10:47 AM, Frederic Lecaille wrote: > >> Hello HAProxy ML, >> >> Please find attached to this mail a patch proposal which allows >> server FQDNs changes from stat

Re: server FQDN changes from stats socket + server-state file

On 04/27/2017 10:47 AM, Frederic Lecaille wrote: Hello HAProxy ML, Please find attached to this mail a patch proposal which allows server FQDNs changes from stats socket. These FQDNs are also added to server-state file. Regards, Fred. A new version of this patch which fixes a memleak

server FQDN changes from stats socket + server-state file

Hello HAProxy ML, Please find attached to this mail a patch proposal which allows server FQDNs changes from stats socket. These FQDNs are also added to server-state file. Regards, Fred. >From f9c1001175d406a15414e893f11d6120cf22 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fr=C3=A9d=C3=A9

Re: Getting JSON encoded data from the stats socket.

Hi, On Mon, Nov 14, 2016 at 03:29:58PM +, Mirek Svoboda wrote: > What if we have the descriptions in the source code, serving as a single > source of truth, and generate the JSON schema file from the source code > upon build? ... or on the fly. That's what I was thinking as well. Ie "show

Re: Getting JSON encoded data from the stats socket.

Hi > > OK. So does this mean that a schema will have to be maintained by hand in > > parallel or will it be deduced from the dump ? I'm starting to be worried > > about something not being kept up to date if we have to maintain it, or > > causing a slow down in adoption of new stats entries. > >

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 wrote: > > Hi

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 of them ? I'm asking > > >

Re: Getting JSON encoded data from the stats socket.

Hi Simon, On Mon, Nov 14, 2016 at 09:09:21AM +0100, Simon Horman wrote: > I took a first pass at defining a schema. > > * The schema follows what is described on json-schema.org (or at least > tries to). Is this a suitable approach? I'll let others respond as I have no idea since I never need

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 schema could take a little

Re: Getting JSON encoded data from the stats socket.

Hi, On 16-11-10 16:56:33, Willy Tarreau wrote: > I removed you from the To in this response, but just as a hint we > generally recommend to keep people CCed since most of us subscribed > to lists have filters to automatically place them in the right box, > and some people may participate without

Re: Getting JSON encoded data from the stats socket.

On Thu, Nov 10, 2016 at 04:30:57PM +0100, ge...@riseup.net wrote: > (Please don't Cc: me, I'm subscribed to the list.) I removed you from the To in this response, but just as a hint we generally recommend to keep people CCed since most of us subscribed to lists have filters to automatically place

Re: Getting JSON encoded data from the stats socket.

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 schema could take a little time to get > a consensus on. I totally agree with you. I think the most difficult thing is

Re: Getting JSON encoded data from the stats socket.

(Please don't Cc: me, I'm subscribed to the list.) On 16-11-10 16:12:31, Willy Tarreau wrote: > That's cool! > > The only thing is that I don't want to delay the release only for this, > and at the same time I'm pretty sure it's possible to do something which > will not impact existing code

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 kindly offered to > > take a look at this

Re: Getting JSON encoded data from the stats socket.

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 kindly offered to > take a look at this again. That's cool! The only thing is that I don't want to delay the release

Re: Getting JSON encoded data from the stats socket.

On Thu, 10 Nov 2016, at 13:53, Malcolm Turnbull wrote: > Georg, > > That's a timely reminder thanks: > I just had another chat with Simon Horman who has kindly offered to > take a look at this again. Sounds great! I'm very interested in logging this continually via chrooted unix socket, into

Re: Getting JSON encoded data from the stats socket.

wondered if we could start a discussion about the possibility of >> having the stats socket return stats data in JSON format. > > After the discussion we had in July, I'm wondering what's the current > status regarding this topic? > > Thanks and all the best, > Georg -- Rega

Re: Getting JSON encoded data from the stats socket.

Hi all, On 16-07-05 10:05:13, Mark Brookes wrote: > I wondered if we could start a discussion about the possibility of > having the stats socket return stats data in JSON format. After the discussion we had in July, I'm wondering what's the current status regarding this topic? Thanks a

Re: Getting JSON encoded data from the stats socket.

Hi, On 16-07-26 21:47:55, Willy Tarreau wrote: > I'd like to wait for other people to have the time to participate to > this discussion, I know that some people are very careful about the > relevance and accuracy of the stats, some people may want to report > other suggestions. I can't add that

Re: Getting JSON encoded data from the stats socket.

On Tue, Jul 26, 2016 at 09:06:05PM +0200, Pavlos Parissis wrote: > > You probably have not looked at the output of "show stats typed", it > > gives you the nature of each value letting you know how to aggregate > > them (min, max, avg, sum, pick any, etc). > > > > I have seen it but it isn't

Re: Getting JSON encoded data from the stats socket.

On 26/07/2016 06:56 μμ, Willy Tarreau wrote: > On Tue, Jul 26, 2016 at 05:51:08PM +0200, Pavlos Parissis wrote: >> In all my setups I have nbproc > 1 and after a lot of changes and on how I >> aggregate HAProxy >> stats and what most people want to see on graphs, I came up that with >> something

Re: Getting JSON encoded data from the stats socket.

On Tue, Jul 26, 2016 at 05:51:08PM +0200, Pavlos Parissis wrote: > In all my setups I have nbproc > 1 and after a lot of changes and on how I > aggregate HAProxy > stats and what most people want to see on graphs, I came up that with > something like the following: > > { > "frontend": { >

Re: Getting JSON encoded data from the stats socket.

On 26/07/2016 03:30 μμ, Willy Tarreau wrote: > Hi Pavlos! > > On Tue, Jul 26, 2016 at 03:23:01PM +0200, Pavlos Parissis wrote: >> Here is a suggestion { "frontend": { "www.haproxy.org": { "bin": >> "", "lbtot": >> "55", ... }, "www.haproxy.com": { "bin": "", "lbtot":

Re: Getting JSON encoded data from the stats socket.

On Tue, Jul 26, 2016 at 03:06:35PM +0100, Mark Brookes wrote: > Could we perhaps group by the node then process_num then? > {nodename:value: > {pid: pid1: { > haproxy: { > Uptime_sec:100, > PoolFailed:1 > } > stats: { "frontend": { >

Re: Getting JSON encoded data from the stats socket.

Could we perhaps group by the node then process_num then? {nodename:value: {pid: pid1: { haproxy: { Uptime_sec:100, PoolFailed:1 } stats: { "frontend": { "www.haproxy.org": { "bin": "", "lbtot":

Re: Getting JSON encoded data from the stats socket.

Hi Pavlos! On Tue, Jul 26, 2016 at 03:23:01PM +0200, Pavlos Parissis wrote: > Here is a suggestion > { > "frontend": { > "www.haproxy.org": { > "bin": "", > "lbtot": "55", > ... > }, > "www.haproxy.com": { >

Re: Getting JSON encoded data from the stats socket.

On 26/07/2016 03:08 μμ, Willy Tarreau wrote: > On Tue, Jul 26, 2016 at 02:05:56PM +0100, Mark Brookes wrote: >>> So for sure I definitely support this proposal :-) >> >> Thats great news. Do you have a JSON structure in mind? >> Or would you like me to come up with something? > > I'm probably the

Re: Getting JSON encoded data from the stats socket.

On Tue, Jul 26, 2016 at 02:05:56PM +0100, Mark Brookes wrote: > >So for sure I definitely support this proposal :-) > > Thats great news. Do you have a JSON structure in mind? > Or would you like me to come up with something? I'm probably the worst ever person to suggest a JSON structure. If you

Re: Getting JSON encoded data from the stats socket.

Mark Brookes wrote: >> Hi Willy/All >> >> I wondered if we could start a discussion about the possibility of >> having the stats socket return stats data in JSON format. >> >> Im primarily interested in the data that is returned by issuing a >> 'sho

Re: Getting JSON encoded data from the stats socket.

Hi Mark, On Tue, Jul 05, 2016 at 10:05:13AM +0100, Mark Brookes wrote: > Hi Willy/All > > I wondered if we could start a discussion about the possibility of > having the stats socket return stats data in JSON format. > > Im primarily interested in the data that is returned by

Getting JSON encoded data from the stats socket.

Hi Willy/All I wondered if we could start a discussion about the possibility of having the stats socket return stats data in JSON format. Im primarily interested in the data that is returned by issuing a 'show stat' which is normally returned as a csv. I wont go into specifics as to how

Re: Setting weight through stats socket, nbproc > 1

Hi, On 05/31/2016 11:55 AM, Unknown User wrote: > I am running haproxy with nbproc 3. (I know its not supported, but i > want to use more than 1 cpu with haproxy) Don't worry, it still works really well :) > The following is my config related to the stats socket > > daemon

Setting weight through stats socket, nbproc > 1

I am running haproxy with nbproc 3. (I know its not supported, but i want to use more than 1 cpu with haproxy) The following is my config related to the stats socket daemon nbproc 3 pidfile /var/run/hapxy.pid # Does not work with nbproc >1 stats socket /var/

[PATCH] DOC: specify that stats socket doc (section 9.2) is in management

Commit 44aed90ce102c4136a5eda66d541f6fa79e141e8 moved the stats socket documentation from config to management but the remaining references to section 9.2 were not updated; improve it to be less confusing. Signed-off-by: Kevin Decherf <ke...@kdecherf.com> --- doc/configuration.txt | 5 ++

Re: [PATCH] DOC: specify that stats socket doc (section 9.2) is in management

On Tue, Oct 13, 2015 at 11:26:44PM +0200, Kevin Decherf wrote: > Commit 44aed90ce102c4136a5eda66d541f6fa79e141e8 moved the stats socket > documentation from config to management but the remaining references to > section 9.2 were not updated; improve it to be less confusing. Ah cra

Re: Interactive stats socket broken on master

On Mon, Oct 12, 2015 at 12:06 AM, Willy Tarreau <w...@1wt.eu> wrote: > On Sat, Oct 10, 2015 at 08:55:44PM -0500, Andrew Hayworth wrote: >> Bump - >> >> I don't mind maintaining my own HAProxy package, but it seems bad to >> release a major version with the int

Re: Interactive stats socket broken on master

On Sun, Oct 11, 2015 at 5:06 PM, Willy Tarreau wrote: > > Has anyone else tested it ? Since the beginning of the thread I must > confess it's unclear to me as Jesse reported the issue, you said that > your patch works for you then Jesse asks whether we should merge it. > Jesse, have

Re: Interactive stats socket broken on master

On Mon, Oct 12, 2015 at 12:33:39PM -0500, Jesse Hathaway wrote: > On Sun, Oct 11, 2015 at 5:06 PM, Willy Tarreau wrote: > > > > Has anyone else tested it ? Since the beginning of the thread I must > > confess it's unclear to me as Jesse reported the issue, you said that > > your

Re: Interactive stats socket broken on master

On Sat, Oct 10, 2015 at 08:55:44PM -0500, Andrew Hayworth wrote: > Bump - > > I don't mind maintaining my own HAProxy package, but it seems bad to > release a major version with the interactive stats socket broken. Any > thoughts on the patch? Has anyone else tested it ? Sinc

Re: Interactive stats socket broken on master

Bump - I don't mind maintaining my own HAProxy package, but it seems bad to release a major version with the interactive stats socket broken. Any thoughts on the patch? On Tue, Oct 6, 2015 at 9:29 AM, Jesse Hathaway <je...@mbuki-mvuki.org> wrote: > On Fri, Oct 2, 2015 at 10:24 A

Re: Interactive stats socket broken on master

On Fri, Oct 2, 2015 at 10:24 AM, Andrew Hayworth wrote:> > Attached is a patch that fixes the issue for me. Willy, any thoughts on merging this patch into 1.6?

Re: Interactive stats socket broken on master

Hi all - On Thu, Oct 1, 2015 at 8:55 AM, Jesse Hathaway <je...@mbuki-mvuki.org> wrote: > It appears the following commit broke the interactive stats socket. > When this commit is applied the stats socket disconnects after typing > prompt and hitting enter. Attached is a p

Interactive stats socket broken on master

It appears the following commit broke the interactive stats socket. When this commit is applied the stats socket disconnects after typing prompt and hitting enter. This breaks applications such as hatop. We found the breaking commit using git bisect. Please let me know if I can help debug

Re: stats socket over TCP - dangerous?

On Mon, Sep 21, 2015 at 10:34:17PM +, Thrawn wrote: > > Does this mean that the TCP port is dangerous, or that the multiple > > instances of the socket is dangerous?? > > What is the danger with it? > > I believe the danger is that it may be externally visible, allowing outsiders > to start

Re: stats socket over TCP - dangerous?

The loopback address is a good idea for allowing communication locally, with software that can't use Unix sockets, like Java. -- ✉ Eduard Martinescu | ✆ (585) 708-9685 | [image: http://www.salsalabs.com] - ignite

Re: stats socket over TCP - dangerous?

> software that can't use Unix sockets, like Java Er...that's generally true (although there are libraries like junixsocket), and not to put you off, but why do you have Java talking to the HAProxy admin socket?

Re: stats socket over TCP - dangerous?

> Does this mean that the TCP port is dangerous, or that the multiple > instances of the socket is dangerous?? > What is the danger with it? I believe the danger is that it may be externally visible, allowing outsiders to start and stop your servers, add new backends and redirect traffic to

stats socket over TCP - dangerous?

Hi, I am looking at pulling stuff out of the stats socket, but the documentation is unclear on this point: It is also possible to add multiple instances of the stats socket by repeating the line, and make them listen to a TCP port instead of a UNIX socket. This is never done by default because

Session counter doesnt increase for stats socket

Hi, I have several haproxy installations running on HAProxy version 1.5.4, released 2014/09/02 (debian packet) and I see no counting up on the stats socket session counter. The Bytes-counter count up on every reload, but the sessions total stay and don't get updated on every reload (as I

Re: Client certs on tcp and securing stats socket

with a regular HTTP backend instead of the stats socket? That is something that should work and you could use to verify that your certs are working correctly... Cheers, Conrad Hi Donovan, You should have find some answers here: http://blog.haproxy.com/2012/10/03/ssl-client-certificate-management

Re: Client certs on tcp and securing stats socket

. But I am curious about what's going on. D On 7/24/14 7:00 PM, Conrad Hoffmann con...@soundcloud.com wrote: Hey Donovan, I never used client certificates in haproxy, but have you tried the setup with a regular HTTP backend instead of the stats socket? That is something that should work and you

Re: Client certs on tcp and securing stats socket

Hey Donovan, I never used client certificates in haproxy, but have you tried the setup with a regular HTTP backend instead of the stats socket? That is something that should work and you could use to verify that your certs are working correctly... Cheers, Conrad On 07/24/2014 09:36 PM, Meyers

Client certs on tcp and securing stats socket

Hi all, First of all, thanks again and always for the great work and an excellent product. I'm looking for a secure way to communicate with the haproxy stats socket for remote management of haproxy (without ssh), preferably without running some extra API service or anything. I love that 1.5

Stats Socket

Developers, Is anyone working on on a feature to make the stats socket more deterministic or sane. As is documented in 1.5 any haproxy instance may respond on the stat socket file. I would like to see only the most recent instance of haproxy respond to the stats socket file and an option to make

Re: Stats Socket

Hello Daniel, On 07/03/2014 12:06 AM, Daniel Schultze wrote: Developers, Is anyone working on on a feature to make the stats socket more deterministic or sane. As is documented in 1.5 any haproxy instance may respond on the stat socket file. I would like to see only the most recent instance

Re: Haproxy stats socket with nbproc1

So what is the current behavior? Does the stats socket function with nbproc 1, or will it only modify one of the two processes if you drain / disable a server, etc.) Russell

RE: Haproxy stats socket with nbproc1

Hi! So what is the current behavior? Does the stats socket function with nbproc 1 No. or will it only modify one of the two processes if you drain / disable a server, etc.) Yes, it will only modify the process where the stats process runs on, so in other words the behavior

Re: about stats socket per process

On Mon, Sep 30, 2013 at 04:07:00PM +0400, Avatar wrote: I would like to ask you about any perspective in implementation statistics socket at each process in nbproc. Do you have any plans to work on it? It was started a few months ago but ended in a maelstorm where many other things had to be

about stats socket per process

I would like to ask you about any perspective in implementation statistics socket at each process in nbproc. Do you have any plans to work on it? Thanks. -- The more you know, the less you need. Rgrds, Pavel Morozov

RE: Remotely accessible stats socket and HATop

Hi Willy, Ref: Since a recent enough version, maybe dev16 or 17, you can even have your stats socket listen to TCP directly :-) How is that done? I'm struggling to find it in the docs. That would be much cleaner than using socat! Simon -Original Message- From: Willy Tarreau [mailto:w

Re: Remotely accessible stats socket and HATop

Hey, Can you give a try to stats socket ipv4@a.b.c.d:1234 You can even cipher the connection and even use a client certificate to allow people using the socket. Baptiste Baptiste On Tue, Jul 9, 2013 at 10:48 AM, Simon Green si...@wirehive.net wrote: Hi Willy, Ref: Since a recent enough

Re: Remotely accessible stats socket and HATop

Hi Simon, On Sun, Jun 23, 2013 at 10:17:29PM +, Simon Green wrote: Hi List, We had a requirement to be able to put servers in and out of maint mode remotely from a script. To facilitate this we exposed the stats socket using socat, and wrote an init script to do that for us: https

Per process stats socket

Hi! Actually, the Unix stats socket is global. It is possible to pin it to some processes, but it is not possible to have one Unix socket per process. Has someone already tried to add the appropriate code to declare several Unix sockets? Thanks. -- printk(Entering UltraSMPenguin Mode...\n

Re: Per process stats socket

Hi Vincent, On Tue, Feb 26, 2013 at 10:19:48AM +0100, Vincent Bernat wrote: Hi! Actually, the Unix stats socket is global. It is possible to pin it to some processes, but it is not possible to have one Unix socket per process. Has someone already tried to add the appropriate code

'stats socket' doesn't accept 'level' parameter

' i get command not found, followed by a list of possible commands which only has 'list info' in it. The error on startup when i include the 'level' parameter: [ALERT] 302/195316 (16456) : parsing [/etc/haproxy.cfg:4] : 'stats socket' only supports 'user', 'uid', 'group', 'gid', and 'mode

Re: Haproxy stats socket with nbproc1

On Wed, Jul 25, 2012 at 05:14:38PM +0200, Stojan Rancic (Iprom) wrote: On 25.7.2012 15:12, Vincent Bernat wrote: ??? 25 juillet 2012 12:00 CEST, Stojan Rancic (Iprom) sto...@iprom.si : is it possible to create a stats socket (or per-process stats socket) when haproxy is configured

Re: Haproxy stats socket with nbproc1

❦ 25 juillet 2012 12:00 CEST, Stojan Rancic (Iprom) sto...@iprom.si : is it possible to create a stats socket (or per-process stats socket) when haproxy is configured with 'nbproc=2' or higher ? Hi! I am unsure if this is possible with a socket. However, you can do it for the web interface

Re: Haproxy stats socket with nbproc1

On 25.7.2012 15:12, Vincent Bernat wrote: ❦ 25 juillet 2012 12:00 CEST, Stojan Rancic (Iprom) sto...@iprom.si : is it possible to create a stats socket (or per-process stats socket) when haproxy is configured with 'nbproc=2' or higher ? Hi! I am unsure if this is possible with a socket

Re: [PATCH] Avoid truncation of the path used for the stats socket

On Thu, Jan 20, 2011 at 10:44:03AM +0100, Andreas Kohn wrote: On Wed, 2011-01-19 at 20:38 +0100, Andreas Kohn wrote: Hi, while working further on the changes to allow for dynamic adding/removing of backend servers we noticed a potential problem: the path given for the 'stats socket

Re: [PATCH] Avoid truncation of the path used for the stats socket

On Wed, 2011-01-19 at 20:38 +0100, Andreas Kohn wrote: Hi, while working further on the changes to allow for dynamic adding/removing of backend servers we noticed a potential problem: the path given for the 'stats socket' global option may get truncated when copying

[PATCH] Avoid truncation of the path used for the stats socket

Hi, while working further on the changes to allow for dynamic adding/removing of backend servers we noticed a potential problem: the path given for the 'stats socket' global option may get truncated when copying it into the sockaddr_un.sun_path field. Attached patch checks the length

HAProxy init and stats socket script

Hi folks. For our company's convenience, we prefer to have our HAProxy unit script also allow us to talk to the stats socket. We also do a couple other things, like show connections with a status argument. Perhaps you can use it too. Code and readme here: https://github.com/flores/haproxyctl

Re: stats socket issues with concurrent accesses

Le Dimanche 14 Mars 2010 19:58:08, Willy Tarreau a écrit : Here's the patch I'm going to merge. I did a bunch of tests on it (both unix and tcp) and it appears OK. Oh nice ! It works well, I couldn't reproduce the problem with 10 loops running for more than 15 minutes. Thanks. -- Cyril Bonté

stats socket issues with concurrent accesses

these ones) but there's no error with 1.3.15.x versions (tested with 1.3.15.12, 1.3.15.11, 1.3.15.10 and 1.3.15.7). Maybe this can remind you some modifications of code. To reproduce the issue : - a simple configuration file : global stats socket /tmp/haproxy.socket listen dummy :1

Re: stats socket issues with concurrent accesses

Hi Cyril, On Fri, Mar 12, 2010 at 05:03:15PM +0100, Cyril Bonté wrote: Hi Willy, Our monitoring scripts use the unix socket to get haproxy's status. Sometimes they detect haproxy DOWN when it's not really the case. Do you know how much time it takes to observe it ? I'm currently running it

Re: stats socket issues with concurrent accesses

Le Vendredi 12 Mars 2010 20:17:14, Willy Tarreau a écrit : Hi Cyril, On Fri, Mar 12, 2010 at 05:03:15PM +0100, Cyril Bonté wrote: Hi Willy, Our monitoring scripts use the unix socket to get haproxy's status. Sometimes they detect haproxy DOWN when it's not really the case. Do you

  1   2   >