Mysterious syslog entries

proxwolfe

Member
Jun 20, 2020
252
12
23
47
Hi,

I just noticed the following in my syslog

Code:
Oct 07 19:43:48 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethb7f577f: link becomes ready
Oct 07 19:43:48 pve kernel: br-857733caeccb: port 3(vethb7f577f) entered blocking state
Oct 07 19:43:48 pve kernel: br-857733caeccb: port 3(vethb7f577f) entered forwarding state
Oct 07 19:44:00 pve systemd[1]: Starting Proxmox VE replication runner...
Oct 07 19:44:01 pve kernel: br-857733caeccb: port 3(vethb7f577f) entered disabled state
Oct 07 19:44:01 pve kernel: veth8418d2a: renamed from eth0
Oct 07 19:44:02 pve kernel: br-857733caeccb: port 3(vethb7f577f) entered disabled state
Oct 07 19:44:02 pve kernel: device vethb7f577f left promiscuous mode
Oct 07 19:44:02 pve kernel: br-857733caeccb: port 3(vethb7f577f) entered disabled state
Oct 07 19:44:02 pve kernel: br-857733caeccb: port 3(vetha5d0ae9) entered blocking state
Oct 07 19:44:02 pve kernel: br-857733caeccb: port 3(vetha5d0ae9) entered disabled state
Oct 07 19:44:02 pve kernel: device vetha5d0ae9 entered promiscuous mode
Oct 07 19:44:02 pve kernel: br-857733caeccb: port 3(vetha5d0ae9) entered blocking state
Oct 07 19:44:02 pve kernel: br-857733caeccb: port 3(vetha5d0ae9) entered forwarding state
Oct 07 19:44:02 pve systemd[1]: pvesr.service: Succeeded.
Oct 07 19:44:02 pve systemd[1]: Finished Proxmox VE replication runner.
Oct 07 19:44:02 pve systemd[1]: pvesr.service: Consumed 2.174s CPU time.
Oct 07 19:44:02 pve kernel: br-857733caeccb: port 3(vetha5d0ae9) entered disabled state
Oct 07 19:44:03 pve kernel: eth0: renamed from veth8ad57b5
Oct 07 19:44:03 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vetha5d0ae9: link becomes ready
Oct 07 19:44:03 pve kernel: br-857733caeccb: port 3(vetha5d0ae9) entered blocking state
Oct 07 19:44:03 pve kernel: br-857733caeccb: port 3(vetha5d0ae9) entered forwarding state
Oct 07 19:44:16 pve kernel: br-857733caeccb: port 3(vetha5d0ae9) entered disabled state
Oct 07 19:44:16 pve kernel: veth8ad57b5: renamed from eth0
Oct 07 19:44:16 pve kernel: br-857733caeccb: port 3(vetha5d0ae9) entered disabled state
Oct 07 19:44:17 pve kernel: device vetha5d0ae9 left promiscuous mode
Oct 07 19:44:17 pve kernel: br-857733caeccb: port 3(vetha5d0ae9) entered disabled state
Oct 07 19:44:17 pve kernel: br-857733caeccb: port 3(vethf506002) entered blocking state
Oct 07 19:44:17 pve kernel: br-857733caeccb: port 3(vethf506002) entered disabled state
Oct 07 19:44:17 pve kernel: device vethf506002 entered promiscuous mode
Oct 07 19:44:17 pve kernel: br-857733caeccb: port 3(vethf506002) entered blocking state
Oct 07 19:44:17 pve kernel: br-857733caeccb: port 3(vethf506002) entered forwarding state
Oct 07 19:44:17 pve kernel: br-857733caeccb: port 3(vethf506002) entered disabled state
Oct 07 19:44:18 pve kernel: eth0: renamed from veth425cedf
Oct 07 19:44:18 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethf506002: link becomes ready
Oct 07 19:44:18 pve kernel: br-857733caeccb: port 3(vethf506002) entered blocking state
Oct 07 19:44:18 pve kernel: br-857733caeccb: port 3(vethf506002) entered forwarding state
Oct 07 19:44:31 pve kernel: br-857733caeccb: port 3(vethf506002) entered disabled state
Oct 07 19:44:31 pve kernel: veth425cedf: renamed from eth0
Oct 07 19:44:31 pve kernel: br-857733caeccb: port 3(vethf506002) entered disabled state
Oct 07 19:44:31 pve kernel: device vethf506002 left promiscuous mode
Oct 07 19:44:31 pve kernel: br-857733caeccb: port 3(vethf506002) entered disabled state
Oct 07 19:44:32 pve kernel: br-857733caeccb: port 3(veth96fac44) entered blocking state
Oct 07 19:44:32 pve kernel: br-857733caeccb: port 3(veth96fac44) entered disabled state
Oct 07 19:44:32 pve kernel: device veth96fac44 entered promiscuous mode
Oct 07 19:44:32 pve kernel: br-857733caeccb: port 3(veth96fac44) entered blocking state
Oct 07 19:44:32 pve kernel: br-857733caeccb: port 3(veth96fac44) entered forwarding state
Oct 07 19:44:32 pve kernel: br-857733caeccb: port 3(veth96fac44) entered disabled state
Oct 07 19:44:33 pve kernel: eth0: renamed from veth4a79e29
Oct 07 19:44:33 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth96fac44: link becomes ready
Oct 07 19:44:33 pve kernel: br-857733caeccb: port 3(veth96fac44) entered blocking state
Oct 07 19:44:33 pve kernel: br-857733caeccb: port 3(veth96fac44) entered forwarding state
Oct 07 19:44:46 pve kernel: br-857733caeccb: port 3(veth96fac44) entered disabled state
Oct 07 19:44:46 pve kernel: veth4a79e29: renamed from eth0
Oct 07 19:44:46 pve kernel: br-857733caeccb: port 3(veth96fac44) entered disabled state
Oct 07 19:44:46 pve kernel: device veth96fac44 left promiscuous mode
Oct 07 19:44:46 pve kernel: br-857733caeccb: port 3(veth96fac44) entered disabled state
Oct 07 19:44:46 pve kernel: br-857733caeccb: port 3(veth80e279e) entered blocking state
Oct 07 19:44:46 pve kernel: br-857733caeccb: port 3(veth80e279e) entered disabled state
Oct 07 19:44:46 pve kernel: device veth80e279e entered promiscuous mode
Oct 07 19:44:46 pve kernel: br-857733caeccb: port 3(veth80e279e) entered blocking state
Oct 07 19:44:46 pve kernel: br-857733caeccb: port 3(veth80e279e) entered forwarding state
Oct 07 19:44:47 pve kernel: br-857733caeccb: port 3(veth80e279e) entered disabled state
Oct 07 19:44:47 pve kernel: eth0: renamed from veth0824b7f
Oct 07 19:44:47 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth80e279e: link becomes ready
Oct 07 19:44:47 pve kernel: br-857733caeccb: port 3(veth80e279e) entered blocking state
Oct 07 19:44:47 pve kernel: br-857733caeccb: port 3(veth80e279e) entered forwarding state
Oct 07 19:45:00 pve systemd[1]: Starting Proxmox VE replication runner...
Oct 07 19:45:00 pve kernel: br-857733caeccb: port 3(veth80e279e) entered disabled state
Oct 07 19:45:00 pve kernel: veth0824b7f: renamed from eth0
Oct 07 19:45:01 pve kernel: br-857733caeccb: port 3(veth80e279e) entered disabled state
Oct 07 19:45:01 pve kernel: device veth80e279e left promiscuous mode
Oct 07 19:45:01 pve kernel: br-857733caeccb: port 3(veth80e279e) entered disabled state
Oct 07 19:45:01 pve kernel: br-857733caeccb: port 3(veth2b87220) entered blocking state
Oct 07 19:45:01 pve kernel: br-857733caeccb: port 3(veth2b87220) entered disabled state
Oct 07 19:45:01 pve kernel: device veth2b87220 entered promiscuous mode
Oct 07 19:45:01 pve kernel: br-857733caeccb: port 3(veth2b87220) entered blocking state
Oct 07 19:45:01 pve kernel: br-857733caeccb: port 3(veth2b87220) entered forwarding state
Oct 07 19:45:02 pve kernel: br-857733caeccb: port 3(veth2b87220) entered disabled state
Oct 07 19:45:02 pve kernel: eth0: renamed from veth962e2fb
Oct 07 19:45:02 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth2b87220: link becomes ready
Oct 07 19:45:02 pve kernel: br-857733caeccb: port 3(veth2b87220) entered blocking state
Oct 07 19:45:02 pve kernel: br-857733caeccb: port 3(veth2b87220) entered forwarding state
Oct 07 19:45:02 pve systemd[1]: pvesr.service: Succeeded.
Oct 07 19:45:02 pve systemd[1]: Finished Proxmox VE replication runner.
Oct 07 19:45:02 pve systemd[1]: pvesr.service: Consumed 2.608s CPU time.
Oct 07 19:45:16 pve kernel: br-857733caeccb: port 3(veth2b87220) entered disabled state
Oct 07 19:45:16 pve kernel: veth962e2fb: renamed from eth0
Oct 07 19:45:16 pve kernel: br-857733caeccb: port 3(veth2b87220) entered disabled state
Oct 07 19:45:16 pve kernel: device veth2b87220 left promiscuous mode
Oct 07 19:45:16 pve kernel: br-857733caeccb: port 3(veth2b87220) entered disabled state
Oct 07 19:45:16 pve kernel: br-857733caeccb: port 3(vethff917c5) entered blocking state
Oct 07 19:45:16 pve kernel: br-857733caeccb: port 3(vethff917c5) entered disabled state
Oct 07 19:45:16 pve kernel: device vethff917c5 entered promiscuous mode
Oct 07 19:45:16 pve kernel: br-857733caeccb: port 3(vethff917c5) entered blocking state
Oct 07 19:45:16 pve kernel: br-857733caeccb: port 3(vethff917c5) entered forwarding state
Oct 07 19:45:17 pve kernel: br-857733caeccb: port 3(vethff917c5) entered disabled state
Oct 07 19:45:17 pve kernel: eth0: renamed from veth0042311
Oct 07 19:45:17 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethff917c5: link becomes ready
Oct 07 19:45:17 pve kernel: br-857733caeccb: port 3(vethff917c5) entered blocking state
Oct 07 19:45:17 pve kernel: br-857733caeccb: port 3(vethff917c5) entered forwarding state
Oct 07 19:45:31 pve kernel: br-857733caeccb: port 3(vethff917c5) entered disabled state
Oct 07 19:45:31 pve kernel: veth0042311: renamed from eth0
Oct 07 19:45:31 pve kernel: br-857733caeccb: port 3(vethff917c5) entered disabled state
Oct 07 19:45:31 pve kernel: device vethff917c5 left promiscuous mode
Oct 07 19:45:31 pve kernel: br-857733caeccb: port 3(vethff917c5) entered disabled state
Oct 07 19:45:31 pve kernel: br-857733caeccb: port 3(vethc826c14) entered blocking state
Oct 07 19:45:31 pve kernel: br-857733caeccb: port 3(vethc826c14) entered disabled state
Oct 07 19:45:31 pve kernel: device vethc826c14 entered promiscuous mode
Oct 07 19:45:31 pve kernel: br-857733caeccb: port 3(vethc826c14) entered blocking state
Oct 07 19:45:31 pve kernel: br-857733caeccb: port 3(vethc826c14) entered forwarding state
Oct 07 19:45:32 pve kernel: br-857733caeccb: port 3(vethc826c14) entered disabled state
Oct 07 19:45:32 pve kernel: eth0: renamed from veth48e0e1f
Oct 07 19:45:32 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethc826c14: link becomes ready
Oct 07 19:45:32 pve kernel: br-857733caeccb: port 3(vethc826c14) entered blocking state
Oct 07 19:45:32 pve kernel: br-857733caeccb: port 3(vethc826c14) entered forwarding state
Oct 07 19:45:45 pve kernel: br-857733caeccb: port 3(vethc826c14) entered disabled state
Oct 07 19:45:45 pve kernel: veth48e0e1f: renamed from eth0
Oct 07 19:45:45 pve kernel: br-857733caeccb: port 3(vethc826c14) entered disabled state
Oct 07 19:45:45 pve kernel: device vethc826c14 left promiscuous mode
Oct 07 19:45:45 pve kernel: br-857733caeccb: port 3(vethc826c14) entered disabled state
Oct 07 19:45:45 pve kernel: br-857733caeccb: port 3(veth2f0a7c6) entered blocking state
Oct 07 19:45:45 pve kernel: br-857733caeccb: port 3(veth2f0a7c6) entered disabled state
Oct 07 19:45:45 pve kernel: device veth2f0a7c6 entered promiscuous mode
Oct 07 19:45:45 pve kernel: br-857733caeccb: port 3(veth2f0a7c6) entered blocking state
Oct 07 19:45:45 pve kernel: br-857733caeccb: port 3(veth2f0a7c6) entered forwarding state
Oct 07 19:45:46 pve kernel: br-857733caeccb: port 3(veth2f0a7c6) entered disabled state
Oct 07 19:45:47 pve kernel: eth0: renamed from vethf4963ee
Oct 07 19:45:47 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth2f0a7c6: link becomes ready
Oct 07 19:45:47 pve kernel: br-857733caeccb: port 3(veth2f0a7c6) entered blocking state
Oct 07 19:45:47 pve kernel: br-857733caeccb: port 3(veth2f0a7c6) entered forwarding state
Oct 07 19:46:00 pve systemd[1]: Starting Proxmox VE replication runner...
Oct 07 19:46:00 pve kernel: br-857733caeccb: port 3(veth2f0a7c6) entered disabled state
Oct 07 19:46:00 pve kernel: vethf4963ee: renamed from eth0
Oct 07 19:46:00 pve kernel: br-857733caeccb: port 3(veth2f0a7c6) entered disabled state
Oct 07 19:46:00 pve kernel: device veth2f0a7c6 left promiscuous mode
Oct 07 19:46:00 pve kernel: br-857733caeccb: port 3(veth2f0a7c6) entered disabled state
Oct 07 19:46:00 pve kernel: br-857733caeccb: port 3(veth2dbf11b) entered blocking state
Oct 07 19:46:00 pve kernel: br-857733caeccb: port 3(veth2dbf11b) entered disabled state
Oct 07 19:46:00 pve kernel: device veth2dbf11b entered promiscuous mode
Oct 07 19:46:00 pve kernel: br-857733caeccb: port 3(veth2dbf11b) entered blocking state
Oct 07 19:46:00 pve kernel: br-857733caeccb: port 3(veth2dbf11b) entered forwarding state
Oct 07 19:46:01 pve kernel: br-857733caeccb: port 3(veth2dbf11b) entered disabled state
Oct 07 19:46:01 pve kernel: eth0: renamed from vethe18b99a
Oct 07 19:46:01 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth2dbf11b: link becomes ready
Oct 07 19:46:01 pve kernel: br-857733caeccb: port 3(veth2dbf11b) entered blocking state
Oct 07 19:46:01 pve kernel: br-857733caeccb: port 3(veth2dbf11b) entered forwarding state
Oct 07 19:46:02 pve systemd[1]: pvesr.service: Succeeded.
Oct 07 19:46:02 pve systemd[1]: Finished Proxmox VE replication runner.
Oct 07 19:46:02 pve systemd[1]: pvesr.service: Consumed 2.188s CPU time.
Oct 07 19:46:14 pve kernel: br-857733caeccb: port 3(veth2dbf11b) entered disabled state
Oct 07 19:46:14 pve kernel: vethe18b99a: renamed from eth0
Oct 07 19:46:14 pve kernel: br-857733caeccb: port 3(veth2dbf11b) entered disabled state
Oct 07 19:46:15 pve kernel: device veth2dbf11b left promiscuous mode
Oct 07 19:46:15 pve kernel: br-857733caeccb: port 3(veth2dbf11b) entered disabled state
Oct 07 19:46:15 pve kernel: br-857733caeccb: port 3(veth51b554c) entered blocking state
Oct 07 19:46:15 pve kernel: br-857733caeccb: port 3(veth51b554c) entered disabled state
Oct 07 19:46:15 pve kernel: device veth51b554c entered promiscuous mode
Oct 07 19:46:15 pve kernel: br-857733caeccb: port 3(veth51b554c) entered blocking state
Oct 07 19:46:15 pve kernel: br-857733caeccb: port 3(veth51b554c) entered forwarding state
Oct 07 19:46:15 pve kernel: br-857733caeccb: port 3(veth51b554c) entered disabled state
Oct 07 19:46:16 pve kernel: eth0: renamed from vethbf8093e
Oct 07 19:46:16 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth51b554c: link becomes ready
Oct 07 19:46:16 pve kernel: br-857733caeccb: port 3(veth51b554c) entered blocking state
Oct 07 19:46:16 pve kernel: br-857733caeccb: port 3(veth51b554c) entered forwarding state
Oct 07 19:46:29 pve kernel: br-857733caeccb: port 3(veth51b554c) entered disabled state
Oct 07 19:46:29 pve kernel: vethbf8093e: renamed from eth0
Oct 07 19:46:29 pve kernel: br-857733caeccb: port 3(veth51b554c) entered disabled state
Oct 07 19:46:29 pve kernel: device veth51b554c left promiscuous mode
Oct 07 19:46:29 pve kernel: br-857733caeccb: port 3(veth51b554c) entered disabled state
Oct 07 19:46:29 pve kernel: br-857733caeccb: port 3(veth53d12f3) entered blocking state
Oct 07 19:46:29 pve kernel: br-857733caeccb: port 3(veth53d12f3) entered disabled state
Oct 07 19:46:29 pve kernel: device veth53d12f3 entered promiscuous mode
Oct 07 19:46:29 pve kernel: br-857733caeccb: port 3(veth53d12f3) entered blocking state
Oct 07 19:46:29 pve kernel: br-857733caeccb: port 3(veth53d12f3) entered forwarding state
Oct 07 19:46:30 pve kernel: br-857733caeccb: port 3(veth53d12f3) entered disabled state
Oct 07 19:46:30 pve kernel: eth0: renamed from vethb013071
Oct 07 19:46:30 pve kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth53d12f3: link becomes ready
Oct 07 19:46:30 pve kernel: br-857733caeccb: port 3(veth53d12f3) entered blocking state
Oct 07 19:46:30 pve kernel: br-857733caeccb: port 3(veth53d12f3) entered forwarding state
Logs

This goes on and on and one.

Doesn't look right - but I have no clue what it means or what I should do about it...

Any help appreciated.

Thanks!
 

Hannes Laimer

Proxmox Staff Member
Staff member
Jul 27, 2020
442
59
33
23
Hey,

this bridge name is not generated by PVE br-857733caeccb, is it possible that you have Docker or something similar running? Services like that seem to generate similar names [1]. Unfortunately, I am not sure what the reason for those messages could be, [2] describes a possible reason and solution, but it could also be something else that causes those logs.

[1] https://www.reddit.com/r/Ubuntu/comments/8zcr0k/help_with_multiple_unknown_br_and_veth_interfaces/
[2] https://github.com/moby/moby/issues/15172#issuecomment-178591819
 

proxwolfe

Member
Jun 20, 2020
252
12
23
47
I don't have anything running on the PVE host directly.

However, there are a couple of containers and VMs that each contain a docker installation. I am assuming that the VMs isolate the docker installations from the PVE host but maybe the LXC dockers can be noticed?

If this is the case, what would be the best way to investigate?

Does this seem to be a problem at all or is it just flooding my syslog with no further consequences?

Thanks!
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!