I've been running my Unraid system smoothly for a year, but recently I've encountered a strange issue. The webGUI is showing that the log is rapidly growing to almost 100%, and I'm not sure what's causing this. From the logs, I can see that some ports are constantly opening and closing, and it seems to be acquiring an IPv6 address, even though I haven't enabled IPv6 in my network and system settings. What's even stranger is that I restarted the system two days ago, and in just two days, the log has grown to 15%, with the log types remaining the same. I'm hoping to get some help with this issue.

 

Oct  3 09:10:19 MingShun kernel: docker0: port 8(veth6197960) entered blocking state
Oct  3 09:10:19 MingShun kernel: docker0: port 8(veth6197960) entered disabled state
Oct  3 09:10:19 MingShun kernel: device veth6197960 entered promiscuous mode
Oct  3 09:10:19 MingShun kernel: docker0: port 8(veth6197960) entered blocking state
Oct  3 09:10:19 MingShun kernel: docker0: port 8(veth6197960) entered forwarding state
Oct  3 09:10:19 MingShun kernel: eth0: renamed from veth31aafdc
Oct  3 09:10:19 MingShun kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth6197960: link becomes ready
Oct  3 09:10:20 MingShun kernel: docker0: port 9(vetha79dc8e) entered disabled state
Oct  3 09:10:20 MingShun kernel: vethd77f734: renamed from eth0
Oct  3 09:10:20 MingShun avahi-daemon[22691]: Interface vetha79dc8e.IPv6 no longer relevant for mDNS.
Oct  3 09:10:20 MingShun avahi-daemon[22691]: Leaving mDNS multicast group on interface vetha79dc8e.IPv6 with address fe80::a0e5:f2ff:fe83:ec46.
Oct  3 09:10:20 MingShun kernel: docker0: port 9(vetha79dc8e) entered disabled state
Oct  3 09:10:20 MingShun kernel: device vetha79dc8e left promiscuous mode
Oct  3 09:10:20 MingShun kernel: docker0: port 9(vetha79dc8e) entered disabled state
Oct  3 09:10:20 MingShun avahi-daemon[22691]: Withdrawing address record for fe80::a0e5:f2ff:fe83:ec46 on vetha79dc8e.
Oct  3 09:10:20 MingShun kernel: docker0: port 9(veth9dd70b3) entered blocking state
Oct  3 09:10:20 MingShun kernel: docker0: port 9(veth9dd70b3) entered disabled state
Oct  3 09:10:20 MingShun kernel: device veth9dd70b3 entered promiscuous mode
Oct  3 09:10:20 MingShun kernel: docker0: port 9(veth9dd70b3) entered blocking state
Oct  3 09:10:20 MingShun kernel: docker0: port 9(veth9dd70b3) entered forwarding state
Oct  3 09:10:20 MingShun kernel: eth0: renamed from vethec901bb
Oct  3 09:10:20 MingShun kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth9dd70b3: link becomes ready
Oct  3 09:10:21 MingShun avahi-daemon[22691]: Joining mDNS multicast group on interface veth6197960.IPv6 with address fe80::ecfb:f2ff:febd:75a8.
Oct  3 09:10:21 MingShun avahi-daemon[22691]: New relevant interface veth6197960.IPv6 for mDNS.
Oct  3 09:10:21 MingShun avahi-daemon[22691]: Registering new address record for fe80::ecfb:f2ff:febd:75a8 on veth6197960.*.
Oct  3 09:10:22 MingShun avahi-daemon[22691]: Joining mDNS multicast group on interface veth9dd70b3.IPv6 with address fe80::2821:fcff:fe0e:2348.

 

mingshun-syslog-20241003-0113.zip

Looks like you have a container constantly restarting, check their up-times to see if you can find out which one it is.

3 hours ago, JorgeB said:

Looks like you have a container constantly restarting, check their up-times to see if you can find out which one it is.

Thank you so much! Following the Docker start time, I was able to identify the most recent container and stopping it resolved the issue with the logs.