[SOLVED] kernel: vmbr0: port 4(tap107i0) entering disabled state

offerlam

Member
Dec 30, 2012
198
0
16
Denmark
Hi all..

There is also another post here referring to what could like my issue.. but i didn't want ti potentially hijack the OP thread so i made a new one and figured i would link his thread here:

http://forum.proxmox.com/threads/17598-vmbr0-port-10(tap109i0)-entering-disabled-state

I have this entry about every hour along with some other information i don't know is relevant..

about 6:50
Code:
Jan 21 06:49:55 proxmox01 kernel: vmbr0: port 4(tap107i0) entering disabled stateJan 21 06:49:55 proxmox01 kernel: vmbr0: port 4(tap107i0) entering disabled state
Jan 21 06:49:57 proxmox01 ntpd[2378]: Deleting interface #19 tap107i0, fe80::ac93:a5ff:fe8c:8337#123, interface stats: received=0, sent=0, dropped=0, active_time=3622 secs
Jan 21 06:49:57 proxmox01 ntpd[2378]: peers refreshed
Jan 21 06:50:01 proxmox01 rgmanager[165883]: [pvevm] VM 104 is running
Jan 21 06:50:01 proxmox01 rgmanager[165903]: [pvevm] VM 112 is running
Jan 21 06:50:11 proxmox01 rgmanager[165943]: [pvevm] VM 112 is running
Jan 21 06:50:21 proxmox01 rgmanager[165977]: [pvevm] VM 107 is not running
Jan 21 06:50:21 proxmox01 rgmanager[2937]: status on pvevm "107" returned 7 (unspecified)
Jan 21 06:50:22 proxmox01 rgmanager[2937]: Stopping service pvevm:107
Jan 21 06:50:23 proxmox01 rgmanager[165998]: [pvevm] VM 107 is already stopped
Jan 21 06:50:23 proxmox01 rgmanager[2937]: Service pvevm:107 is recovering
Jan 21 06:50:24 proxmox01 rgmanager[2937]: Recovering failed service pvevm:107
Jan 21 06:50:24 proxmox01 task UPID:proxmox01:00028884:003D5134:52DE0AA0:qmstart:107:root@pam:: start VM 107: UPID:proxmox01:00028884:003D5134:52DE0AA0:qmstart:107:root@pam:
Jan 21 06:50:24 proxmox01 pvevm: <root@pam> starting task UPID:proxmox01:00028884:003D5134:52DE0AA0:qmstart:107:root@pam:
Jan 21 06:50:25 proxmox01 kernel: device tap107i0 entered promiscuous mode
Jan 21 06:50:25 proxmox01 kernel: vmbr0: port 4(tap107i0) entering forwarding state
Jan 21 06:50:25 proxmox01 rgmanager[166042]: [pvevm] Task still active, waiting
Jan 21 06:50:25 proxmox01 pvevm: <root@pam> end task UPID:proxmox01:00028884:003D5134:52DE0AA0:qmstart:107:root@pam: OK
Jan 21 06:50:26 proxmox01 rgmanager[2937]: Service pvevm:107 started
Jan 21 06:50:28 proxmox01 ntpd[2378]: Listen normally on 20 tap107i0 fe80::20a4:bbff:fee6:2cb9 UDP 123
Jan 21 06:50:28 proxmox01 ntpd[2378]: peers refreshed
Jan 21 06:50:35 proxmox01 kernel: tap107i0: no IPv6 routers present
than about 7:50

