Weird logs looking for smart gurus to explain

[ritty]

I was in my system logs (which I never check) and noticed some weird logs as shown below. Can anybody explain what these mean and if i should be modifying something in my configuration? I appreciate your help in advance as I am not smart but I do love Unraid. Thank you.

 

Dec 31 08:20:39 JamFlix kernel: eth0: renamed from vethed5eb14
Dec 31 08:20:39 JamFlix kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth583b29d: link becomes ready
Dec 31 08:20:39 JamFlix kernel: br-e494ce73ff26: port 29(veth583b29d) entered blocking state
Dec 31 08:20:39 JamFlix kernel: br-e494ce73ff26: port 29(veth583b29d) entered forwarding state
Dec 31 08:30:01 JamFlix kernel: br-e494ce73ff26: port 30(veth9cdb3e1) entered blocking state
Dec 31 08:30:01 JamFlix kernel: br-e494ce73ff26: port 30(veth9cdb3e1) entered disabled state
Dec 31 08:30:01 JamFlix kernel: device veth9cdb3e1 entered promiscuous mode
Dec 31 08:30:03 JamFlix kernel: eth0: renamed from veth24f5098
Dec 31 08:30:03 JamFlix kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth9cdb3e1: link becomes ready
Dec 31 08:30:03 JamFlix kernel: br-e494ce73ff26: port 30(veth9cdb3e1) entered blocking state
Dec 31 08:30:03 JamFlix kernel: br-e494ce73ff26: port 30(veth9cdb3e1) entered forwarding state
Dec 31 08:30:04 JamFlix kernel: veth24f5098: renamed from eth0
Dec 31 08:30:04 JamFlix kernel: br-e494ce73ff26: port 30(veth9cdb3e1) entered disabled state
Dec 31 08:30:04 JamFlix kernel: br-e494ce73ff26: port 30(veth9cdb3e1) entered disabled state
Dec 31 08:30:04 JamFlix kernel: device veth9cdb3e1 left promiscuous mode
Dec 31 08:30:04 JamFlix kernel: br-e494ce73ff26: port 30(veth9cdb3e1) entered disabled state
Dec 31 08:42:20 JamFlix kernel: br-e494ce73ff26: port 19(vethf3c35f7) entered disabled state
Dec 31 08:42:20 JamFlix kernel: vethaf8c910: renamed from eth0
Dec 31 08:42:20 JamFlix kernel: br-e494ce73ff26: port 19(vethf3c35f7) entered disabled state
Dec 31 08:42:20 JamFlix kernel: device vethf3c35f7 left promiscuous mode
Dec 31 08:42:20 JamFlix kernel: br-e494ce73ff26: port 19(vethf3c35f7) entered disabled state
Dec 31 08:42:25 JamFlix kernel: br-e494ce73ff26: port 19(vethe0efc8f) entered blocking state
Dec 31 08:42:25 JamFlix kernel: br-e494ce73ff26: port 19(vethe0efc8f) entered disabled state
Dec 31 08:42:25 JamFlix kernel: device vethe0efc8f entered promiscuous mode
Dec 31 08:42:25 JamFlix kernel: br-e494ce73ff26: port 19(vethe0efc8f) entered blocking state
Dec 31 08:42:25 JamFlix kernel: br-e494ce73ff26: port 19(vethe0efc8f) entered forwarding state
Dec 31 08:42:25 JamFlix kernel: br-e494ce73ff26: port 19(vethe0efc8f) entered disabled state
Dec 31 08:42:25 JamFlix kernel: eth0: renamed from vethe9ade76
Dec 31 08:42:25 JamFlix kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethe0efc8f: link becomes ready
Dec 31 08:42:25 JamFlix kernel: br-e494ce73ff26: port 19(vethe0efc8f) entered blocking state
Dec 31 08:42:25 JamFlix kernel: br-e494ce73ff26: port 19(vethe0efc8f) entered forwarding state

 

[JorgeB]

That looks normal, but if it keeps repeating check to see if one or more containers are constantly re-starting, you can check based on their uptime.

[ritty]

Thanks @JorgeB, appreciate the response. Will keep an eye on docker but everything seems okay so far. Appreciate it!