vmbr0: port 1 entered blocking state

msd

Active Member
Sep 12, 2015
24
0
41
Hello,

I have 3 servers and all servers go to blocking state at once is it some proxmox global problem od what???

Code:
root@hz2:~# dmesg|grep   block|grep vmbr
[    5.817978] vmbr0: port 1(enp35s0) entered blocking state
[    8.718539] vmbr0: port 1(enp35s0) entered blocking state
[    9.934613] vmbr1: port 1(fwpr101p0) entered blocking state
[    9.934675] vmbr1: port 1(fwpr101p0) entered blocking state
[   14.016401] vmbr1: port 2(fwpr102p0) entered blocking state
[   14.016663] vmbr1: port 2(fwpr102p0) entered blocking state
[   17.942074] vmbr1: port 3(fwpr103p0) entered blocking state
[   17.942137] vmbr1: port 3(fwpr103p0) entered blocking state
[   22.014815] vmbr1: port 4(fwpr104p0) entered blocking state
[   22.014889] vmbr1: port 4(fwpr104p0) entered blocking state
[   26.012301] vmbr1: port 5(fwpr105p0) entered blocking state
[   26.012538] vmbr1: port 5(fwpr105p0) entered blocking state


Thanks for the any help...
 
hi,

could you post the full dmesg output? (you can do dmesg > dmesg.txt and attach it here)

also what kind of NIC are you using? could you post lspci -nnk | grep Eth -C 2 as well?
 
Hello,

this is lspci log

Code:
root@xxx:~# lspci -nnk | grep Eth -C 2
        Kernel driver in use: ahci
        Kernel modules: ahci
09:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
        Subsystem: ASRock Incorporation Motherboard (one of many) [1849:8168]
        Kernel driver in use: r8169

for dmesg.txt, I can't find this file
 
for dmesg.txt, I can't find this file
you need to create it by running the first command i wrote in the above post.
 
I think this error happens to me too. Some of my Debian 10 LXC containers show console login after 1-5 minutes und their aren't reachable via network.
Code:
root@pve01:~# pveversion --verbose
proxmox-ve: 7.1-1 (running kernel: 5.13.19-4-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
pve-kernel-helper: 7.1-9
pve-kernel-5.13: 7.1-7
pve-kernel-5.4: 6.4-11
pve-kernel-5.0: 6.0-11
pve-kernel-5.13.19-4-pve: 5.13.19-8
pve-kernel-5.13.19-3-pve: 5.13.19-7
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.4.157-1-pve: 5.4.157-1
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph: 16.2.7
ceph-fuse: 16.2.7
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-6
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-2
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.0-15
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-1
proxmox-backup-client: 2.1.5-1
proxmox-backup-file-restore: 2.1.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-5
pve-cluster: 7.1-3
pve-container: 4.1-3
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-4
pve-ha-manager: 3.3-3
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.1-1
pve-xtermjs: 4.16.0-1
qemu-server: 7.1-4
smartmontools: 7.2-pve2
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1
 

Attachments

hi guys,

i solved problem change to harddisk.

i was using sata ssd

i changed nvme disk and solved.

i think sata not enough for 10 or 1 gigabit lan

sory for my bad english