strange dmesg messages

DocMAX

Member
Jan 30, 2023
201
14
18
Bremen
any idea where and why i get these messages?:
Code:
[So Mai 26 20:00:28 2024] br-b7fcf6dccca5: port 2(veth0c961c6) entered disabled state
[So Mai 26 20:01:27 2024] br-b7fcf6dccca5: port 2(veth224fca8) entered blocking state
[So Mai 26 20:01:27 2024] br-b7fcf6dccca5: port 2(veth224fca8) entered disabled state
[So Mai 26 20:01:27 2024] veth224fca8: entered allmulticast mode
[So Mai 26 20:01:27 2024] veth224fca8: entered promiscuous mode
[So Mai 26 20:01:32 2024] eth0: renamed from vethc820ee3
[So Mai 26 20:01:32 2024] br-b7fcf6dccca5: port 2(veth224fca8) entered blocking state
[So Mai 26 20:01:32 2024] br-b7fcf6dccca5: port 2(veth224fca8) entered forwarding state
[So Mai 26 20:01:33 2024] vethc820ee3: renamed from eth0
[So Mai 26 20:01:33 2024] br-b7fcf6dccca5: port 2(veth224fca8) entered disabled state
[So Mai 26 20:01:33 2024] br-b7fcf6dccca5: port 2(veth224fca8) entered disabled state
[So Mai 26 20:01:33 2024] veth224fca8 (unregistering): left allmulticast mode
[So Mai 26 20:01:33 2024] veth224fca8 (unregistering): left promiscuous mode
[So Mai 26 20:01:33 2024] br-b7fcf6dccca5: port 2(veth224fca8) entered disabled state
[So Mai 26 20:02:33 2024] br-b7fcf6dccca5: port 2(veth50197e5) entered blocking state
[So Mai 26 20:02:33 2024] br-b7fcf6dccca5: port 2(veth50197e5) entered disabled state
[So Mai 26 20:02:33 2024] veth50197e5: entered allmulticast mode
[So Mai 26 20:02:33 2024] veth50197e5: entered promiscuous mode
[So Mai 26 20:02:36 2024] eth0: renamed from veth687649d
[So Mai 26 20:02:36 2024] br-b7fcf6dccca5: port 2(veth50197e5) entered blocking state
[So Mai 26 20:02:36 2024] br-b7fcf6dccca5: port 2(veth50197e5) entered forwarding state
[So Mai 26 20:02:37 2024] br-b7fcf6dccca5: port 2(veth50197e5) entered disabled state
[So Mai 26 20:02:37 2024] veth687649d: renamed from eth0
[So Mai 26 20:02:38 2024] br-b7fcf6dccca5: port 2(veth50197e5) entered disabled state
[So Mai 26 20:02:38 2024] veth50197e5 (unregistering): left allmulticast mode
[So Mai 26 20:02:38 2024] veth50197e5 (unregistering): left promiscuous mode
[So Mai 26 20:02:38 2024] br-b7fcf6dccca5: port 2(veth50197e5) entered disabled state
[So Mai 26 20:03:37 2024] br-b7fcf6dccca5: port 2(veth124a5bb) entered blocking state
[So Mai 26 20:03:37 2024] br-b7fcf6dccca5: port 2(veth124a5bb) entered disabled state
[So Mai 26 20:03:37 2024] veth124a5bb: entered allmulticast mode
[So Mai 26 20:03:37 2024] veth124a5bb: entered promiscuous mode
[So Mai 26 20:03:41 2024] eth0: renamed from vethd295c27
[So Mai 26 20:03:41 2024] br-b7fcf6dccca5: port 2(veth124a5bb) entered blocking state
[So Mai 26 20:03:41 2024] br-b7fcf6dccca5: port 2(veth124a5bb) entered forwarding state
[So Mai 26 20:03:42 2024] vethd295c27: renamed from eth0
[So Mai 26 20:03:42 2024] br-b7fcf6dccca5: port 2(veth124a5bb) entered disabled state
[So Mai 26 20:03:43 2024] br-b7fcf6dccca5: port 2(veth124a5bb) entered disabled state
[So Mai 26 20:03:43 2024] veth124a5bb (unregistering): left allmulticast mode
[So Mai 26 20:03:43 2024] veth124a5bb (unregistering): left promiscuous mode
[So Mai 26 20:03:43 2024] br-b7fcf6dccca5: port 2(veth124a5bb) entered disabled state
[So Mai 26 20:04:42 2024] br-b7fcf6dccca5: port 2(veth41d6a79) entered blocking state
[So Mai 26 20:04:42 2024] br-b7fcf6dccca5: port 2(veth41d6a79) entered disabled state
[So Mai 26 20:04:42 2024] veth41d6a79: entered allmulticast mode
[So Mai 26 20:04:42 2024] veth41d6a79: entered promiscuous mode
[So Mai 26 20:04:44 2024] eth0: renamed from veth6038bd8
[So Mai 26 20:04:44 2024] br-b7fcf6dccca5: port 2(veth41d6a79) entered blocking state
[So Mai 26 20:04:44 2024] br-b7fcf6dccca5: port 2(veth41d6a79) entered forwarding state
[So Mai 26 20:04:45 2024] veth6038bd8: renamed from eth0
[So Mai 26 20:04:45 2024] br-b7fcf6dccca5: port 2(veth41d6a79) entered disabled state
[So Mai 26 20:04:46 2024] br-b7fcf6dccca5: port 2(veth41d6a79) entered disabled state
[So Mai 26 20:04:46 2024] veth41d6a79 (unregistering): left allmulticast mode
[So Mai 26 20:04:46 2024] veth41d6a79 (unregistering): left promiscuous mode
[So Mai 26 20:04:46 2024] br-b7fcf6dccca5: port 2(veth41d6a79) entered disabled state
[So Mai 26 20:05:45 2024] br-b7fcf6dccca5: port 2(veth7d5d45d) entered blocking state
[So Mai 26 20:05:45 2024] br-b7fcf6dccca5: port 2(veth7d5d45d) entered disabled state
[So Mai 26 20:05:45 2024] veth7d5d45d: entered allmulticast mode
[So Mai 26 20:05:45 2024] veth7d5d45d: entered promiscuous mode
[So Mai 26 20:05:48 2024] eth0: renamed from vethd4bddb1
[So Mai 26 20:05:48 2024] br-b7fcf6dccca5: port 2(veth7d5d45d) entered blocking state
[So Mai 26 20:05:48 2024] br-b7fcf6dccca5: port 2(veth7d5d45d) entered forwarding state
[So Mai 26 20:05:50 2024] vethd4bddb1: renamed from eth0
[So Mai 26 20:05:50 2024] br-b7fcf6dccca5: port 2(veth7d5d45d) entered disabled state
[So Mai 26 20:05:50 2024] br-b7fcf6dccca5: port 2(veth7d5d45d) entered disabled state
[So Mai 26 20:05:50 2024] veth7d5d45d (unregistering): left allmulticast mode
[So Mai 26 20:05:50 2024] veth7d5d45d (unregistering): left promiscuous mode
[So Mai 26 20:05:50 2024] br-b7fcf6dccca5: port 2(veth7d5d45d) entered disabled state
[So Mai 26 20:06:49 2024] br-b7fcf6dccca5: port 2(veth2e4c026) entered blocking state
[So Mai 26 20:06:49 2024] br-b7fcf6dccca5: port 2(veth2e4c026) entered disabled state
[So Mai 26 20:06:49 2024] veth2e4c026: entered allmulticast mode
[So Mai 26 20:06:49 2024] veth2e4c026: entered promiscuous mode
[So Mai 26 20:06:51 2024] eth0: renamed from vethf1e713f
[So Mai 26 20:06:51 2024] br-b7fcf6dccca5: port 2(veth2e4c026) entered blocking state
 
OK, the strange thing is, i haven't started or stopped a VM/CT in that timeperiod.
Technically VMs are started automatically for a moment when a (usually scheduled) backup in Snapshot-Mode is initiating. (The Qemu-process starts, but not the actual Guest-Operating-System, so don't worry...)

Best regards
 

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 yours easily in our online shop.

Buy now!