Hi Hemant,
On Mon, Nov 27, 2017 at 12:11:25PM -0600, Coscend@Coscend wrote:
> Dear HAProxy community,
>
> We have been successfully loading Stats page and other applications via
> HAProxy 1.7.9. We successfully compiled, installed and ran 1.8.0 as a
> systemd service. However, with 1.8.0, we
Hi Maciej,
On Mon, Nov 27, 2017 at 09:15:22AM +0100, Maciej Zdeb wrote:
> Hi,
>
> Thank you for your hard work on HAProxy 1.8 - great job!
>
> I tried to update haproxy from 1.7 on our r machine to 1.8 version
> however stumbled upon problem with tune.ssl.cachesize directive.
>
> In 1.7.3 with
Hi Manu,
On Mon, Nov 27, 2017 at 06:21:50PM +0100, Emmanuel Hocdet wrote:
> Hi Willy,
>
> > Le 18 nov. 2017 à 12:28, Willy Tarreau a écrit :
> >
> > Hi Manu,
> >
> > On Fri, Nov 17, 2017 at 05:14:11PM +0100, Emmanuel Hocdet wrote:
> >> In master-worker mode with peers, old worker
Hello Ricardo,
On Mon, Nov 27, 2017 at 04:33:45PM -0200, Ricardo Nabinger Sanchez wrote:
> Hello,
>
> While compile-testing 1.9-dev with Clang/LLVM analyzer, it found the
> following (possible) scenario:
>
> 1- in function cfg_cache_postparser(), when entering the nested loop in
> line 914,
Hi Pieter,
On Mon, Nov 27, 2017 at 09:43:52PM +0100, PiBa-NL wrote:
> Hi List,
>
> I thought i 'reasonably' tested some of 1.8.0's options.
> Today i put it into 'production' on my secondary cluster node and notice it
> takes 100% cpu...
G.. bad. This sounds like another case of recursive
Dear list!
Author: CJ Ting
Number of patches: 1
This is an automated relay of the Github pull request:
Fix typo
Patch title(s):
Fix typo
Link:
https://github.com/haproxy/haproxy/pull/81
Edit locally:
wget https://github.com/haproxy/haproxy/pull/81.patch
Hi Willy.
-- Originalnachricht --
Von: "Willy Tarreau"
An: "Aleksandar Lazic"
Cc: haproxy@formilux.org
Gesendet: 27.11.2017 23:54:31
Betreff: Re: [ANNOUNCE] haproxy-1.8.0
Hi Aleks,
On Mon, Nov 27, 2017 at 09:18:35PM +, Aleksandar Lazic wrote:
>
Hi.
-- Originalnachricht --
Von: "Willy Tarreau"
An: haproxy@formilux.org
Gesendet: 26.11.2017 19:57:35
Betreff: [ANNOUNCE] haproxy-1.8.0
Hi all,
After one year of intense development and almost one month of
debugging,
polishing, and cross-review work trying to prevent
Hi List,
I thought i 'reasonably' tested some of 1.8.0's options.
Today i put it into 'production' on my secondary cluster node and notice
it takes 100% cpu... I guess i should have tried such a thing last week.
My regular config with 10 frontends and total 13 servers seems to
startup fine
Further, we have added the following new parameters in the configuration
before testing 1.8.0 [{I} -Baptiste Assman's article]. Still the pages /
applications are not accessible via 1.8.0. What obvious thing could we be
missing with 1.8.0 installation/configuration vs. 1.7.9? Your vectors to
Hello Moemen,
Thank you and very thoughtful of you to educate us on how HAProxy handles
Websockets and logs cookies. Guidance such as these have helped us grow
from a rank startup to offer SLA-based healthcare services to disadvantaged
remote areas (where there are no hospitals/clinics)
Hi Hemant,
When using websocket, HAProxy will switch to tunnel mode whenever it
detects the Connection: Upgrade header.
Tunnel mode means that only the first request and response are processed
and logged and everything else will be forwarded with no analysis, I
think this is what happens with
Hello,
While compile-testing 1.9-dev with Clang/LLVM analyzer, it found the
following (possible) scenario:
1- in function cfg_cache_postparser(), when entering the nested loop in
line 914, cache_ptr is free()ed and redefined to cache (line 918):
914
Dear HAProxy community,
We have been successfully loading Stats page and other applications via
HAProxy 1.7.9. We successfully compiled, installed and ran 1.8.0 as a
systemd service. However, with 1.8.0, we are unable to access the same
stats page or any other application. We are using the
Hi Willy,
> Le 18 nov. 2017 à 12:28, Willy Tarreau a écrit :
>
> Hi Manu,
>
> On Fri, Nov 17, 2017 at 05:14:11PM +0100, Emmanuel Hocdet wrote:
>> In master-worker mode with peers, old worker never died after a reload (kill
>> -USR2).
>>
>> Tested without traffic, with/without
> Le 27 nov. 2017 à 17:52, Olivier Houchard a écrit :
>
> Hi Emmanuel,
>
> On Mon, Nov 27, 2017 at 05:17:54PM +0100, Emmanuel Hocdet wrote:
>>
>> Hi,
>>
>> This patch fix CO_FL_EARLY_DATA removal to have correct ssl_fc_has_early
>> reporting. It work for 'mode http'.
Hi Emmanuel,
On Mon, Nov 27, 2017 at 05:17:54PM +0100, Emmanuel Hocdet wrote:
>
> Hi,
>
> This patch fix CO_FL_EARLY_DATA removal to have correct ssl_fc_has_early
> reporting. It work for 'mode http'.
>
> It does not fix ssl_fc_has_early for 'mode tcp'. In this mode CO_FL_EARLY_DATA
> should
Hi,
This patch fix CO_FL_EARLY_DATA removal to have correct ssl_fc_has_early
reporting. It work for 'mode http'.
It does not fix ssl_fc_has_early for 'mode tcp'. In this mode CO_FL_EARLY_DATA
should not be removed if early data was accepted.
It is possible to check MODE_TCP in mux_pt_recv? Or
Congratulations!
On Mon, Nov 27, 2017 at 8:41 AM, Arnall wrote:
> Le 26/11/2017 à 19:57, Willy Tarreau a écrit :
>
>> Hi all,
>>
>> After one year of intense development and almost one month of debugging,
>> polishing, and cross-review work trying to prevent our respective
Hi,
I am interested in having a link on your website much like others have on your
site here;
http://hnpaper.forge.partlab.io/u/flibble
Please could you let me know the costs for this?
Many Thanks,
Jack Russell
Le 26/11/2017 à 19:57, Willy Tarreau a écrit :
Hi all,
After one year of intense development and almost one month of debugging,
polishing, and cross-review work trying to prevent our respective coworkers
from winning the first bug award, I'm pleased to announce that haproxy 1.8.0
is now
On Mon, Nov 27, 2017 at 12:53:27PM +, David Carlier wrote:
> Following up the 1.8 release, deviceatlas being MT safe, we enable this new
> Haproxy feature from this module.
>
> Needs to be backported to 1.8 branch.
Thanks very much for testing David, now merged in master an 1.8.
Willy
Hi,
Following up the 1.8 release, deviceatlas being MT safe, we enable this new
Haproxy feature from this module.
Needs to be backported to 1.8 branch.
Thanks in advance.
Regards.
From b2e649193e5707244638122d3df04e1224bd060d Mon Sep 17 00:00:00 2001
From: David Carlier
On 26/11/2017 07:57 μμ, Willy Tarreau wrote:
> Hi all,
>
> After one year of intense development and almost one month of debugging,
> polishing, and cross-review work trying to prevent our respective coworkers
> from winning the first bug award, I'm pleased to announce that haproxy 1.8.0
> is now
Hi,
On Mon, Nov 27, 2017 at 06:58:06AM -0200, Joao Morais wrote:
>
> Hi, from nbproc doc[1]: "This requires the 'daemon' mode”, but this is also
> the way to start more than one worker on master-worker mode, right?
>
You can have several workers with the master-worker in foreground mode, the
Hi, from nbproc doc[1]: "This requires the 'daemon' mode”, but this is also the
way to start more than one worker on master-worker mode, right?
Still on the same doc: "USING MULTIPLE PROCESSES IS HARDER TO DEBUG AND IS
REALLY DISCOURAGED”, is this still valid on master-worker? Both "harder to
Hi,
Greetings!
This is Shweta Dubey Freelancer services provider. Current working for
a client who is interested in buying paid advertising articles
with links on good finance, Forex, casino, gambling, sports
betting sites (if you allow), news and other relevant sites. So, if you
are
Hi,
Thank you for your hard work on HAProxy 1.8 - great job!
I tried to update haproxy from 1.7 on our r machine to 1.8 version
however stumbled upon problem with tune.ssl.cachesize directive.
In 1.7.3 with tune.ssl.cachesize = 1000:
ps aux | grep haproxy
USER PID %CPU %MEMVSZ
28 matches
Mail list logo