Hi list,

We've recently tried to upgrade from 1.8.0 to 1.8.1, then 1.8.2, 1.8.3
on a preprod environment and noticed that the reload is not so seamless
since 1.8.1 (easily getting TCP RSTs while reloading).

Having a short look on the haproxy-1.8 git remote on the changes
affecting haproxy.c, c2b28144 can be eliminated, so 3 commits remains:

* 3ce53f66 MINOR: threads: Fix pthread_setaffinity_np on FreeBSD.  (5
weeks ago)
* f926969a BUG/MINOR: mworker: detach from tty when in daemon mode  (5
weeks ago)
* 4e612023 BUG/MINOR: mworker: fix validity check for the pipe FDs  (5
weeks ago)

In case it matters: we use threads and did the usual worker setup (which
again works very well in 1.8.0).
Here is a config extract:

$ cat /etc/haproxy/haproxy.cfg:
(...)
user haproxy
group haproxy
nbproc 1
daemon
stats socket /var/lib/haproxy/stats level admin mode 644 expose-fd listeners
stats timeout 2m
nbthread 11
(...)

$ cat /etc/sysconfig/haproxy
(...)
CONFIG="/etc/haproxy/haproxy.cfg"
PIDFILE="/run/haproxy.pid"
OPTIONS="-x /var/lib/haproxy/stats"
(...)

$ cat /usr/lib/systemd/system/haproxy.service
[Unit]
Description=HAProxy Load Balancer
After=syslog.target network.target

[Service]
EnvironmentFile=/etc/sysconfig/haproxy
ExecStartPre=/usr/sbin/haproxy -f $CONFIG -c -q
ExecStart=/usr/sbin/haproxy -W -f $CONFIG -p $PIDFILE $OPTIONS
ExecReload=/usr/sbin/haproxy -f $CONFIG -c -q
ExecReload=/bin/kill -USR2 $MAINPID
Type=forking
KillMode=mixed
Restart=always

Does the behavior observed sounds consistent regarding the changes that
occurred between 1.8.0 and 1.8.1 ? Before trying to bisect, compile,
test etc. I'd like to get your feedback.

Thanks in advance,

Pierre


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to