Hi Cyril, Yes, I tried "make clean" first before compiling and still the same problem on 10.04 LTS.
Below is the output of "haproxy -vv": HA-Proxy version 1.5.1 2014/06/24 Copyright 2000-2014 Willy Tarreau <[email protected]> Build options : TARGET = linux2628 CPU = native CC = gcc CFLAGS = -O2 -march=native -g -fno-strict-aliasing OPTIONS = USE_OPENSSL=1 USE_STATIC_PCRE=1 Default settings : maxconn = 2000, bufsize = 16384, maxrewrite = 8192, maxpollevents = 200 Encrypted password support via crypt(3): yes Built without zlib support (USE_ZLIB not set) Compression algorithms supported : identity Built with OpenSSL version : OpenSSL 0.9.8k 25 Mar 2009 Running on OpenSSL version : OpenSSL 0.9.8k 25 Mar 2009 OpenSSL library supports TLS extensions : yes OpenSSL library supports SNI : yes OpenSSL library supports prefer-server-ciphers : yes Built with PCRE version : 7.8 2008-09-05 PCRE library supports JIT : no (USE_PCRE_JIT not set) Built with transparent proxy support using: IP_TRANSPARENT IPV6_TRANSPARENT IP_FREEBIND Available polling systems : epoll : pref=300, test result OK poll : pref=200, test result OK select : pref=150, test result OK Total: 3 (3 usable), will use epoll. Configuration below: global log 127.0.0.1 local1 info log 127.0.0.1 local1 notice maxconn 2000 chroot /usr/share/haproxy uid 99 gid 99 daemon defaults log global mode http option httplog option dontlognull retries 3 option redispatch option abortonclose maxconn 2000 timeout connect 5s timeout http-request 10s timeout http-keep-alive 500ms timeout client 600s timeout server 600s frontend public mode http bind 0.0.0.0:80 bind 0.0.0.0:443 ssl crt /path/to/my.pem no-sslv3 ciphers RC4:HIGH:!EXP:!LOW:!RC2:!3DES:!SEED:!aNULL:!eNULL:!MD5:!EDH option forwardfor except 127.0.0.1 reqadd X-Forwarded-Proto:\ https if { ssl_fc } reqadd X-Forwarded-Proto:\ http if !{ ssl_fc } redirect scheme https if !{ ssl_fc } # define ACLs ... # define rules ... backend mybackend_1 ... backend mybackend_2 ... Again, the same version and configs work fine on Ubuntu 12.04 LTS. Do you see any problem above? Thanks. Best regards, Merton On Sat, Jul 5, 2014 at 2:19 AM, Cyril Bonté <[email protected]> wrote: > Hi Merton, > > Le 04/07/2014 18:44, Merton Lister a écrit : > > 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 to >> the 1.5-dev-26 binary and the problem disappeared. >> >> The only thing I changed in the config file for 1.5.1 was adding the >> following line to the global section: >> >> tune.ssl.default-dh-param 1024 >> >> since without it HAProxy complained at startup: 'Starting haproxy: >> [WARNING] 170/090803 (38826) : Setting tune.ssl.default-dh-param to 1024 >> by default, if your workload permits it you should set it to at least >> 2048. Please set a value>= 1024 to make this warning disappear.' >> >> Strangely enough, on another Ubuntu 12.04 LTS box, even without the >> 'tune.ssl.default-dh-param' setting, HAProxy 1.5.1 starts without any >> warning and works fine too. >> >> Not sure what is going on here. Any thought? >> > > Did you make a "make clean" before compiling ? > > Also, can you provide the output of "haproxy -vv" and your configuration > (without sensitive data) ? > > > -- > Cyril Bonté >
