On Thu, May 24, 2018 at 11:20:13PM +0200, Janusz Dziemidowicz wrote:
> 2018-05-24 22:26 GMT+02:00 Willy Tarreau :
> >> This kinda seems like the socket was closed on the writing side, but
> >> the client has already sent something and everything is stuck. I was
> >> not able to reproduce the proble
2018-05-24 22:26 GMT+02:00 Willy Tarreau :
>> This kinda seems like the socket was closed on the writing side, but
>> the client has already sent something and everything is stuck. I was
>> not able to reproduce the problem by myself. Any ideas how to debug
>> this further?
>
> For now not much com
Hi William,
Thank you for your reply.
On Thu, May 24, 2018 at 12:01:38PM +0200, William Lallemand wrote:
> I managed to reproduce something similar with the 1.8.8 version. It looks like
> letting a socat connected to the socket helps.
>
> I'm looking into the code to see what's happening.
Indeed
Hi Janusz,
On Thu, May 24, 2018 at 01:49:52PM +0200, Janusz Dziemidowicz wrote:
> Recently I've moved several servers from haproxy 1.7.x to 1.8.x I have
> a setup with nghttpx handling h2 (haproxy connects to nghttpx via unix
> socket which handles h2 and connects back to haproxy with plain
> http
Hi Daniel,
On Thu, May 17, 2018 at 02:05:28PM -0400, Daniel Corbett wrote:
> Hello,
>
> When using table_* converters ref_cnt was incremented
> and never decremented causing entries to not expire.
>
> The root cause appears to be that stktable_lookup_key()
> was called within all sample_conv_tab
On Sat, May 19, 2018 at 08:08:13PM -0400, Daniel Corbett wrote:
> From 24f8a74f490435969c04e2bb5387d396b62850c0 Mon Sep 17 00:00:00 2001
> From: Daniel Corbett
> Date: Sat, 19 May 2018 19:43:24 -0400
> Subject: [PATCH] BUG/MEDIUM: servers state: Add srv_addr default placeholder
(...)
Merged, tha
On 24/05/2018 11:54, Daniel Corbett wrote:
Hello Aleks,
On 05/24/2018 10:54 AM, Aleksandar Lazic wrote:
I remembert that Willy mentioned this in any of his mail.
Do you have any rough timeline, this year, next year something like this
;-)
We're aiming to have the native internal HTTP repres
Hello Aleks,
On 05/24/2018 10:54 AM, Aleksandar Lazic wrote:
I remembert that Willy mentioned this in any of his mail.
Do you have any rough timeline, this year, next year something like this
;-)
We're aiming to have the native internal HTTP representation completed
for 1.9 which is slated
Would that I could gift you time away from lesser things (fix the
plumbing? make breakfast?) from across the ocean ...
I do have some small sense of how ...
overwhelming/consuming/pressing/stressful/... driving a project the size
and stature (and awesome capability) of haproxy would be.
Huge tha
Willy, I think you've reviewed this one already. :) I fixed a few
things after your review, then you said you just wanted to wait
for Baptiste to ACK back on 4/27.
I pinged Baptiste independently, just to make sure he had
seen your note. He replied, but he's been busy too. (Sorry
to add to the pil
Hi Jim,
On Thu, May 24, 2018 at 08:50:29AM -0600, Jim Freeman wrote:
> I'm not seeing any signs of this feature sliding into 1.9 source - any
> danger of it not going in to the current dev branch?
> Are there further concerns/problems/... standing in the way ? (it
> addresses one of my few haprox
Hi Daniel.
On 24/05/2018 10:09, Daniel Corbett wrote:
Hello Aleks,
gRPC is on our road map. We're currently working on implementing a
new native internal HTTP representation and that will bring us end to
end HTTP/2, which is the requirement for us to add gRPC.
I remembert that Willy mention
I'm not seeing any signs of this feature sliding into 1.9 source - any
danger of it not going in to the current dev branch?
Are there further concerns/problems/... standing in the way ? (it
addresses one of my few haproxy gripes)
...jfree
[ grateful/impressed haproxy user - thanks to all involved
Hello Aleks,
gRPC is on our road map. We're currently working on implementing a new
native internal HTTP representation and that will bring us end to end
HTTP/2, which is the requirement for us to add gRPC.
In regards to the gRPC lua script -- thanks for sharing. It's the first
time I have
On Thu, May 24, 2018 at 02:38:58PM +0200, Thierry Fournier wrote:
> I do not observe error during runtime, my only one problem is the
> compilation. I don't understand the impact of these modification,
> and so I can't test, because I don't known the impact on the
> polling.
(...)
Don't worry, I'v
> On 22 May 2018, at 19:03, Willy Tarreau wrote:
>
> Hi Thierry,
>
> On Mon, May 21, 2018 at 07:58:01PM +0200, Thierry Fournier wrote:
>> Hi,
>>
>> You will two patches in attachment.
>>
>> - The first fix some Lua error messages
>
> thanks, I've merged this one already.
>
>> - The second
Recently I've moved several servers from haproxy 1.7.x to 1.8.x I have
a setup with nghttpx handling h2 (haproxy connects to nghttpx via unix
socket which handles h2 and connects back to haproxy with plain
http/1.1 also through unix socket).
After the upgrade I wanted to switch to native h2 suppor
On Thu, May 24, 2018 at 10:07:23AM +0200, William Dauchy wrote:
> On Wed, May 23, 2018 at 08:45:04PM +0200, William Dauchy wrote:
> > More details which could help understand what is going on:
> >
> > ps output:
> >
> > root 15928 0.3 0.0 255216 185268 ? Ss May21 10:11
> > /usr/sbin
Hi Lukas,
On 05/24/2018 11:27 AM, Lukas Tribus wrote:
> Hi Emeric,
>
>
> On 24 May 2018 at 11:19, Emeric Brun wrote:
>> in pre6 there is a news wrapping function on getrandom which have different
>> fallback way to use the syscall.
>>
>> Perhaps the openssl -r output depends of that (if getran
Hi Emeric,
On 24 May 2018 at 11:19, Emeric Brun wrote:
> in pre6 there is a news wrapping function on getrandom which have different
> fallback way to use the syscall.
>
> Perhaps the openssl -r output depends of that (if getrandom was found from
> glibc or if a syscall loaded from a different
Hi Lukas,
On 05/23/2018 09:48 PM, Lukas Tribus wrote:
> Hello,
>
>
> On 23 May 2018 at 18:29, Emeric Brun wrote:
>> This issue was due to openssl-1.1.1 which re-seed after an elapsed time or
>> number of request.
>>
>> If /dev/urandom is used as seeding source when haproxy is chrooted it fails
On 05/23/2018 09:48 PM, Lukas Tribus wrote:
> Hello,
>
>
> On 23 May 2018 at 18:29, Emeric Brun wrote:
>> This issue was due to openssl-1.1.1 which re-seed after an elapsed time or
>> number of request.
>>
>> If /dev/urandom is used as seeding source when haproxy is chrooted it fails
>> to re-op
> Le 24 mai 2018 à 09:21, Hervé Commowick a
> écrit :
>
> I didn't know about the curves parameter, and i don't see performance
> regression with it. I don't really understand why this kind of parameter
> can influence certs loading time.
>
I don't know really why either.
"ecdhe" uses EC_KEY_
Hi, Christopher!
Could you tell if these patches will be backported to haproxy 1.8 or not?
2018-04-11 20:06 GMT+03:00 Максим Куприянов :
> Hi!
>
> Thank you very much for the patches. Looks like they helped.
>
> 2018-03-29 14:25 GMT+05:00 Christopher Faulet :
>
>> Le 28/03/2018 à 14:16, Максим К
Hi Stephan.
On 24/05/2018 10:16, Stephan Seitz wrote:
subscribe
Please use haproxy+subscr...@formilux.org as shown in
https://www.haproxy.org/#tact
Mit freundlichen Grüßen,
Stephan Seitz
Best regards
Aleks
--
Heinlein Support GmbH
Schwedter Str. 8/9b, 10119 Berlin
http://www.heinlein
subscribe
Mit freundlichen Grüßen,
Stephan Seitz
--
Heinlein Support GmbH
Schwedter Str. 8/9b, 10119 Berlin
http://www.heinlein-support.de
Tel: 030 / 405051-44
Fax: 030 / 405051-19
Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht
Berlin-Charlottenburg,
Geschäftsführer: Peer Heinlein -
On Wed, May 23, 2018 at 08:45:04PM +0200, William Dauchy wrote:
> More details which could help understand what is going on:
>
> ps output:
>
> root 15928 0.3 0.0 255216 185268 ? Ss May21 10:11
> /usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -sf
> 16988 1691
I didn't know about the curves parameter, and i don't see performance
regression with it. I don't really understand why this kind of parameter
can influence certs loading time.
Hervé.
Le 23/05/2018 à 15:08, Emmanuel Hocdet a écrit :
> Hi Hervé,
>
>> Le 22 mai 2018 à 10:31, Hervé Commowick a
>>
28 matches
Mail list logo
