"initctl list" shows 11974 instances of network-interface-security after two days of uptime
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Incomplete
|
Medium
|
Unassigned | ||
lxc (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
On an Ubuntu 12.04.1 system, each time you start and stop a container,
"initctl status" shows two more instances of network-interface and network-
The numbers do not go down after the container shuts down.
Evidently there's an interface leak in lxc-start?
Here's how I ran into this.
Hosting a small number of buildbots in
one-shot ephemeral LXC containers,
in which the LXC container is stop and started after each build,
after two days of uptime, running the commands
while true
do
time initctl list | awk '{print $1}' | sort | uniq -c | sort -n | tail -n 3
done
outputs
1 wait-for-state
6003 network-interface
11990 network-
real 0m19.428s
1 wait-for-state
6004 network-interface
11994 network-
real 0m19.271s
If I stop the buildbots, the numbers stop rising.
This broke my build.
I can work around this by rebooting every night, but I'd sure rather not.
Changed in lxc (Ubuntu): | |
importance: | Undecided → High |
tags: | added: patch |
Yup, I can reproduce this. However I believe the bug is in the init script, not in lxc. The veth interfaces are not around.