Lukas, We build all of our RPM’s w/ statically linked libraries, aka FatRPM’s or Omnibus packages. You can see its using openssl which is bundled w/ the ‘omnibus’
Production ( currently running 1.5.4) COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME haproxy 32645 haproxy cwd DIR 202,64 4096 143421 /etc/haproxy haproxy 32645 haproxy rtd DIR 202,64 4096 2 / haproxy 32645 haproxy txt REG 202,64 4346693 18856 /opt/haproxy/embedded/sbin/haproxy haproxy 32645 haproxy mem REG 202,64 110960 397813 /lib64/libresolv-2.12.so haproxy 32645 haproxy mem REG 202,64 27424 397086 /lib64/libnss_dns-2.12.so haproxy 32645 haproxy mem REG 202,64 65928 397811 /lib64/libnss_files-2.12.so haproxy 32645 haproxy mem REG 202,64 19536 397807 /lib64/libdl-2.12.so haproxy 32645 haproxy mem REG 202,64 383504 397320 /lib64/libfreebl3.so haproxy 32645 haproxy mem REG 202,64 1921176 397298 /lib64/libc-2.12.so haproxy 32645 haproxy mem REG 202,64 2191352 17645 /opt/haproxy/embedded/lib/libcrypto.so.1.0.0 haproxy 32645 haproxy mem REG 202,64 480945 17695 /opt/haproxy/embedded/lib/libssl.so.1.0.0 haproxy 32645 haproxy mem REG 202,64 121833 17706 /opt/haproxy/embedded/lib/libz.so.1.2.6 which is bundled w/ openssl 1.0.1i [root@lb1a log]# /opt/haproxy/embedded/bin/openssl version OpenSSL 1.0.1i 6 Aug 2014 [root@lb1a log]# on the production server, which gets no traffic other then internal testing, I have the following: Staging ( currently running 1.5.11) COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME haproxy 10976 haproxy cwd DIR 202,64 4096 145762 /etc/haproxy haproxy 10976 haproxy rtd DIR 202,64 4096 2 / haproxy 10976 haproxy txt REG 202,64 4394002 16976 /opt/haproxy/embedded/sbin/haproxy haproxy 10976 haproxy mem REG 202,64 65928 397350 /lib64/libnss_files-2.12.so haproxy 10976 haproxy mem REG 202,64 19536 397314 /lib64/libdl-2.12.so haproxy 10976 haproxy mem REG 202,64 383504 397320 /lib64/libfreebl3.so haproxy 10976 haproxy mem REG 202,64 1916568 397300 /lib64/libc-2.12.so haproxy 10976 haproxy mem REG 202,64 2566713 11704 /opt/haproxy/embedded/lib/libcrypto.so.1.0.0 haproxy 10976 haproxy mem REG 202,64 534856 11763 /opt/haproxy/embedded/lib/libssl.so.1.0.0 haproxy 10976 haproxy mem REG 202,64 121841 12354 /opt/haproxy/embedded/lib/libz.so.1.2.6 haproxy 10976 haproxy mem REG 202,64 40400 397309 /lib64/libcrypt-2.12.so haproxy 10976 haproxy mem REG 202,64 154504 393719 /lib64/ld-2.12.so [root@lb-staging haproxy]# /opt/haproxy/embedded/bin/openssl version OpenSSL 1.0.2a 19 Mar 2015 [root@lb-staging haproxy]# -John -- John Dyer Sent with Airmail On April 2, 2015 at 12:04:09 PM, Lukas Tribus ([email protected]) wrote: > Lukas, > > Thank you for responding. Here is the output as requested Clearly on your production box you have openssl1.0.1 and on your staging box you have openssl1.0.2. But you cannot compile on your staging box linking against openssl 1.0.2 and then put that executable on your production box where openssl 1.0.1 is installed. The output we need to check this is the output of haproxy -vv of the 1.5.11 executable from your production box (aka on the system where the crash happend). Regards, Lukas
