Re: Strange crash of HAProxy 1.5.1

Hi everyone, Thanks a lot for the suggestions and discussion. Below are some more info as requested. Hopefully they can lead to a definitive diagnosis of the problem. It looks like the CPU=native parameter above results in some machine code generated during compilation which cannot be executed

Re: Strange crash of HAProxy 1.5.1

Hi Lukas, I tried compiling with make CFLAGS=-g -O0, but it complained that the TARGET variable must be specified. So I compiled using: make CFLAGS=-g -O0 TARGET=linux2628 USE_OPENSSL=1. Funny enough, the compiled binary did not crash anymore. I then tried: make CFLAGS=-g -O0 TARGET=linux2628

Strange crash of HAProxy 1.5.1

Hello, I just compiled and installed HAProxy 1.5.1, and it didn't give any error. However, after I restarted HAProxy using the latest binary, any request (e.g. a simple GET for robots.txt) will simply crash the HAProxy process. I'm running it on an Ubuntu 10.04 LTS box, and I just switched back

Re: 'SSL handshake failure' errors

Thank you Lukas. We will see whether SSLv3 improves things. Best, Merton On Wed, Jun 19, 2013 at 1:15 AM, Lukas Tribus luky...@hotmail.com wrote: Hi Merton! don't forget to CC the mailing-list :) Out of the 5 possible causes you listed, we probably can't do much about the other

'SSL handshake failure' errors

Hi, We are seeing a fair amount of 'SSL handshake failure' errors in our log, and we are running HAProxy 1.5-dev18. The pattern of errors is: Jun 17 20:00:28 localhost.localdomain haproxy[26060]: 68.xxx.xx.216:56030 [17/Jun/2013:20:00:28.002] public/2: SSL handshake failure The following are

Re: 'maxconn' usages

How much free memory do you have left and how much does your backend software consume per connection? I have about 800 mb memory left when all services are running (with minimal traffic and load). The per-connection memory usage of my backend is about 25 kb. Given the purpose and normal usage

Re: 'maxconn' usages

Thanks a lot for the clarifications. So now I understand the differences between 'maxconn' in different places: 1. if it is in the global section, it specifies the maximum number of concurrent connections the HAProxy process will handle at any point of time. 2. if it is in a frontend section, it

Re: 'maxconn' usages

Hi Lukas, Thanks very much for your confirmations and the Stackoverflow post. I just want to expand a little on the last question relating to websockets connections. Let's say I have a backend which exclusively deal with long-lived connections: websockets and xdr-streaming. These connections

'maxconn' usages

Hi, I've read that lowering 'maxconn' number can make the services faster and can also prevent connection flooding. However, in the HAProxy doc, it is a little confusing whether we should use 'maxconn' globally, set it with a default, or on a specific backend (or any combination of the three).