Re: [PATCH] MEDIUM: ssl: disable SSLv3 per default for bind

Hello, Am 23.05.2017 um 17:17 schrieb Emmanuel Hocdet: > Hi, > > I think it’s time to disable SSLv3 on bind line per default. > All configurations should have no-sslv3 (or used a ssllib without sslv3). > SSLv3 can be enable with "ssl-min-ver SSLv3. > > What do you think? +1 agreed, no need to

Re: Haproxy first core 100%

Hello Haim, Am 25.05.2017 um 09:23 schrieb Haim Ari: > > Hello, > > > I'll try do describe the issue as clear as possible: > > > We set up an haproxy Cluster on Ubuntu16.04 + pacemaker + corosync > > We faced an issue where after working for a few hours with single core > (the haproxy process

Re: OneConnect feature in HAProxy

On 05/25/2017 08:26 AM, James Stroehmann wrote: Is there a feature in HAProxy similar to OneConnect that the F5 LTM has? https://www.f5.com/pdf/deployment-guides/oneconnect-tuning-dg.pdf I am trying to migrate some frontends from an LTM to an HAProxy load balancer, and a few of the existing

OneConnect feature in HAProxy

Is there a feature in HAProxy similar to OneConnect that the F5 LTM has? https://www.f5.com/pdf/deployment-guides/oneconnect-tuning-dg.pdf I am trying to migrate some frontends from an LTM to an HAProxy load balancer, and a few of the existing frontends have the OneConnect feature turned on. I

Re: Haproxy first core 100%

Just some more info on this I noticed there is a single haproxy process (nbproc 8) that uses 100% CPU when hitting '1' on 'top' command we see that every minute or two, different core becomes utilized (75%) So according to the CPU maps it jumps between Cores 1,3,5,7 strace: Process 82882

Haproxy first core 100%

Hello, I'll try do describe the issue as clear as possible: We set up an haproxy Cluster on Ubuntu16.04 + pacemaker + corosync We faced an issue where after working for a few hours with single core (the haproxy process was bind to core #1 not #0 - which is handling the IRQ interrupts ) it