Code:
Jan 21 07:50:56 proxmox01 kernel: vmbr0: port 4(tap107i0) entering disabled stateJan 21 07:50:56 proxmox01 kernel: vmbr0: port 4(tap107i0) entering disabled state
Jan 21 07:50:58 proxmox01 ntpd[2378]: Deleting interface #20 tap107i0, fe80::20a4:bbff:fee6:2cb9#123, interface stats: received=0, sent=0, dropped=0, active_time=3630 secs
Jan 21 07:50:58 proxmox01 ntpd[2378]: peers refreshed
Jan 21 07:51:04 proxmox01 rgmanager[180670]: [pvevm] VM 104 is running
Jan 21 07:51:04 proxmox01 rgmanager[180689]: [pvevm] VM 112 is running
Jan 21 07:51:14 proxmox01 rgmanager[180731]: [pvevm] VM 107 is not running
Jan 21 07:51:14 proxmox01 rgmanager[2937]: status on pvevm "107" returned 7 (unspecified)
Jan 21 07:51:15 proxmox01 rgmanager[180751]: [pvevm] VM 112 is running
Jan 21 07:51:15 proxmox01 rgmanager[2937]: Stopping service pvevm:107
Jan 21 07:51:16 proxmox01 rgmanager[180772]: [pvevm] VM 107 is already stopped
Jan 21 07:51:16 proxmox01 rgmanager[2937]: Service pvevm:107 is recovering
Jan 21 07:51:17 proxmox01 rgmanager[2937]: Recovering failed service pvevm:107
Jan 21 07:51:18 proxmox01 task UPID:proxmox01:0002C23A:0042E451:52DE18E6:qmstart:107:root@pam:: start VM 107: UPID:proxmox01:0002C23A:0042E451:52DE18E6:qmstart:107:root@pam:
Jan 21 07:51:18 proxmox01 pvevm: <root@pam> starting task UPID:proxmox01:0002C23A:0042E451:52DE18E6:qmstart:107:root@pam:
Jan 21 07:51:18 proxmox01 kernel: device tap107i0 entered promiscuous mode
Jan 21 07:51:18 proxmox01 kernel: vmbr0: port 4(tap107i0) entering forwarding state
Jan 21 07:51:19 proxmox01 rgmanager[180816]: [pvevm] Task still active, waiting
Jan 21 07:51:19 proxmox01 pvevm: <root@pam> end task UPID:proxmox01:0002C23A:0042E451:52DE18E6:qmstart:107:root@pam: OK
Jan 21 07:51:19 proxmox01 rgmanager[2937]: Service pvevm:107 started
Jan 21 07:51:21 proxmox01 ntpd[2378]: Listen normally on 21 tap107i0 fe80::d87c:49ff:fe41:5e38 UDP 123
Jan 21 07:51:21 proxmox01 ntpd[2378]: peers refreshed
Jan 21 07:51:24 proxmox01 rgmanager[180853]: [pvevm] VM 104 is running
Jan 21 07:51:28 proxmox01 kernel: tap107i0: no IPv6 routers present
and than about 8:50

Code:
Jan 21 08:51:48 proxmox01 kernel: vmbr0: port 4(tap107i0) entering disabled stateJan 21 08:51:48 proxmox01 kernel: vmbr0: port 4(tap107i0) entering disabled state
Jan 21 08:51:50 proxmox01 ntpd[2378]: Deleting interface #21 tap107i0, fe80::d87c:49ff:fe41:5e38#123, interface stats: received=0, sent=0, dropped=0, active_time=3629 secs
Jan 21 08:51:50 proxmox01 ntpd[2378]: peers refreshed
Jan 21 08:51:58 proxmox01 rgmanager[195272]: [pvevm] VM 107 is not running
Jan 21 08:51:58 proxmox01 rgmanager[2937]: status on pvevm "107" returned 7 (unspecified)
Jan 21 08:51:58 proxmox01 rgmanager[195288]: [pvevm] VM 112 is running
Jan 21 08:51:59 proxmox01 rgmanager[2937]: Stopping service pvevm:107
Jan 21 08:51:59 proxmox01 rgmanager[195322]: [pvevm] VM 107 is already stopped
Jan 21 08:51:59 proxmox01 rgmanager[2937]: Service pvevm:107 is recovering
Jan 21 08:52:00 proxmox01 rgmanager[2937]: Recovering failed service pvevm:107
Jan 21 08:52:01 proxmox01 task UPID:proxmox01:0002FB10:00487378:52DE2721:qmstart:107:root@pam:: start VM 107: UPID:proxmox01:0002FB10:00487378:52DE2721:qmstart:107:root@pam:
Jan 21 08:52:01 proxmox01 pvevm: <root@pam> starting task UPID:proxmox01:0002FB10:00487378:52DE2721:qmstart:107:root@pam:
Jan 21 08:52:02 proxmox01 kernel: device tap107i0 entered promiscuous mode
Jan 21 08:52:02 proxmox01 kernel: vmbr0: port 4(tap107i0) entering forwarding state
Jan 21 08:52:02 proxmox01 rgmanager[195366]: [pvevm] Task still active, waiting
Jan 21 08:52:02 proxmox01 pvevm: <root@pam> end task UPID:proxmox01:0002FB10:00487378:52DE2721:qmstart:107:root@pam: OK
Jan 21 08:52:02 proxmox01 rgmanager[2937]: Service pvevm:107 started
Jan 21 08:52:05 proxmox01 ntpd[2378]: Listen normally on 22 tap107i0 fe80::947d:4bff:fec3:b083 UDP 123
Jan 21 08:52:05 proxmox01 ntpd[2378]: peers refreshed
Jan 21 08:52:12 proxmox01 kernel: tap107i0: no IPv6 routers present
I have 3 nodes

