Hi Christopher,
On Thu, Apr 18, 2019 at 09:36:30PM +0200, Christopher Faulet wrote:
> > It seems related to the last commits from Christopher Faulet, maybe
> > around this commit:
> > http://git.haproxy.org/?p=haproxy-1.9.git;a=commit;h=0c2973662163ab2753a54e729ecdb09dd694c2dd
> > BUG/MINOR:
чт, 18 апр. 2019 г. в 21:51, Илья Шипицин :
>
>
> чт, 18 апр. 2019 г. в 21:45, Willy Tarreau :
>
>> Hi Ilya,
>>
>> On Wed, Apr 17, 2019 at 01:06:11PM +0500, ??? wrote:
>> > btw, we can run lua tests
>> >
>> > https://travis-ci.com/chipitsine/haproxy-1/builds/108641032
>> >
>> > so... how
Le 18/04/2019 à 16:55, William Dauchy a écrit :
Hello,
We are triggering a segfault on the last HEAD of haproxy-1.9 tree, last
commit being
1e0fd266db3e503783ff623faabcb1dfe211cb89 BUG/MINOR: mworker: disable busy
polling in the master process
backtrace:
Thread 1 (Thread 0x7f73aeffd700 (LWP
Hi Lukas,
On Thu, Apr 18, 2019 at 08:45:18PM +0200, Lukas Tribus wrote:
> Hi Willy,
>
>
> On Fri, 8 Mar 2019 at 14:23, PR Bot wrote:
> >
> > Dear list!
> >
> > Author: Radek Zajic
> > Number of patches: 1
> >
> > This is an automated relay of the Github pull request:
> >IPv6: properly
Hi Willy,
On Fri, 8 Mar 2019 at 14:23, PR Bot wrote:
>
> Dear list!
>
> Author: Radek Zajic
> Number of patches: 1
>
> This is an automated relay of the Github pull request:
>IPv6: properly format an address coming from IPv6 socket as hex in
>lf_ip
>
> Patch title(s):
>IPv6:
Hi Paul,
On Thu, Apr 18, 2019 at 02:46:17PM +0200, Paul Stephen Borile wrote:
> Hi All, Willy,
>
> please find attached to this email the 6 patches that cover various areas
> of restyling of
> the WURFL device detection feature for HAProxy. All patches can be back
> ported to 1.9 if necessary.
>
чт, 18 апр. 2019 г. в 21:45, Willy Tarreau :
> Hi Ilya,
>
> On Wed, Apr 17, 2019 at 01:06:11PM +0500, ??? wrote:
> > btw, we can run lua tests
> >
> > https://travis-ci.com/chipitsine/haproxy-1/builds/108641032
> >
> > so... how do we want to run lua ? always enabled ? or two builds
Hi Ilya,
On Wed, Apr 17, 2019 at 01:06:11PM +0500, ??? wrote:
> btw, we can run lua tests
>
> https://travis-ci.com/chipitsine/haproxy-1/builds/108641032
>
> so... how do we want to run lua ? always enabled ? or two builds (with and
> without lua) ?
I'd say that we generally detect
Hello Marco,
On Thu, Apr 18, 2019 at 05:27:26PM +0200, Marco Corte wrote:
> Hello!
>
> From time to time, about twice daily, and without any apparent reason,
> haproxy jumps from using about 15% CPU usage to 100% (relative to the single
> core it can use).
> The situation becomes normal again
Hello!
From time to time, about twice daily, and without any apparent reason,
haproxy jumps from using about 15% CPU usage to 100% (relative to the
single core it can use).
The situation becomes normal again after about 15-20 minutes.
During one of these events, I was able to capture (see
Hello,
We are triggering a segfault on the last HEAD of haproxy-1.9 tree, last
commit being
1e0fd266db3e503783ff623faabcb1dfe211cb89 BUG/MINOR: mworker: disable busy
polling in the master process
backtrace:
Thread 1 (Thread 0x7f73aeffd700 (LWP 13044)):
#0 h1_skip_chunk_crlf (stop=0, start=0,
On 4/18/19 11:06 AM, Emeric Brun wrote:
> Hi Marcin,
>
> On 4/12/19 6:10 PM, Marcin Deranek wrote:
>> Hi Emeric,
>>
>> On 4/12/19 5:26 PM, Emeric Brun wrote:
>>
>>> Do you have ssl enabled on the server side?
>>
>> Yes, ssl is on frontend and backend with ssl checks enabled.
>>
>>> If it is the
Hi All, Willy,
please find attached to this email the 6 patches that cover various areas
of restyling of
the WURFL device detection feature for HAProxy. All patches can be back
ported to 1.9 if necessary.
Last patch is a dummy WURFL library that can be used to build/run haproxy
compiled with the
Hi Marcin,
On 4/12/19 6:10 PM, Marcin Deranek wrote:
> Hi Emeric,
>
> On 4/12/19 5:26 PM, Emeric Brun wrote:
>
>> Do you have ssl enabled on the server side?
>
> Yes, ssl is on frontend and backend with ssl checks enabled.
>
>> If it is the case could replace health check with a simple tcp
Hi all, Willy,
Please find attached to this email the 4 patches for the http-request
do-resolve action I submitted a few months ago.
I integrated all feedback from Willy and also now support tcp-request
content do-resolve.
Baptiste
From e96ff49ee05dbdc15dc7582349e6314dcfccb20e Mon Sep 17
15 matches
Mail list logo