[SOLVED] Network Error Spamming Logs

spencerskinner

New Member
Apr 17, 2023
5
2
3
Hi,

I have been getting this error allot in my syslogs, I think it is due to several VPN docker containers I have running on a LXC container, I am unsure on what the issue is or how to solve it.

I have passed TUN/TAP through to the LXC Container like such
Code:
lxc.cgroup.devices.allow: c 10:200 rwm
lxc.mount.entry: /dev/net dev/net none bind,create=dir

This is the syslog output
Code:
Apr 17 22:32:05 pve kernel: br-2026d6b774f4: port 11(veth5b62d59) entered blocking state
Apr 17 22:32:05 pve kernel: br-2026d6b774f4: port 11(veth5b62d59) entered disabled state
Apr 17 22:32:05 pve kernel: device veth5b62d59 entered promiscuous mode
Apr 17 22:32:05 pve kernel: eth0: renamed from veth0258905
Apr 17 22:32:05 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth5b62d59: link becomes ready
Apr 17 22:32:05 pve kernel: br-2026d6b774f4: port 11(veth5b62d59) entered blocking state
Apr 17 22:32:05 pve kernel: br-2026d6b774f4: port 11(veth5b62d59) entered forwarding state
Apr 17 22:32:05 pve kernel: traps: dotnet[77332] general protection fault ip:7ff4eff8f611 sp:7ffce3f875a0 error:0 in libc-2.28.so[7ff4eff8f000+147000]
Apr 17 22:32:05 pve kernel: br-2026d6b774f4: port 11(veth5b62d59) entered disabled state
Apr 17 22:32:05 pve kernel: veth0258905: renamed from eth0
Apr 17 22:32:05 pve kernel: br-2026d6b774f4: port 11(veth5b62d59) entered disabled state
Apr 17 22:32:05 pve kernel: device veth5b62d59 left promiscuous mode
Apr 17 22:32:05 pve kernel: br-2026d6b774f4: port 11(veth5b62d59) entered disabled state

My interface config looks like this
Code:
auto lo
iface lo inet loopback

iface enp35s0 inet manual

iface enp36s0 inet manual

iface enx1a787d0c6cc6 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.2.30/24
        gateway 192.168.2.1
        bridge-ports enp35s0
        bridge-stp off
        bridge-fd 0

auto vmbr1
iface vmbr1 inet static
        address 192.168.3.2/24
        bridge-ports enp36s0
        bridge-stp off
        bridge-fd 0
                                                                                                                                                                                                                                                                           24        35,0-1        All

Any ideas on what could be causing the log spam?

Thanks
Spencer
 
@spencerskinner, could you please elaborate on how did you fix the issue at your end I am having the exact issue and am a bit lost on how to tackle it? Any help would be appreciated in advance.
 
Hi,
So I noticed that the IP of the virtual network interface (veth) was the same as one of my main docker networks inside my LXC container so I shut down all except my critical containers and the error stopped. I then just started groups of containers slowly until error appeared again, then isolated it to a container that had been repeatedly crashing and restarting, I didn't look too much into the container error itself, I just reset the config folder for it and moved on as it allowed the container to start and the error was resolved