proxmox00
proxmox01
proxmox02

the error is happening on both 01 and 02.. and they are the only one running VMs

There is a template and a turned off vm on prox00 so maybe its related to running VMs.. in any case i will power on the vm on prox00 to see what happens..

Also i have two HP 1810-g24 V2 switches running latest firmware connected with 4 ports in LACP where switch 1 is set to LACP-Active and switch 2 is LACP-Passiv.

I have two NAS synlogy DS1513+ connected to the switch one for vm,iso and template storage and the other for backup. The storage NAS is connected with 4 1gb cables two in each switches configured with LACP. In this setup the Switch is running LACP static on the 4 ports connecting the storage nas.

Backup nas is connected to each switch with only 1 cable in each switch with LACP and the switch ports sets to LACP-Static...

also because I had returning traffic on my bridges i added this to the /etc/network/interfaces file

Code:
  bridge_maxage 0        bridge_ageing 0
        bridge_maxwait 0
so that it looks like this

Code:
offerlam[20-01-2014 19:50:58] offerlam: auto vmbr0
iface vmbr0 inet static
        address  10.10.99.20
        netmask  255.255.255.0
        gateway  10.10.99.1
        bridge_ports bond0
        bridge_stp off
        bridge_fd 0
        bridge_maxage 0
        bridge_ageing 0
        bridge_maxwait 0
this was because of user in the forum reporting the same problems i had
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559879
and found the solution here:
http://ubuntuforums.org/showthread.php?t=1565074

Anyone has any suggestions what is happening?

THANKS

Casper
 
Last edited:

offerlam

Member
Dec 30, 2012
198
0
16
Denmark
I can add to this that proxmox02 has stopped showing this error in my syslog ..

The only other occurence is this one

Code:
[COLOR=#000000][FONT=tahoma]Jan 21 10:29:05 proxmox02 kernel: vmbr0: port 7(tap112i0) entering disabled state[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Jan 21 10:29:05 proxmox02 kernel: vmbr0: port 7(tap112i0) entering disabled state[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Jan 21 10:29:06 proxmox02 ntpd[2371]: Deleting interface #19 tap112i0, fe80::5455:7cff:fee3:5722#123, interface stats: received=0, sent=0, dropped=0, active_time=40 secs[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Jan 21 10:29:06 proxmox02 ntpd[2371]: peers refreshed[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Jan 21 10:29:08 proxmox02 pvedaemon[3063]: <root@pam> end task UPID:proxmox02:0007F02C:00514E06:52DE3DD1:qmigrate:112:root@pam: OK[/FONT][/COLOR]
 

fcukinyahoo

New Member
Nov 29, 2012
27
0
1
I dont think my problem on the original post is the same problem as we see here. I dont have any bounded interfaces and it was working without any problems before. So as for http://forum.proxmox.com/threads/17598-vmbr0-port-10(tap109i0)-entering-disabled-state problem, then what is the suggested solution??? I dont have HA and I only have one node so it can not be the HA config changes being applied... So i ll just create another post???
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE 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!