Can any help to fix this bug? I reported here long time ago.
On 14 August 2016 at 15:06, Tao Wang wrote:
> Hi,
>
> As the issue reported on Github haproxy repo are disabled, I transfer
> the issue here.
>
> I created a Github repo for this issue,
>
Hi Willy.
Thank you as always for the detailed answer.
Am 10-11-2016 06:51, schrieb Willy Tarreau:
Hi Aleks,
On Thu, Nov 10, 2016 at 12:52:22AM +0100, Aleksandar Lazic wrote:
> http://www.haproxy.org/download/1.7/doc/SPOE.txt
I have read the doc. very interesting.
When I understand
Hi Thomas,
Am 10.11.2016 um 22:20 schrieb Thomas Heil:
Also see:
https://www.openssl.org/docs/man1.1.0/crypto/ERR_remove_state.html
hmm. did i read correctly, that this function does nothing?
It does nothing in openssl 1.1.0, as it isn't required in that branch.
However it is required
Hey,
On 10.11.2016 19:13, Lukas Tribus wrote:
> Hi,
>
>
> Am 10.11.2016 um 18:27 schrieb Thomas Heil:
>> Hi,
>>
>> Iam facing a problem when building haproxy 1.6.9 with ssl for mips_24kc
>> with musl 1.1.15.
>> Openssl was building fine, but the function "ERR_remove_state(0)" does
>> not exist
> On Nov 9, 2016, at Nov 9, 4:45 AM, Azam Mohammed wrote:
>
> Also we have exact same Haproxy config on QA and UAT environment and works
> fine.
>
> QA Environment:
> Haproxy Version: HA-Proxy version 1.5.4
> OS Version: CentOS release 6.3 (Final)
>
> UAT Environment:
>
… please include the list in your responses too
> On Nov 10, 2016, at Nov 10, 4:09 AM, Azam Mohammed wrote:
>
> Hi Bryan,
>
> Thanks for your reply.
>
> Putting "use_backend test" first in Haproxy config worked fine.
>
> But I have few more question based on the solution.
Hi,
Am 10.11.2016 um 18:27 schrieb Thomas Heil:
Hi,
Iam facing a problem when building haproxy 1.6.9 with ssl for mips_24kc
with musl 1.1.15.
Openssl was building fine, but the function "ERR_remove_state(0)" does
not exist but
ERR_remove_thread_state(0); is available.
So does anybody know
Hi,
On 16-11-10 16:56:33, Willy Tarreau wrote:
> I removed you from the To in this response, but just as a hint we
> generally recommend to keep people CCed since most of us subscribed
> to lists have filters to automatically place them in the right box,
> and some people may participate without
On Thu, Nov 10, 2016 at 04:30:57PM +0100, ge...@riseup.net wrote:
> (Please don't Cc: me, I'm subscribed to the list.)
I removed you from the To in this response, but just as a hint we
generally recommend to keep people CCed since most of us subscribed
to lists have filters to automatically place
Hi Simon!
On Thu, Nov 10, 2016 at 04:27:15PM +0100, Simon Horman wrote:
> My preference is to take things calmly as TBH I am only just getting
> started on this and I think the schema could take a little time to get
> a consensus on.
I totally agree with you. I think the most difficult thing is
(Please don't Cc: me, I'm subscribed to the list.)
On 16-11-10 16:12:31, Willy Tarreau wrote:
> That's cool!
>
> The only thing is that I don't want to delay the release only for this,
> and at the same time I'm pretty sure it's possible to do something which
> will not impact existing code
On Thu, Nov 10, 2016 at 04:12:31PM +0100, Willy Tarreau wrote:
> Hi Malcolm,
>
> On Thu, Nov 10, 2016 at 12:53:13PM +, Malcolm Turnbull wrote:
> > Georg,
> >
> > That's a timely reminder thanks:
> > I just had another chat with Simon Horman who has kindly offered to
> > take a look at this
Hi Malcolm,
On Thu, Nov 10, 2016 at 12:53:13PM +, Malcolm Turnbull wrote:
> Georg,
>
> That's a timely reminder thanks:
> I just had another chat with Simon Horman who has kindly offered to
> take a look at this again.
That's cool!
The only thing is that I don't want to delay the release
On Thu, 10 Nov 2016, at 13:53, Malcolm Turnbull wrote:
> Georg,
>
> That's a timely reminder thanks:
> I just had another chat with Simon Horman who has kindly offered to
> take a look at this again.
Sounds great!
I'm very interested in logging this continually via chrooted unix
socket,
into
Georg,
That's a timely reminder thanks:
I just had another chat with Simon Horman who has kindly offered to
take a look at this again.
On 10 November 2016 at 10:54, ge...@riseup.net wrote:
> Hi all,
>
> On 16-07-05 10:05:13, Mark Brookes wrote:
>> I wondered if we could
Am 10.11.16 um 10:24 schrieb Pavlos Parissis:
> On 09/11/2016 09:20 μμ, Steven Le Roux wrote:
>> Hi a first good coverage for a comparison between 1.5 and 1.6 would be
>> http://blog.haproxy.com/2015/10/14/whats-new-in-haproxy-1-6/
>>
>> 1.6 is perfectly considered stable and hasn't seen any
Hi all,
On 16-07-05 10:05:13, Mark Brookes wrote:
> I wondered if we could start a discussion about the possibility of
> having the stats socket return stats data in JSON format.
After the discussion we had in July, I'm wondering what's the current
status regarding this topic?
Thanks and all
Hello Raghu,
On Thu, Nov 10, 2016 at 01:30:05PM +0530, Raghu Udiyar wrote:
> Hello
>
> We have developed a generic service (using python gevent) to serve as an
> agent check service for Haproxy. Its extensible via plugins for application
> feedback, and supports result cacheing, json
On 09/11/2016 09:20 μμ, Steven Le Roux wrote:
> Hi a first good coverage for a comparison between 1.5 and 1.6 would be
> http://blog.haproxy.com/2015/10/14/whats-new-in-haproxy-1-6/
>
> 1.6 is perfectly considered stable and hasn't seen any maintenance
> release for more than 2 months. It's being
Hello
We have developed a generic service (using python gevent) to serve as an
agent check service for Haproxy. Its extensible via plugins for application
feedback, and supports result cacheing, json expressions, arithmetic, regex
match, and fallback in case of failure.
The source is here :
20 matches
Mail list logo