When haproxy is restarted the original process remains leaving multiple haproxies running
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nova-cloud-controller (Juju Charms Collection) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
While testing https:/
root@juju-
haproxy 10061 1 0 14:53 ? 00:00:00 /usr/sbin/haproxy -f /etc/haproxy/
haproxy 27031 1 0 15:06 ? 00:00:00 /usr/sbin/haproxy -f /etc/haproxy/
root@juju-
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1051/sshd
tcp 0 0 0.0.0.0:8888 0.0.0.0:* LISTEN 27031/haproxy
tcp 0 0 0.0.0.0:8888 0.0.0.0:* LISTEN 10061/haproxy
tcp 0 0 0.0.0.0:8763 0.0.0.0:* LISTEN 13761/python
tcp 0 0 0.0.0.0:3323 0.0.0.0:* LISTEN 13808/python
tcp 0 0 0.0.0.0:8764 0.0.0.0:* LISTEN 13782/python
tcp 0 0 0.0.0.0:9696 0.0.0.0:* LISTEN 10061/haproxy
tcp 0 0 0.0.0.0:3333 0.0.0.0:* LISTEN 27031/haproxy
tcp 0 0 0.0.0.0:8773 0.0.0.0:* LISTEN 27031/haproxy
tcp 0 0 0.0.0.0:3333 0.0.0.0:* LISTEN 10061/haproxy
tcp 0 0 0.0.0.0:8773 0.0.0.0:* LISTEN 10061/haproxy
tcp 0 0 0.0.0.0:8774 0.0.0.0:* LISTEN 27031/haproxy
tcp 0 0 0.0.0.0:8774 0.0.0.0:* LISTEN 10061/haproxy
tcp6 0 0 :::22 :::* LISTEN 1051/sshd
tcp6 0 0 :::80 :::* LISTEN 7327/apache2
Changed in nova-cloud-controller (Juju Charms Collection): | |
status: | Confirmed → Fix Released |
It sounds like bug #1477198 (SRU in progress).