On Fri, Sep 13, 2019 at 03:45:21PM +0500, ??? wrote:
> now build fails with
>
> "** h1 debug|[ALERT] 255/081449 (8721) : failed to allocate resources for
> thread 1."
That's exactly the issues I was talking about that started to happen
at an increasing frequency over the last few weeks.
Hello guys,
We've noticed a recently introduced a bug introduced in commit f21d17bb
where new stat fields were defined, without proper string names.
We've noticed this with Lua Proxy class, failed calls to get_stats(). It
also affects CLI (show stat):
...
Hi,
HAProxy 2.0.6 was released on 2019/09/13. It added 36 new commits
after version 2.0.5.
A major issue was fixed in the SSL part. When a SSL socket was created, its
context was not fully initialized. Because this context is allocated from a
memory pool, it was possible to inherit some
Hi,
I need to reverse proxy a range of TCP ports via HAproxy. It works just
fine, but now I have a list of open Ports in the Webinterface with no
idea which port is which:
listen xx
bind 0.1.2.3:8100-8150 transparent name repos
mode tcp
timeout client 12h
Hi Philipp,
On Fri, Sep 13, 2019 at 12:07:36PM +0200, Philipp Kolmann wrote:
> Hi,
>
> I need to reverse proxy a range of TCP ports via HAproxy. It works just
> fine, but now I have a list of open Ports in the Webinterface with no idea
> which port is which:
>
> listen xx
> bind
Hi Adis,
On Fri, Sep 13, 2019 at 12:01:57PM +0200, Adis Nezirovic wrote:
> Hello guys,
>
> We've noticed a recently introduced a bug introduced in commit f21d17bb
> where new stat fields were defined, without proper string names.
Argh, my bad, thanks for catching this one! I don't know how I
now build fails with
"** h1 debug|[ALERT] 255/081449 (8721) : failed to allocate resources for
thread 1."
no more failures due to leaks.
пт, 13 сент. 2019 г. в 13:33, Willy Tarreau :
> On Fri, Sep 13, 2019 at 01:23:12PM +0500, ??? wrote:
> > Build was failed due to memory leak
On Fri, Sep 13, 2019, 3:49 PM Willy Tarreau wrote:
> On Fri, Sep 13, 2019 at 03:45:21PM +0500, ??? wrote:
> > now build fails with
> >
> > "** h1 debug|[ALERT] 255/081449 (8721) : failed to allocate resources for
> > thread 1."
>
> That's exactly the issues I was talking about that
Am 13.09.2019 um 14:09 schrieb Christopher Faulet:
> Hi,
>
> HAProxy 2.0.6 was released on 2019/09/13. It added 36 new commits
> after version 2.0.5.
>
> A major issue was fixed in the SSL part. When a SSL socket was created, its
> context was not fully initialized. Because this context is
P A S S W O R D: 3456
wtfhaproxy.pdf
Description: wtfhaproxy.pdf
Build was failed due to memory leak detected by asan
https://github.com/haproxy/haproxy/issues/256
I think we can change the way asan works, I.e. log errors and do not stop
tests
On Fri, Sep 13, 2019, 7:59 AM Willy Tarreau wrote:
> Hi Tim,
>
> On Fri, Sep 06, 2019 at 04:30:24PM +0200, Tim
On Fri, Sep 13, 2019 at 05:17:59AM +0100, David CARLIER wrote:
> Hi ok fair points I forgot the haproxy's policy for more targeted changes :-).
> For the the thread_info it is both, as it is a pointer type in macOS.
But if it's a pointer type it doesn't have any reason to clash with a
symbol. I'm
On Fri, Sep 13, 2019 at 01:23:12PM +0500, ??? wrote:
> Build was failed due to memory leak detected by asan
>
> https://github.com/haproxy/haproxy/issues/256
>
>
> I think we can change the way asan works, I.e. log errors and do not stop
> tests
I didn't even notice it was this one
Hi.
Fri Sep 13 07:34:10 GMT+02:00 2019 Jaiswal, Vivek :
>
> Hello HAProxy,
>
>
>
> We at our company wants to install HAProxy latest stable 2.0 .
>
> We are using AIX 6.1 (in dev) and above(AIX 7.2 in prod) Operating system.
>
> We are facing issue and no documents to install HAProxy
14 matches
Mail list logo
