I am not able to keep my containers running after a host reboot. Some of them continually restart in a loop and others not starting at all.
Noticed some NIC errors in dmesg, can anyone help with this?
[ 1295.670459] br0: port 4(vethEVVR6K) entered forwarding state
[ 1295.718268] eth0: renamed from vethNQ6MTU [ 1295.733469] IPv6: ADDRCONF(NETDEV_CHANGE): vethEVVR6K: link becomes ready [ 1296.046930] device veth57DW12 entered promiscuous mode [ 1296.047071] IPv6: ADDRCONF(NETDEV_UP): veth57DW12: link is not ready [ 1296.094273] eth0: renamed from veth4BX5HQ [ 1296.117386] IPv6: ADDRCONF(NETDEV_CHANGE): veth57DW12: link becomes ready [ 1296.117404] br0: port 5(veth57DW12) entered forwarding state [ 1296.117411] br0: port 5(veth57DW12) entered forwarding state [ 1296.495810] device veth3REOCE entered promiscuous mode [ 1296.496069] IPv6: ADDRCONF(NETDEV_UP): veth3REOCE: link is not ready
[ 1296.496074] br0: port 6(veth3REOCE) entered forwarding state [ 1296.496080] br0: port 6(veth3REOCE) entered forwarding state [ 1296.542761] eth0: renamed from veth45A4WV [ 1296.573497] IPv6: ADDRCONF(NETDEV_CHANGE): veth3REOCE: link becomes ready
[ 1297.000227] device vethIF5K7H entered promiscuous mode [ 1297.002169] IPv6: ADDRCONF(NETDEV_UP): vethIF5K7H: link is not ready
[ 1297.002176] br0: port 7(vethIF5K7H) entered forwarding state
[ 1297.002182] br0: port 7(vethIF5K7H) entered forwarding state [ 1297.041026] eth0: renamed from vethQI4380 [ 1297.065203] br0: port 7(vethIF5K7H) entered disabled state
[ 1297.065627] IPv6: ADDRCONF(NETDEV_CHANGE): vethIF5K7H: link becomes ready [ 1297.065644] br0: port 7(vethIF5K7H) entered forwarding state [ 1297.065651] br0: port 7(vethIF5K7H) entered forwarding state [ 1297.663844] br0: port 4(vethEVVR6K) entered disabled state [ 1297.731281] br0: port 3(vethX248GJ) entered disabled state
[ 1297.731405] device vethX248GJ left promiscuous mode [ 1297.731415] br0: port 3(vethX248GJ) entered disabled state [ 1297.920010] br0: port 5(veth57DW12) entered disabled state
[ 1297.920108] device veth57DW12 left promiscuous mode [ 1297.920109] br0: port 5(veth57DW12) entered disabled state [ 1297.954137] br0: port 4(vethEVVR6K) entered disabled state [ 1297.954209] device vethEVVR6K left promiscuous mode [ 1297.954211] br0: port 4(vethEVVR6K) entered disabled state [ 1298.177976] br0: port 2(vethL9NJ65) entered disabled state [ 1298.214505] br0: port 7(vethIF5K7H) entered disabled state [ 1298.214593] device vethIF5K7H left promiscuous mode [ 1298.214596] br0: port 7(vethIF5K7H) entered disabled state [ 1298.254746] br0: port 2(vethL9NJ65) entered disabled state [ 1298.254921] device vethL9NJ65 left promiscuous mode [ 1298.254923] br0: port 2(vethL9NJ65) entered disabled state [ 1311.507619] br0: port 6(veth3REOCE) entered forwarding state [ 1327.287729] br0: port 6(veth3REOCE) entered disabled state
[ 1327.288066] device veth3REOCE left promiscuous mode [ 1327.288075] br0: port 6(veth3REOCE) entered disabled state
Failed to open file '/sys/class/net/vethDQDA6O/operstate': No such file or directory
lxd.daemon[30139]: lvl=warn msg="Unable to update backup.yaml at this time." name=mumble
Thanks for your reply. Funnily enough I done a reboot there and all went well, all containers auto started.
I wonder if it was the lxd bridge issue you mentioned, as since I disabled this at /etc/default/ it seems to be resolved.
Here’s output of lxd.log for this reboot (I manually restarted the transmission container due to unrelated network issue):