Des problèmes pour lire cet e-mail? Cliquez ici 15 EUROS OFFERTS* DÈS 100
EUROS D’ACHAT EXCLUSIVEMENT SUR IKKS.COM AVEC LE CODE : LUCKY15
EXPLORE SUMMER 16 IKKS COLLECTIONS FEMME HOMME ENFANT STORE LOCATOR ONLINE
STORE FOLLOW US SE DÉSINSCRIRE CONTACTEZ-NOUS MENTIONS
I am trying to stop backend health check error messages from being logged to
the system console.
I have tried using "no option log-health-checks” in my configuration
defaults
log global
no option log-health-checks
mode http
option dontlognull
But I am still seeing error
Hi James and Baptist,
Le 04/05/2016 21:21, James Brown a écrit :
(gentle bump)
On Mon, Apr 25, 2016 at 11:36 AM, James Brown wrote:
Here's the top of the file. None of the backends override the
load-server-state-from-file setting that's made in `defaults`. There
are 106
(gentle bump)
On Mon, Apr 25, 2016 at 11:36 AM, James Brown wrote:
> Here's the top of the file. None of the backends override the
> load-server-state-from-file setting that's made in `defaults`. There
> are 106 backends defined.
>
>
> global
> log ${LOG_DGRAM_SYSLOG}
Unsubscribe
Kind regards,
Steven Iveson
This is a secure ProtonMail account.
Hello,
I described the case haproxy->application->haproxy.
My preferred behavior would be that the header is set only if it is not
present already.
Our goal is tracing requests through our whole stack. This can be for
example
Haproxy --> Varnish --> Haproxy --> Application --> Backend
We
Aleksey Maltzev writes:
>> Hi Aleksey,
>>
>> Well, if I were you I would make the stats socket listening on a
>> private IP address and run the command over the network to both
>> HAProxy servers.
>>
>> Baptiste
>>
>>
>
> Hi, Baptiste
>
> If I reload on one server?
> Then the
7 matches
Mail list logo