On Fri, May 10, 2019 at 05:50:50PM +0200, Tim Duesterhus wrote:
> vars_check_arg previously leaked the string containing the variable
> name:
(...)
Thanks Tim! I'm going to apply a minor change :
> diff --git a/src/vars.c b/src/vars.c
> index 477a14632..d32310270 100644
> --- a/src/vars.c
> +++
Hello,
I would like to inquire about publishing a guest post on your site - unique
& objective content, not self-promotional and of course relevant to your
site's audience.
We'd be willing to pay for it.
Please let me know how can we proceed.
Looking forward to working with you,
Levente
merged, thank you Ilya.
Willy
On Fri, May 10, 2019 at 10:53:07AM +0200, Willy Tarreau wrote:
> On Wed, Jun 26, 2013 at 12:10:27PM -0400, Chris Patti wrote:
(...)
Just noticed that a thread sorting issue on my side brought this very old
thread back and that this post is probably not interesting anymore to the
initial
On Thu, May 09, 2019 at 08:59:44PM +, Chris Packham wrote:
> >>haproxy-1.9.7/src/fd.c:267: undefined reference to `__ha_cas_dw'
(...)
> >>collect2: error: ld returned 1 exit status
> >>Makefile:994: recipe for target 'haproxy' failed
> >>make: *** [haproxy] Error 1
> >>
> >>
Hello,
On Thu, May 09, 2019 at 11:42:54AM -0600, ericr wrote:
> A couple of weeks ago I installed haproxy on our server running FreeBSD
> 11.0-RELEASE-p16. (yes, I know it's an old version of the OS, I'm going to
> upgrade it as soon as I solve my haproxy problem.)
Can you tell us what exact
Hi Ilya,
On Thu, May 09, 2019 at 12:19:45AM +0500, ??? wrote:
> Hello,
>
> does haproxy have some issues when it is built using openssl-1.1.0 and
> running with openssl-1.1.1, for example ?
I don't know. I'd say that openssl guarantees ABI compatibility for low
numbers (as you could
On Wed, Jun 26, 2013 at 12:10:27PM -0400, Chris Patti wrote:
> Thank you *VERY* much for this tidbit Nenad.
>
> With the early version of HAProxy we're using (v1.3.18) the actual syntax
> is:
>
> option httpclose
>
> This worked perfectly, session afinity started performing as expected.
>
>
On 10/05/19 8:57 PM, Willy Tarreau wrote:
> On Thu, May 09, 2019 at 05:07:40PM +1200, Chris Packham wrote:
>> __ha_cas_dw() is used in fd_rm_from_fd_list() and when built without
>> USE_THREADS=1 the linker fails to find __ha_cas_dw(). Add a definition
>> of __ha_cas_dw() for the #ifndef
__ha_cas_dw() is used in fd_rm_from_fd_list() and when built without
USE_THREADS=1 the linker fails to find __ha_cas_dw(). Add a definition
of __ha_cas_dw() for the #ifndef USE_THREADS case.
Signed-off-by: Chris Packham
---
Changes in v2:
- cast to int * to avoid dereferencing void *
On Fri, May 10, 2019 at 09:38:08AM +, Chris Packham wrote:
> On 10/05/19 8:57 PM, Willy Tarreau wrote:
> > On Thu, May 09, 2019 at 05:07:40PM +1200, Chris Packham wrote:
> >> __ha_cas_dw() is used in fd_rm_from_fd_list() and when built without
> >> USE_THREADS=1 the linker fails to find
Hello!
On Wed, May 08, 2019 at 10:13:38PM +, Zakharychev, Bob wrote:
> I wouldn't bother even trying to add support for BoringSSL - they themselves
> discourage people from doing so in their mission statement:
>
> "Although BoringSSL is an open source project, it is not intended for general
Hi Maciej,
On Thu, May 09, 2019 at 07:25:54PM +0200, Maciej Zdeb wrote:
> Hi again,
>
> I have bad news, HAProxy 1.9.7-35b44da still looping :/
Well, it's getting really annoying. Something's definitely wrong in
this list and I can't figure what.
> 2609list_for_each_entry_safe(h2s,
On Thu, May 09, 2019 at 05:07:40PM +1200, Chris Packham wrote:
> __ha_cas_dw() is used in fd_rm_from_fd_list() and when built without
> USE_THREADS=1 the linker fails to find __ha_cas_dw(). Add a definition
> of __ha_cas_dw() for the #ifndef USE_THREADS case.
Just found your patch, I think it's
osx build is broken
https://travis-ci.com/haproxy/haproxy/jobs/199157750
seems to be related
пт, 10 мая 2019 г. в 14:45, Chris Packham :
> __ha_cas_dw() is used in fd_rm_from_fd_list() and when built without
> USE_THREADS=1 the linker fails to find __ha_cas_dw(). Add a definition
> of
I'm gettingh old... I failed to remember to dump core :( And already killed
the process. Sorry, but the issue must reoccur and I can't say how long it
may take.
As soon as I get core dump I'll return.
pt., 10.05.2019, 10:35 użytkownik Willy Tarreau napisał:
> Hi Maciej,
>
> On Thu, May 09,
From: Ilya Shipitsin
---
.travis.yml | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/.travis.yml b/.travis.yml
index f9a13586..530d1682 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -8,6 +8,7 @@ env:
- FLAGS="USE_ZLIB=1 USE_PCRE=1 USE_LUA=1 USE_OPENSSL=1"
-
*From:* Willy Tarreau [mailto:w...@1wt.eu]
*Sent:* Tuesday, May 7, 2019, 14:46 EDT
*To:* Patrick Hemmer
*Cc:* haproxy@formilux.org
*Subject:* HAProxy 1.9.6 unresponsive
Hi Patrick,
On Tue, May 07, 2019 at 02:01:33PM
I've just sent some additional data to Willy. :)
Sure, I'll test your patch!
pt., 10 maj 2019 o 15:11 Olivier Houchard
napisał(a):
> Hi Maciej,
>
> On Thu, May 09, 2019 at 07:25:54PM +0200, Maciej Zdeb wrote:
> > Hi again,
> >
> > I have bad news, HAProxy 1.9.7-35b44da still looping :/
> >
> >
this patch will reveal osx reg-tests errors (after osx build is repaired)
пт, 10 мая 2019 г. в 15:38, :
> From: Ilya Shipitsin
>
> v2, rebased to master
>
> ---
> .travis.yml | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/.travis.yml b/.travis.yml
> index
From: Ilya Shipitsin
v2, rebased to master
---
.travis.yml | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/.travis.yml b/.travis.yml
index c00725d8..530d1682 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -8,6 +8,7 @@ env:
- FLAGS="USE_ZLIB=1 USE_PCRE=1 USE_LUA=1
please ignore, I will send "v2" soon
пт, 10 мая 2019 г. в 15:32, :
> From: Ilya Shipitsin
>
> ---
> .travis.yml | 8 ++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/.travis.yml b/.travis.yml
> index f9a13586..530d1682 100644
> --- a/.travis.yml
> +++ b/.travis.yml
>
Hi Maciej,
On Thu, May 09, 2019 at 07:25:54PM +0200, Maciej Zdeb wrote:
> Hi again,
>
> I have bad news, HAProxy 1.9.7-35b44da still looping :/
>
> gdb session:
> h2_process_mux (h2c=0x1432420) at src/mux_h2.c:2609
> 2609list_for_each_entry_safe(h2s, h2s_back, >send_list, list) {
>
vars_check_arg previously leaked the string containing the variable
name:
Consider this config:
frontend fe1
mode http
bind :8080
http-request set-header X %[var(txn.host)]
Starting HAProxy and immediately stopping it by sending a SIGINT makes
Valgrind report this
Olivier, it's still looping, but differently:
2609list_for_each_entry_safe(h2s, h2s_back, >send_list, list) {
(gdb) n
2610if (h2c->st0 >= H2_CS_ERROR || h2c->flags &
H2_CF_MUX_BLOCK_ANY)
(gdb)
2609list_for_each_entry_safe(h2s, h2s_back, >send_list, list) {
(gdb)
2613
On Fri, May 10, 2019 at 03:42:17PM +0500, ??? wrote:
> this patch will reveal osx reg-tests errors (after osx build is repaired)
>
> ??, 10 ??? 2019 ?. ? 15:38, :
>
> > From: Ilya Shipitsin
> >
> > v2, rebased to master
(...)
Thanks Ilya, I've applied it. However, please in the
26 matches
Mail list logo
