Kernel[597]: unregister_netdevice: waiting for *network interface* to become free. Usage count = 3

#1

Hi,

We have a balena multicontainer device that flashed with the latest balenaOS 2.32.0+rev4.
The device is unable to get the services up an running, but they are downloaded.
We gave support access for a week, here’s the URI: https://dashboard.balena-cloud.com/devices/821b66d3c6b1b3636730955301f16681
Sometimes we see a lot of these errors in the host OS console:
kernel[597]: unregister_netdevice: waiting for *network interface* to become free. Usage count = 3
These issues also appear in the following github issue: https://github.com/moby/moby/issues/5618

We are using the following kernel: 4.18.14-yocto-standard

dmesg output:

[ 2898.906645] IPv6: ADDRCONF(NETDEV_CHANGE): veth649d128: link becomes ready
[ 2898.906714] br-2772ec63007d: port 1(veth649d128) entered blocking state
[ 2898.906718] br-2772ec63007d: port 1(veth649d128) entered forwarding state
[ 2900.776276] br-2772ec63007d: port 1(veth649d128) entered disabled state
[ 2900.776714] vethf0a7197: renamed from eth0
[ 2900.802416] br-2772ec63007d: port 1(veth649d128) entered disabled state
[ 2900.805242] device veth649d128 left promiscuous mode
[ 2900.805247] br-2772ec63007d: port 1(veth649d128) entered disabled state
[ 2900.974535] br-2772ec63007d: port 2(vethaccd002) entered disabled state
[ 2900.975687] veth0b48912: renamed from eth0
[ 2901.001931] br-2772ec63007d: port 2(vethaccd002) entered disabled state
[ 2901.004688] device vethaccd002 left promiscuous mode
[ 2901.004693] br-2772ec63007d: port 2(vethaccd002) entered disabled state
[ 2901.691453] br-2772ec63007d: port 1(veth6cabadf) entered blocking state
[ 2901.691457] br-2772ec63007d: port 1(veth6cabadf) entered disabled state
[ 2901.691568] device veth6cabadf entered promiscuous mode
[ 2901.691706] IPv6: ADDRCONF(NETDEV_UP): veth6cabadf: link is not ready
[ 2901.691709] br-2772ec63007d: port 1(veth6cabadf) entered blocking state
[ 2901.691712] br-2772ec63007d: port 1(veth6cabadf) entered forwarding state
[ 2901.718049] br-2772ec63007d: port 2(vethe668bfd) entered blocking state
[ 2901.718054] br-2772ec63007d: port 2(vethe668bfd) entered disabled state
[ 2901.718163] device vethe668bfd entered promiscuous mode
[ 2901.718319] IPv6: ADDRCONF(NETDEV_UP): vethe668bfd: link is not ready
[ 2901.718323] br-2772ec63007d: port 2(vethe668bfd) entered blocking state
[ 2901.718326] br-2772ec63007d: port 2(vethe668bfd) entered forwarding state
[ 2901.835545] br-2772ec63007d: port 1(veth6cabadf) entered disabled state
[ 2901.836013] br-2772ec63007d: port 2(vethe668bfd) entered disabled state
[ 2902.223849] eth0: renamed from veth0993ecf
[ 2902.229094] IPv6: ADDRCONF(NETDEV_CHANGE): veth6cabadf: link becomes ready
[ 2902.229158] br-2772ec63007d: port 1(veth6cabadf) entered blocking state
[ 2902.229161] br-2772ec63007d: port 1(veth6cabadf) entered forwarding state
[ 2902.277584] eth0: renamed from veth785c4c4
[ 2902.284249] IPv6: ADDRCONF(NETDEV_CHANGE): vethe668bfd: link becomes ready
[ 2902.284315] br-2772ec63007d: port 2(vethe668bfd) entered blocking state
[ 2902.284319] br-2772ec63007d: port 2(vethe668bfd) entered forwarding state
[ 2904.167698] br-2772ec63007d: port 2(vethe668bfd) entered disabled state
[ 2904.168108] veth785c4c4: renamed from eth0
[ 2904.190513] br-2772ec63007d: port 2(vethe668bfd) entered disabled state
[ 2904.192233] device vethe668bfd left promiscuous mode
[ 2904.192238] br-2772ec63007d: port 2(vethe668bfd) entered disabled state
[ 2905.075015] br-2772ec63007d: port 2(vethc9c5a4b) entered blocking state
[ 2905.075020] br-2772ec63007d: port 2(vethc9c5a4b) entered disabled state
[ 2905.075107] device vethc9c5a4b entered promiscuous mode

Thanks in advance!

#3

Hi,

It seems like the issue here is specifying ports in both ports and expose, as the ports you specify in ports will also be exposed (mqtt and redis service). You can try removing duplicate ports in expose and see how it goes.

We already have a fix for this as the supervisor version 9.14.4 and newer removes duplicates automatically. Please let us know if this solves your issue!