Hi,

I created issue:  haproxy 2.1.3 issue with ssl on solaris 11 sru 950 #512

Nut really sure about gdb and bt full.
First time using it… had to install it first.
Is this what you need:

root@SYSTEM:/var/core# gdb --core=core_sz4203_haproxy_0_0_1582279635_18282
GNU gdb (GDB) 8.0
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "sparc-sun-solaris2.11".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
[New LWP 1]
[New LWP 1]
Core was generated by `/usr/local/sbin/haproxy -p /tmp/haproxy.pid -f 
/usr/local/etc/haproxy.cfg'.
Program terminated with signal SIGBUS, Bus error.
#0  0x0000000100242c90 in ?? ()
(gdb) bt full
#0  0x0000000100242c90 in ?? ()
No symbol table info available.
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Can you please guide me…

Met vriendelijke groet/Kind regards,

[cid:[email protected]]
Marcel Kloosterman
Specialist Technisch Beheer


KPN
N&I ACN P&TDC DC Cloud 1

Phone: +31612413284
Email: [email protected]<mailto:[email protected]>
TeamWiki (with spoc planning): 
https://confluence.kpn.org/display/KDU/KPN+DCLOUD+SOLARIS+CLOUD+TEAM+HOMEPAGE
(JIRA access is required and can be requested using IAM portal)
BTW nr.: NL0092.92.056B01
KvK: 27124701

The information transmitted is intended only for use by the addressee and may 
contain confidential and/or privileged material. Any review, re-transmission, 
dissemination or other use of it, or the taking of any action in reliance upon 
this information by persons and/or entities other than the intended recipient 
is prohibited. If you received this in error, please inform the sender and/or 
addressee immediately and delete the material. Thank you.

Van: Илья Шипицин <[email protected]>
Verzonden: vrijdag 21 februari 2020 10:24
Aan: Kloosterman, Marcel <[email protected]>
CC: HAProxy <[email protected]>
Onderwerp: Re: haproxy 2.1.2 and 2.1.3

useful things to debug would be

1) haorpxy -vv
2) config
3) bt full


can you please open a github issue at https://github.com/haproxy/haproxy/issues 
 ?

пт, 21 февр. 2020 г. в 13:55, 
<[email protected]<mailto:[email protected]>>:
Hi all,

At this moment we’re using  HA-Proxy version 2.0.0 2019/06/16 - 
https://haproxy.org/
And we’re running solaris 11.4 sru 950 for SPARC and I used developer studio 
version 12.6 to compile the newer versions and 12.5 to compile the 2.0.0 
version.

And because of a known bug in haproxy, we wanted to upgrade to: HA-Proxy 
version 2.1.2 2019/12/21 - https://haproxy.org/
On our test-server we had no problems but on the production server it kept 
crashing.
The problem is somehow related to ssl, because as soon as we add “ssl crt 
/etc/certs/self.pem” to the bind it crashes also on the test-server.
So then I checked and version 2.1.3 is already available, solving lots of ssl 
bugs. So I tried that one also…but without any luck ☹

Starting haproxy now gives a Bus Error (with both versons, 2.1.2 and 2.1.3):

root@sz4203:~ # /usr/local/sbin/haproxy -p /tmp/haproxy.pid -f 
/usr/local/etc/haproxy.cfg
Bus Error (core dumped)

Can you please help me solving this issue ?

This is the stack-dump of the 2.1.3 version I compiled:
root@s00501:/var/core# pstack core_sz4203_haproxy_0_0_1582273479_18461
core 'core_sz4203_haproxy_0_0_1582273479_18461' of 18461:       
/usr/local/sbin/haproxy -p /tmp/haproxy.pid -f /usr/local/etc/haproxy.
0000000100240c30 shctx_init (100366170, 4e20, c4, ffffffff, ffffffff7ec00144, 
0) + b0 (shctx.c:368)
0000000100086e7c ssl_sock_prepare_bind_conf (1005bbb80, ffffffff, 
fffffffefffffffc, ffffffff29729948, ffffffff00000000, 100366000) + 1bc
0000000100135278 check_config_validity (fffffffefffffffc, 1400, 1005bbb80, 
1005bb750, 100357238, 0) + 25b8 (cfgparse.c:3753)
0000000100173450 init (100357468, 1000596a0, 10005a940, 100357238, 10003aa90, 
0) + 610 (haproxy.c:1884)
0000000100178058 main (5, ffffffff7ffff688, ffffffff7ffff6b8, 100000, 
10046d680, 0) + 178 (haproxy.c:2858)
000000010006caa4 _start (0, 0, 0, 0, 0, 0) + 64

And this is how I compiled the 2.1.3 version:

PATH=/usr/gnu/bin:${PATH}:/opt/developerstudio12.6/bin/
cd ~bhr_kloos605/haproxy-2.1.3/
vi Makefile
Just to make sure that I can compile…changes:
root@sz4203:/export/home/bhr_kloos605# diff haproxy-2.1.3/Makefile 
haproxy-2.1.3.compiled/Makefile
137c137
< DESTDIR =
---
> DESTDIR = /tmp/haproxy
662c662,663
< OPTIONS_LDFLAGS += $(if $(PCRE_LIB),-L$(PCRE_LIB)) -Wl,-Bstatic -lpcreposix 
-lpcre -Wl,-Bdynamic
---
> #OPTIONS_LDFLAGS += $(if $(PCRE_LIB),-L$(PCRE_LIB)) -Wl,-Bstatic -lpcreposix 
> -lpcre -Wl,-Bdynamic
> OPTIONS_LDFLAGS += $(if $(PCRE_LIB),-L$(PCRE_LIB)) -Bstatic -lpcreposix -lpcre
make TARGET=solaris CPU=ultrasparc PCRE_LIB=/usr/lib PCRE_INC=/usr/include/pcre 
USE_STATIC_PCRE=1 USE_OPENSSL=1
make install

Can you please help ?


Met vriendelijke groet/Kind regards,

[cid:[email protected]]
Marcel Kloosterman
Specialist Technisch Beheer


KPN
N&I ACN P&TDC DC Cloud 1

Phone: +31612413284
Email: [email protected]<mailto:[email protected]>
TeamWiki (with spoc planning): 
https://confluence.kpn.org/display/KDU/KPN+DCLOUD+SOLARIS+CLOUD+TEAM+HOMEPAGE
(JIRA access is required and can be requested using IAM portal)
BTW nr.: NL0092.92.056B01
KvK: 27124701

The information transmitted is intended only for use by the addressee and may 
contain confidential and/or privileged material. Any review, re-transmission, 
dissemination or other use of it, or the taking of any action in reliance upon 
this information by persons and/or entities other than the intended recipient 
is prohibited. If you received this in error, please inform the sender and/or 
addressee immediately and delete the material. Thank you.

Reply via email to