Hi Willy,
Le 02/03/2018 à 06:32, Willy Tarreau a écrit :
You're right, both are set in the same loop. Usually I prefer to adapt
the code to make it match the doc, but here I don't see a reasonable
way to do it, so I think we'll instead update the code to emit a warning
and update the doc. Any
On Tue, Mar 06, 2018 at 09:48:11AM +, Pieter Vogelaar wrote:
> Does use-server also accept some keyword to address the first server in the
> backend instead of a specific valid server name of the backend?
Hmmm no there's no such feature. I'm not sure I'm seeing well the real
use case to be
Does use-server also accept some keyword to address the first server in the
backend instead of a specific valid server name of the backend?
That would save quite a bit logic complexity in Puppet.
Best regards,
Pieter Vogelaar
Op 02-03-18 15:41 heeft Willy Tarreau geschreven:
On Fri, Mar 02, 2018 at 01:51:42PM +, Pieter Vogelaar wrote:
> When I move force-persist to the backend, it indeed works.
Great, thanks for the feedback.
> From some other post I understand it's only possible to bypass the
> maintenance mode where stickiness is used?
Yes, or you can use the
When I move force-persist to the backend, it indeed works.
From some other post I understand it's only possible to bypass the maintenance
mode where stickiness is used?
Best regards,
Pieter Vogelaar
Op 02-03-18 06:32 heeft Willy Tarreau geschreven:
Hi Cyril,
On
Hi Cyril,
On Thu, Mar 01, 2018 at 08:50:55PM +0100, Cyril Bonté wrote:
> Well, I think your issue will be resolved by moving "force-persist" on the
> backend side instead of the frontend one.
>
> The issue seems to exist from the first day of "force-persist", where the
> code and the
Hi Pieter and Willy,
Le 01/03/2018 à 16:09, Pieter Vogelaar a écrit :
Hi Willy,
Yes I'm absolutely certain that the cookie is present in the browser request
when I get the 503.
I changed the JSESSIONID line to "cookie SERVERID insert indirect nocache", but
that didn't make a difference.
Log
Hi Willy,
Yes I'm absolutely certain that the cookie is present in the browser request
when I get the 503.
I changed the JSESSIONID line to "cookie SERVERID insert indirect nocache", but
that didn't make a difference.
Log line when both servers in backend are in maintenance mode:
On Thu, Mar 01, 2018 at 02:29:57PM +, Pieter Vogelaar wrote:
> Hi Willy,
>
> We use Memcached Session Manager that stores the Tomcat sessions to a
> Couchbase cluster. It suffixes the session ID with "-n1" like:
>
> JSESSIONID=s01~1C7985929CDF981D9ACC79EBD8A3293D-n1
>
> Could this
Hi Willy,
We use Memcached Session Manager that stores the Tomcat sessions to a Couchbase
cluster. It suffixes the session ID with "-n1" like:
JSESSIONID=s01~1C7985929CDF981D9ACC79EBD8A3293D-n1
Could this JSESSIONID format somehow have impact on HAProxy?
Best regards,
Pieter Vogelaar
Op
Hi Pieter,
On Thu, Mar 01, 2018 at 01:16:36PM +, Pieter Vogelaar wrote:
> Hi Willy,
>
> I have the following (stripped down) configuration:
>
> ---
>
> defaults
> log global
> maxconn 8000
> option redispatch
> option allbackups
> retries 3
> stats enable
>
Hi Willy,
I have the following (stripped down) configuration:
---
defaults
log global
maxconn 8000
option redispatch
option allbackups
retries 3
stats enable
timeout http-request 10s
timeout queue 1m
timeout connect 10s
timeout client 1m
timeout server
Am 2018-02-20 13:44, schrieb Willy Tarreau:
On Tue, Feb 20, 2018 at 12:33:59PM +0100, rai...@ultra-secure.de wrote:
can you point out what is wrong with this config?
https://stackoverflow.com/questions/29248144/working-configuration-for-haproxy-with-the-force-persist-setting
Thanks for the
On Tue, Feb 20, 2018 at 12:33:59PM +0100, rai...@ultra-secure.de wrote:
> can you point out what is wrong with this config?
>
> https://stackoverflow.com/questions/29248144/working-configuration-for-haproxy-with-the-force-persist-setting
Thanks for the link, I've responded there so that the
Am 2018-02-19 14:04, schrieb Willy Tarreau:
Hi,
On Mon, Feb 19, 2018 at 12:18:36PM +, Pieter Vogelaar wrote:
Hi,
At the moment if we set backends in maintenance mode, the servers
can't be
reached by anyone.
Is it possible to still allow traffic from certain IP's (of the office
network)
On 20/02/2018 09:11 πμ, Pieter Vogelaar wrote:
> Hi Willy,
>
> Thanks I will look into that!
>
> On the statistics report page it's possible to set all servers of a backend
> in maintence mode. Is it also possible to set the servers of all backends in
> maintenance mode?
>
> Best regards,
>
On Tue, Feb 20, 2018 at 08:11:25AM +, Pieter Vogelaar wrote:
> On the statistics report page it's possible to set all servers of a backend
> in maintence mode. Is it also possible to set the servers of all backends in
> maintenance mode?
I don't think so. At least the page doesn't offer the
Hi Willy,
Thanks I will look into that!
On the statistics report page it's possible to set all servers of a backend in
maintence mode. Is it also possible to set the servers of all backends in
maintenance mode?
Best regards,
Pieter Vogelaar
Op 19-02-18 14:04 heeft Willy Tarreau
Hi,
On Mon, Feb 19, 2018 at 12:18:36PM +, Pieter Vogelaar wrote:
> Hi,
>
> At the moment if we set backends in maintenance mode, the servers can't be
> reached by anyone.
> Is it possible to still allow traffic from certain IP's (of the office
> network) so that testing can be done, before
Hi,
At the moment if we set backends in maintenance mode, the servers can’t be
reached by anyone.
Is it possible to still allow traffic from certain IP’s (of the office network)
so that testing can be done, before the backend is available to the general
public again?
Best regards,
Pieter
20 matches
Mail list logo