with servers in this
state for a long time.
Can anyone confirm my understating of this setting ?
śr., 22 wrz 2021 o 19:52 Michał Pasierb napisał(a):
> I would like to clarify how *hold valid* is used by resolvers. I have
> this configuration:
>
> resolvers mydns
>
I would like to clarify how *hold valid* is used by resolvers. I have this
configuration:
resolvers mydns
nameserver dns1 192.168.122.202:53
accepted_payload_size 8192
timeout resolve 5s
timeout retry 2s
resolve_retries 3
hold other 30s
hold refused120s
hold nx
Hello,
I have situation where HAProxy receives a request but doesn't log it. I
would like to know if this is desired behaviour or this is an actual bug.
To replicate this issue:
1) create HAProxy config which doesn't disable http-keep-alive
2) on backend server set http-keep-alive timeout to a
Aleksandar Lazic wrote:
> Am 11.10.2018 um 10:33 schrieb Michał Pasierb:
> > Hello,
> >
> > I have a problem understanding a particular log line from HAProxy 1.7.11
> in
> > production system. My clients report problems from time to time. They
> make
Hello,
I have a problem understanding a particular log line from HAProxy 1.7.11 in
production system. My clients report problems from time to time. They make
another request and all is OK. This is the log format used:
log-format %tr\ %ci:%cp\ %ft\ %b/%s\ %TR/%Tw/%Tc/%Tr/%Ta\ %ST\ %B\ %CC\
%CS\
Hi,
I would like to log size of response before and after compression. Is it
possible ?
I see this question was asked before at
http://thread.gmane.org/gmane.comp.web.haproxy/10008 without any resolution.
Regards,
Michal
Hi,
I would like to report a regression in HAProxy 1.6.13 after upgrading from
1.6.9 in production :(
Reproduce with config:
---
global
log 127.0.0.1 local0
log 127.0.0.1 local1 notice
maxconn 4096
chroot /usr/share/haproxy
uid 99
gid 99
daemon
defaults
log global
mode
Hi,
I didn't want to continue this discussion, but there is one thing that's
totally not true.
2017-04-13 13:50 GMT+02:00 Frederic Lecaille <flecai...@haproxy.com>:
> Hello Michal,
>
> On 04/11/2017 04:41 PM, Michał wrote:
>
>> Hello Willy,
>>
>> So I'm fig
.0.1:8001 track customer2/s1
>
> where one could expect that a dynamic backend tracking a static one
> would always stay in sync with it, but that would not be true anymore.
>
> So for now I think this requires more thinking, probable a specific server
> option like "track-weight" or something like this to let the user decide
> whether or not the weights should be inherited from tracked servers. This
> would limit the risk of very bad surprizes.
>
Probably yes, we need another option for tracking weights and that will fix
issues with those unpredictable variants.
Regards,
> Willy
>
Please don't mess allegrogroup here, I'm posting those patches from my
private
e-mail.
Michał
usly works) with this cleaner
version - thanks for this. The patch got even simpler.
Thanks again,
Michał
2017-03-27 15:34 GMT+02:00 Willy Tarreau <w...@1wt.eu>:
> Hi Michal,
>
> On Mon, Mar 27, 2017 at 03:18:10PM +0200, Michal wrote:
> > Hello,
> > Thank you for y
Hello!
Any news in this topic? Is there anything wrong with my patch?
Michał
2017-02-04 9:38 GMT+01:00 Michał <creating@gmail.com>:
> Hi,
> I checked it and during synthetic tests it worked. I use same
> mechanism as origin agent-check, so it's ready to merge.
>
Hi,
I checked it and during synthetic tests it worked. I use same
mechanism as origin agent-check, so it's ready to merge.
It doesn't need to be backported.
2017-01-27 15:38 GMT+01:00 Michał <creating@gmail.com>:
> Hello,
>
> So here's patch, which includes all functionalitie
then you can send relative weight change and 0 will stay where it is.
Regards,
Michał
2017-01-20 10:54 GMT+01:00 Willy Tarreau <w...@1wt.eu>:
> Hi Michal,
>
> On Thu, Jan 19, 2017 at 11:45:57PM +0100, Micha?? wrote:
> > Hello,
> >
> > We use track's in haproxy
them. I'll let you know with some patches if I will find some
good
way to do it. The more people looking into it the more ways to find better
solution :)
Michał
2017-01-20 11:02 GMT+01:00 Willy Tarreau <w...@1wt.eu>:
> On Thu, Jan 19, 2017 at 11:54:32PM +0100, Micha?? wrote:
if
there's no such possibility to merge this feature in current state.
Michał
. Configurable or not - it will be good feature.
Michał
-agent-addr-and-agent-se.patch) =
971d6c1d23657130db4045d5b9e8cb73
Michał
0001-PATCH-MINOR-checks-Add-agent-addr-config-directive.patch
Description: Binary data
0002-PATCH-MINOR-cli-Add-possiblity-to-change-agent-confi.patch
Description: Binary data
0003-PATCH-MINOR-doc-Add-docs-for-agent-addr-configuratio.patch
D
Hello!
It's my first PR to haproxy, so please tell me if anything still wrong.
I've read CONTRIBUTING.
This patches implements possiblity to define different host (agent-host) for
agent checks in config and they also allow changing agent-host and
agent-send
variables via CLI/socket. We wonna use
ywords= Cannot access memory at address 0xffe8>,
> kw= 0xffe0>) at include/proto/action.h:38
> 38 include/proto/action.h: No such file or directory.
Is this a known issue or any clue how to debug it futher?
--
BR,
Michał Łowicki
Hi,
Is it possible to influence how HAProxy handles HTTP keep-alives to backend
servers ? I want it to close TCP connection after x many HTTP requests.
Also a max-age time for single TCP connection cloud be useful.
These features are available in F5 LTM OneConnect (
Hi,
I have a question about cookie prefix mode. I use configuration like this:
backend b1
balance roundrobin
cookie JSESSIONID prefix
server s1 192.168.122.1:8080 cookie c1
Now the docs
https://cbonte.github.io/haproxy-dconv/configuration-1.6.html#4-cookie for
prefix say:
Since all
keep backend
connections opened for 5 minutes before closing them. Was I mistaken? Would
timeout tunnel allow me to specify such timeout, despite HAProxy working
in http-keep-alive mode?
I'm attaching the haproxy config.
Thank you,
--
*Michał Ślizak*
DaftCode Sp. z o.o.
ul. Domaniewska 34a
configuration so its not possible to tell if your
are running into those
already fixed bugs, or if you simply need zero latency in all cases per
application design.
Hi Lukas,
We've upgraded to 1.5.11 and are working fine without option
http-no-delay.
Thank you for your help,
--
*Michał Ślizak
every minute over each session.
I realize the version we're running is very old and should be updated.
I'd like to know if there was a bug that could explain what we're seeing?
If so, which version of HAProxy fixed it?
Best regards,
--
*Michał Ślizak*
DaftCode Sp. z o.o.
ul. Domaniewska 34a
will never work in our case.
It would be much more efficient to decrease the number of concurrent
connections and send requests more often, but unfortunately we have no
control over this.
Best regards,
--
*Michał Ślizak*
DaftCode Sp. z o.o.
ul. Domaniewska 34a, 02-672 Warszawa
tel. +48 506 175
Thanks Lucas, option http-no-delay seems to have solved the problem.
--
*Michał Ślizak*
DaftCode Sp. z o.o.
ul. Domaniewska 34a, 02-672 Warszawa
tel. +48 506 175 074
26 matches
Mail list logo
