Comment 16 for bug 1828496

Revision history for this message
Haw Loeung (hloeung) wrote :

Saw this elsewhere, on Bionic:

| root 6522 0.0 0.7 2089380 2035060 ? Ss Mar11 0:36 /usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -sf 60208 12488 19796 -x /run/haproxy/admin.sock
| haproxy 19796 0.0 0.5 8374612 1518588 ? Ssl Mar12 370:39 \_ /usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -sf 62903 -x /run/haproxy/admin.sock
| haproxy 63249 0.0 0.5 8490864 1468892 ? Ssl 19:13 185:53 \_ /usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -sf 60208 12488 19796 -x /run/haproxy/admin.sock

New configs weren't made live because the old process was still around, even after a reload and HAProxy spawning a new.