please open an issue at https://github.com/haproxy/haproxy/issues also, do you have collected dump file (as your output says "core dumped"), maybe coredumpctl or so ? if you do, it would be great to provide gdb backtrace
вт, 25 авг. 2020 г. в 00:02, Milen Simeonov <[email protected]>: > I've got an issue after HAProxy 2.0.17 upgrade to 2.2.2 > > > ## Detailed description of the problem > > The following packages will be upgraded: > haproxy > 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > Need to get 1,702 kB of archives. > After this operation, 547 kB of additional disk space will be used. > Do you want to continue? [Y/n] > Get:1 http://ppa.launchpad.net/vbernat/haproxy-2.2/ubuntu focal/main > amd64 haproxy amd64 2.2.2-1ppa1~focal [1,702 kB] > Fetched 1,702 kB in 1s (1,652 kB/s) > (Reading database ... 114932 files and directories currently installed.) > Preparing to unpack .../haproxy_2.2.2-1ppa1~focal_amd64.deb ... > Unpacking haproxy (2.2.2-1ppa1~focal) over (2.0.15-1ppa1~bionic) ... > Setting up haproxy (2.2.2-1ppa1~focal) ... > Job for haproxy.service failed. > See "systemctl status haproxy.service" and "journalctl -xe" for details. > invoke-rc.d: initscript haproxy, action "reload" failed. > Processing triggers for man-db (2.9.1-1) ... > Processing triggers for rsyslog (8.2001.0-1ubuntu1.1) ... > Processing triggers for systemd (245.4-4ubuntu3.2) ... > Reading package lists... Done > Building dependency tree > Reading state information... Done > > service haproxy restart > Job for haproxy.service failed because a fatal signal was delivered > causing the control process to dump core. > See "systemctl status haproxy.service" and "journalctl -xe" for details. > systemctl status haproxy.service > ● haproxy.service - HAProxy Load Balancer > Loaded: loaded (/lib/systemd/system/haproxy.service; enabled; vendor > preset: enabled) > Active: failed (Result: core-dump) since Mon 2020-08-24 05:20:21 CDT; > 36s ago > Docs: man:haproxy(1) > file:/usr/share/doc/haproxy/configuration.txt.gz > Process: 17050 ExecStartPre=/usr/sbin/haproxy -f $CONFIG -c -q > $EXTRAOPTS (code=dumped, signal=ABRT) > Aug 24 05:20:21 k2 systemd[1]: haproxy.service: Scheduled restart job, > restart counter is at 5. > Aug 24 05:20:21 k2 systemd[1]: Stopped HAProxy Load Balancer. > Aug 24 05:20:21 k2 systemd[1]: haproxy.service: Start request repeated too > quickly. > Aug 24 05:20:21 k2 systemd[1]: haproxy.service: Failed with result > 'core-dump'. > Aug 24 05:20:21 k2 systemd[1]: Failed to start HAProxy Load Balancer. > > haproxy -f /etc/haproxy/haproxy.cfg -c > Configuration file is valid > free(): invalid pointer > Aborted (core dumped) > > > ## Expected behavior > > HAproxy 2.2.2 to work > > ## Steps to reproduce the behavior > > The following configuration, derived from the one you posted above, is > enough to reproduce the issue with haproxy 2.2-dev11: > global > log /dev/log local0 > log /dev/log local1 notice > chroot /var/lib/haproxy > stats socket /run/haproxy/admin.sock mode 660 level admin expose-fd > listeners > stats timeout 30s > user haproxy > group haproxy > daemon > defaults > log global > mode http > maxconn 50000 > option httplog > option dontlognull > retries 3 > timeout connect 5s > timeout client 50s > timeout client-fin 50s > timeout server 50s > frontend fe_main > bind 127.0.0.1:443 ssl crt-list > /etc/haproxy/certs/websites.crt_list > default_backend be_main > backend be_main > mode http > server localhost 127.0.0.1:80 > haproxy -c -f will error out. > > > ## Do you have any idea what may have caused this? > No, I haven't > > ## Do you have an idea how to solve the issue? > No, I haven't > > > > > Kind Regards, > -- > *Milen Simeonov* > IT Team Leader > Kukui Corporation <http://www.kukui.com> > > > CONFIDENTIALITY NOTICE: This Email and any attachments may contain > private, confidential, and privileged material is for the sole use of Kukui > Corporation to the intended recipient. Any review, copying, or distribution > of this email and any attachments by others is strictly prohibited. If you > are not the intended recipient, please contact the sender immediately and > permanently delete the original and any copies of this email and any > attachments thereto. >
