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.
** Also affects: haproxy (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: haproxy (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: haproxy (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: haproxy (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828496
Title:
service haproxy reload sometimes fails to pick up new TLS certificates
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1828496/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
