Hello,
Please help...
- Original Message -
From: "flamese...@yahoo.co.jp"
To: "flamese...@yahoo.co.jp" ; "haproxy@formilux.org"
Date: 2020/4/16, Thu 11:22
Subject: Re: Sometimes worker process stops working.
Hi,
I dug a little more:
start haproxy, got 5 processes: say
HI Lukas,
Package was installed in RHEL machines using yum. Let me know how to install
Redhat openssl version.
Yum install haproxy.
Thanks,
Bindushree D B
-Original Message-
From: Lukas Tribus
Sent: Friday, April 17, 2020 3:09 AM
To: D B, Bindushree (Cognizant)
Cc: haproxy
Hello,
On Thu, 16 Apr 2020 at 13:51, wrote:
> # which haproxy
> /usr/ local/sbin/haproxy
>
>
>
> Attached output for command “haproxy –vv”
>
>
>
> Also I’m using a AWS RHEL 8.1 version AMI.
>
> Let us know what else is required. Also let me know how to enable Openssl.
> Provide me the rpm link
Hello,
next typo fixes.
Ilya Shipitcin
From 40a7e81223c783836d6e7d3726ad3db2f9ca418e Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin
Date: Thu, 16 Apr 2020 23:51:34 +0500
Subject: [PATCH] CLEANUP: assorted typo fixes in the code and comments
This is 8th iteration of typo fixes
---
Hello,
I added weekly build for detection incompatibilities against
"no-deprecated" openssl.
(well, I first thought to add those option to travis, but it became
over-engineered from my point of view)
Lukas, if you have suggestions how to add to travis, I can try.
Cheers,
Ilya Shipitsin
From
Hi Willy,
Le 16/04/2020 17:00, « Willy Tarreau » a écrit :
I'm a bit confused by how it can be efficiently used. Because it still
includes the client-side handshake which only happens before the first
request, so if you're interested in removing idle time from keep-alive
Hi all,
now's THE day.
1.4-rc1 was emitted 3 weeks ago, and very minor issues were reported
and fixed. There's no need to wait any longer, so let's release it now.
The code is remarkably stable and has no known regressions from 1.3.
(Some fixes from 1.4 will even have to be backported to 1.3
Hi everyone,
Sixteen months after haproxy 1.5.0 was released, here comes 1.6.0.
We've done a much better job this time and despite some code being
pushed after the freeze (don't do that again or I'll bite), overall
the process has been doing quite well.
Recently for our products I had to walk
Hi Damien,
On Thu, Apr 16, 2020 at 01:27:50PM +, Damien Claisse wrote:
> It can be useful to have a server-side view of the end-to-end time for a
> request to be served, such as a tool like cURL would do on client side.
> HAProxy provides Tt timer for this, but unfortunately, it is
It can be useful to have a server-side view of the end-to-end time for a
request to be served, such as a tool like cURL would do on client side.
HAProxy provides Tt timer for this, but unfortunately, it is accounting
idle time too, which can be very long when using HTTP keep-alive, hence
Rename it to LOG_FMT_Tt (same case as Tt timer), to reserve
LOG_FMT_TT for another usage.
---
include/types/log.h | 2 +-
src/log.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/types/log.h b/include/types/log.h
index c348caa1e..3720fe73f 100644
---
It can be sometimes useful to measure total time of a request, including
TCP/TLS negotiation, server response time and transfer time. "Tt"
currently provides something close to that, but it also takes client idle time
into account, which is problematic for keep-alive requests as idle time
can be
On Thu, Apr 16, 2020 at 05:38:59PM +0500, ??? wrote:
> ??, 16 ???. 2020 ?. ? 16:26, Willy Tarreau :
>
> > On Thu, Apr 16, 2020 at 12:29:42PM +0200, Tim Düsterhus wrote:
> > > > FWIW musl seems to work OK here when building for linux-glibc-legacy.
> > >
> > > Yes. HAProxy linked against
чт, 16 апр. 2020 г. в 16:26, Willy Tarreau :
> On Thu, Apr 16, 2020 at 12:29:42PM +0200, Tim Düsterhus wrote:
> > > FWIW musl seems to work OK here when building for linux-glibc-legacy.
> >
> > Yes. HAProxy linked against Musl is smoke tested as part of the Docker
> > Official Images program,
Hi Team,
Here is the output of the required commands.
# which haproxy
/usr/ local/sbin/haproxy
Attached output for command “haproxy –vv”
Also I’m using a AWS RHEL 8.1 version AMI.
Let us know what else is required. Also let me know how to enable Openssl.
Provide me the rpm link which has
On Thu, Apr 16, 2020 at 12:29:42PM +0200, Tim Düsterhus wrote:
> > FWIW musl seems to work OK here when building for linux-glibc-legacy.
>
> Yes. HAProxy linked against Musl is smoke tested as part of the Docker
> Official Images program, because the Alpine-based Docker images use Musl
> as their
On Thu, Apr 16, 2020 at 12:37:44PM +0200, Tim Düsterhus wrote:
> Ilya,
>
> Am 16.04.20 um 12:34 schrieb ???:
> > yep, I thought about alpine as well.
> >
> > I'm not sure how often official docker validation runs. If it runs often
> > enough, maybe we do not need CI.
> >
>
> The tests
Ilya,
Am 16.04.20 um 12:34 schrieb Илья Шипицин:
> yep, I thought about alpine as well.
>
> I'm not sure how often official docker validation runs. If it runs often
> enough, maybe we do not need CI.
>
The tests are run for every update of the Dockerfile, thus either for
new HAProxy releases
yep, I thought about alpine as well.
I'm not sure how often official docker validation runs. If it runs often
enough, maybe we do not need CI.
чт, 16 апр. 2020 г. в 15:29, Tim Düsterhus :
> Willy,
>
> [removed Bindushree from Cc as we disgress from the main topic]
>
> Am 16.04.20 um 11:44
Willy,
[removed Bindushree from Cc as we disgress from the main topic]
Am 16.04.20 um 11:44 schrieb Willy Tarreau:
>> seems, we need some musl or picolibc in CI.
>> beeing glibc dependent is dangerous
>
> It's not really glibc-dependent in that it's properly enclosed in ifdefs.
> But you'd be
On Thu, Apr 16, 2020 at 02:38:28PM +0500, ??? wrote:
> hmm.
>
> seems, we need some musl or picolibc in CI.
> beeing glibc dependent is dangerous
It's not really glibc-dependent in that it's properly enclosed in ifdefs.
But you'd be welcome to add musl if you find an easy way to do it.
hmm.
seems, we need some musl or picolibc in CI.
beeing glibc dependent is dangerous
чт, 16 апр. 2020 г. в 13:29, Willy Tarreau :
> Hi Lukas,
>
> On Thu, Apr 16, 2020 at 09:44:39AM +0200, Lukas Tribus wrote:
> > Provide the output of "which haproxy" and "haproxy -vv", I doubt you
> > are
On 16.04.20 10:57, Willy Tarreau wrote:
On Thu, Apr 16, 2020 at 10:26:54AM +0200, Willy Tarreau wrote:
Hi Lukas,
On Thu, Apr 16, 2020 at 09:44:39AM +0200, Lukas Tribus wrote:
Provide the output of "which haproxy" and "haproxy -vv", I doubt you
are actually running the Redhat package you
On Thu, Apr 16, 2020 at 10:26:54AM +0200, Willy Tarreau wrote:
> Hi Lukas,
>
> On Thu, Apr 16, 2020 at 09:44:39AM +0200, Lukas Tribus wrote:
> > Provide the output of "which haproxy" and "haproxy -vv", I doubt you
> > are actually running the Redhat package you indicated, more likely you
> >
Hi William,
On Thu, Apr 16, 2020 at 10:37:53AM +0200, William Lallemand wrote:
> Also there isn't a date for each major release on the website, only the
> date of the latest minor release, which is a problem to understand at
> which period of the cycle the version is. So we should probably add
Hi,
On Wed, Apr 15, 2020 at 07:11:04PM +0200, Willy Tarreau wrote:
>
> Yes absolutely. I thought it was clear since 2.0 that even ones are LTS
> and odd are not, but maybe this deserves a clarification somewhere.
>
Just a few ideas/notes, because people often ask me the dates of
releases and
Hi Lukas,
On Thu, Apr 16, 2020 at 09:44:39AM +0200, Lukas Tribus wrote:
> Provide the output of "which haproxy" and "haproxy -vv", I doubt you
> are actually running the Redhat package you indicated, more likely you
> built Haproxy manually from source on top of it.
This just makes me think that
чт, 16 апр. 2020 г. в 12:48, Lukas Tribus :
> Hello,
>
> On Thu, 16 Apr 2020 at 06:04, wrote:
> >
> > Hi Team
> >
> > Let us know your availability to work on this.
>
> As Aleks already said:
>
> This haproxy executable has been build without OpenSSL support, which
> is required for your
On Wed, Apr 08, 2020 at 01:10:27AM +0500, ??? wrote:
> Hello,
>
> 7th iteration of typo fixes.
Merged, thanks Ilya!
Willy
Hello,
On Thu, 16 Apr 2020 at 06:04, wrote:
>
> Hi Team
>
> Let us know your availability to work on this.
As Aleks already said:
This haproxy executable has been build without OpenSSL support, which
is required for your configuration.
Provide the output of "which haproxy" and "haproxy -vv",
31 matches
Mail list logo
