Unable to stop a container (waiting for lo to become free)

S

Smanux

Renowned Member
Jun 29, 2009
39
4
73
Hi,

I created a new container from the Debian 5.0 i386 minimal template available on the OpenVZ site (http://download.openvz.org/template/precreated/contrib/debian-5.0-i386-minimal.tar.gz). I already used this template for other containers on the same server, but this time I added only an IPv6 address and no IPv4. I started the container, and on entering there was no network connectivity outside the container. Here is the content of the generated /etc/network/interface file, there was a 127.0.0.1 address bound to venet0 that seemed unusual :

Code: 
# Auto generated lo interface
auto lo
iface lo inet loopback

# Auto generated venet0 interface
auto venet0
iface venet0 inet static
        address 127.0.0.1
        netmask 255.255.255.255
        broadcast 0.0.0.0
        up route add -net 192.0.2.1 netmask 255.255.255.255 dev venet0
        up route add default gw 192.0.2.1

iface venet0 inet6 static
        address ::1
        netmask 128
        up ifconfig venet0 add 2001:xxxx:xxxx::4/0
So I tried to stop the container and the real troubles began. The container didn't stop and the following message is now printed on all open consoles every 10 seconds :

Code: 
Message from syslogd@nexus at Mar 11 02:17:57 ...
 kernel:unregister_netdevice: waiting for lo to become free. Usage count = 4
Is there a way to stop these messages without restarting the system? It seems to disrupt the network of the other containers, some are still available, others aren't. The web manager is still available on the host, but it's impossible to open new SSH connections, they just time out.

Here is the result of pveversion -v :

Code: 
pve-manager: 1.5-8 (pve-manager/1.5/4674)
running kernel: 2.6.24-10-pve
proxmox-ve-2.6.24: 1.5-21
pve-kernel-2.6.24-7-pve: 2.6.24-11
pve-kernel-2.6.24-10-pve: 2.6.24-21
pve-kernel-2.6.24-5-pve: 2.6.24-6
pve-kernel-2.6.24-2-pve: 2.6.24-5
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-10
vncterm: 0.9-2
vzctl: 3.0.23-1pve8
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.11.1-2
The kernel used is 2.6.24-10-pve

Thank you for your help.
 
I also noticed these traces in /var/log/kern.log :

Code: 
Mar 11 01:48:45 nexus kernel: CT: 104: started
Mar 11 01:48:46 nexus kernel: ioctl32(mount:27378): Unknown cmd fd(3) cmd(80041272){t:12;sz:4} arg(bf899448) on /
Mar 11 01:48:46 nexus kernel: ioctl32(mount:27378): Unknown cmd fd(3) cmd(00001260){t:12;sz:0} arg(bf899450) on /
Mar 11 01:48:46 nexus kernel: ioctl32(mount:27378): Unknown cmd fd(3) cmd(801c0204){t:02;sz:28} arg(bf89942c) on /
Mar 11 01:48:46 nexus kernel: ioctl32(mount:27378): Unknown cmd fd(3) cmd(80041272){t:12;sz:4} arg(bf899448) on /
Mar 11 01:48:46 nexus kernel: ioctl32(mount:27378): Unknown cmd fd(3) cmd(00001260){t:12;sz:0} arg(bf899450) on /
Mar 11 01:48:46 nexus kernel: ioctl32(mount:27378): Unknown cmd fd(3) cmd(801c0204){t:02;sz:28} arg(bf89942c) on /
Mar 11 01:53:24 nexus kernel: WARNING: at include/net/dst.h:165 dst_release()
Mar 11 01:53:24 nexus kernel: Pid: 27957, comm: ifconfig Not tainted 2.6.24-10-pve #1
Mar 11 01:53:24 nexus kernel:
Mar 11 01:53:24 nexus kernel: Call Trace:
Mar 11 01:53:24 nexus kernel: [<ffffffff883d835e>] :ipv6:__ip6_del_rt+0x6e/0xc0
Mar 11 01:53:24 nexus kernel: [<ffffffff883ca4b8>] :ipv6:aca_put+0xa8/0xb0
Mar 11 01:53:24 nexus kernel: [<ffffffff883ca569>] :ipv6:__ipv6_dev_ac_dec+0xa9/0x100
Mar 11 01:53:24 nexus kernel: [<ffffffff883cfd02>] :ipv6:addrconf_leave_anycast+0x82/0xa0
Mar 11 01:53:24 nexus kernel: [<ffffffff883d1de8>] :ipv6:__ipv6_ifa_notify+0x1f8/0x240
Mar 11 01:53:24 nexus kernel: [<ffffffff883d4ae8>] :ipv6:addrconf_ifdown+0x308/0x3e0
Mar 11 01:53:24 nexus kernel: [<ffffffff883d627f>] :ipv6:addrconf_notify+0xef/0xad0
Mar 11 01:53:24 nexus kernel: [<ffffffff883dbcec>] :ipv6:fib6_clean_node+0x1c/0xb0
Mar 11 01:53:24 nexus kernel: [<ffffffff883daec0>] :ipv6:fib6_walk+0x90/0xa0
Mar 11 01:53:24 nexus kernel: [<ffffffff883db399>] :ipv6:fib6_clean_all+0xc9/0x150
Mar 11 01:53:24 nexus kernel: [<ffffffff883dbcd0>] :ipv6:fib6_clean_node+0x0/0xb0
Mar 11 01:53:24 nexus kernel: [<ffffffff80431ed3>] skb_dequeue+0x53/0x80
Mar 11 01:53:24 nexus kernel: [<ffffffff883daaa0>] :ipv6:fib6_age+0x0/0x90
Mar 11 01:53:24 nexus kernel: [<ffffffff804cc2c7>] notifier_call_chain+0x37/0x70
Mar 11 01:53:24 nexus kernel: [<ffffffff8043b2fa>] dev_close+0x6a/0x70
Mar 11 01:53:24 nexus kernel: [<ffffffff8043af22>] dev_change_flags+0x92/0x1c0
Mar 11 01:53:24 nexus kernel: [<ffffffff8049604b>] devinet_ioctl+0x7ab/0x7c0
Mar 11 01:53:24 nexus kernel: [<ffffffff8042a3a6>] sock_ioctl+0x76/0x290
Mar 11 01:53:24 nexus kernel: [<ffffffff802e18cf>] do_ioctl+0x2f/0xb0
Mar 11 01:53:24 nexus kernel: [<ffffffff802e1bdb>] vfs_ioctl+0x28b/0x300
Mar 11 01:53:24 nexus kernel: [<ffffffff802e1c99>] sys_ioctl+0x49/0x80
Mar 11 01:53:24 nexus kernel: [<ffffffff804cbb76>] do_page_fault+0x176/0x890
Mar 11 01:53:24 nexus kernel: [<ffffffff8030f043>] dev_ifsioc+0x73/0x2c0
Mar 11 01:53:24 nexus kernel: [<ffffffff8030fd2b>] compat_sys_ioctl+0x11b/0x3e0
Mar 11 01:53:24 nexus kernel: [<ffffffff8042aaa9>] sock_map_fd+0x49/0x80
Mar 11 01:53:24 nexus kernel: [<ffffffff8022aae2>] ia32_sysret+0x0/0xa
Mar 11 01:53:24 nexus kernel:
Mar 11 01:53:24 nexus kernel: ioctl32(mount:27979): Unknown cmd fd(3) cmd(80041272){t:12;sz:4} arg(bf9897e8) on /
Mar 11 01:53:24 nexus kernel: ioctl32(mount:27979): Unknown cmd fd(3) cmd(00001260){t:12;sz:0} arg(bf9897f0) on /
Mar 11 01:53:24 nexus kernel: ioctl32(mount:27979): Unknown cmd fd(3) cmd(801c0204){t:02;sz:28} arg(bf9897cc) on /
Mar 11 01:53:24 nexus kernel: ioctl32(mount:27979): Unknown cmd fd(3) cmd(80041272){t:12;sz:4} arg(bf9897e8) on /
Mar 11 01:53:24 nexus kernel: ioctl32(mount:27979): Unknown cmd fd(3) cmd(00001260){t:12;sz:0} arg(bf9897f0) on /
Mar 11 01:53:24 nexus kernel: ioctl32(mount:27979): Unknown cmd fd(3) cmd(801c0204){t:02;sz:28} arg(bf9897cc) on /
Mar 11 01:53:26 nexus kernel: WARNING: at include/net/dst.h:165 dst_release()
Mar 11 01:53:26 nexus kernel: Pid: 15, comm: events/0 Not tainted 2.6.24-10-pve #1
Mar 11 01:53:26 nexus kernel:
Mar 11 01:53:26 nexus kernel: Call Trace:
Mar 11 01:53:26 nexus kernel: [<ffffffff883d835e>] :ipv6:__ip6_del_rt+0x6e/0xc0
Mar 11 01:53:26 nexus kernel: [<ffffffff883ca4b8>] :ipv6:aca_put+0xa8/0xb0
Mar 11 01:53:26 nexus kernel: [<ffffffff883ca569>] :ipv6:__ipv6_dev_ac_dec+0xa9/0x100
Mar 11 01:53:26 nexus kernel: [<ffffffff883cfd02>] :ipv6:addrconf_leave_anycast+0x82/0xa0
Mar 11 01:53:26 nexus kernel: [<ffffffff883d1de8>] :ipv6:__ipv6_ifa_notify+0x1f8/0x240
Mar 11 01:53:26 nexus kernel: [<ffffffff883d4ae8>] :ipv6:addrconf_ifdown+0x308/0x3e0
Mar 11 01:53:26 nexus kernel: [<ffffffff80436e80>] cleanup_net+0x0/0xd0
Mar 11 01:53:26 nexus kernel: [<ffffffff883d4bf9>] :ipv6:addrconf_net_exit+0x39/0x70
Mar 11 01:53:26 nexus kernel: [<ffffffff80436efe>] cleanup_net+0x7e/0xd0
Mar 11 01:53:26 nexus kernel: [<ffffffff80256506>] run_workqueue+0x86/0x150
Mar 11 01:53:26 nexus kernel: [<ffffffff80256673>] worker_thread+0xa3/0x110
Mar 11 01:53:26 nexus kernel: [<ffffffff8025c220>] autoremove_wake_function+0x0/0x30
Mar 11 01:53:26 nexus kernel: [<ffffffff802565d0>] worker_thread+0x0/0x110
Mar 11 01:53:26 nexus kernel: [<ffffffff8025be77>] kthread+0x47/0x90
Mar 11 01:53:26 nexus kernel: [<ffffffff8020d4e8>] child_rip+0xa/0x12
Mar 11 01:53:26 nexus kernel: [<ffffffff8025be30>] kthread+0x0/0x90
Mar 11 01:53:26 nexus kernel: [<ffffffff8020d4de>] child_rip+0x0/0x12
Mar 11 01:53:26 nexus kernel:
Mar 11 01:53:37 nexus kernel: unregister_netdevice: waiting for lo to become free. Usage count = 4
Mar 11 01:53:47 nexus kernel: unregister_netdevice: waiting for lo to become free. Usage count = 4
Mar 11 01:53:57 nexus kernel: unregister_netdevice: waiting for lo to become free. Usage count = 4
 
You must log in or register to reply here.
Top Bottom