Different problems started after VE update

[Fiko]

Hi all
Problems seems to be related to networking issues, but can't confirm, problem continue after reboot also.
Syslog:
ul 20 12:48:40 proxprod4 kernel: [32690545.502283] fwbr260i0: port 2(tap260i0) entered disabled state
Jul 20 12:48:40 proxprod4 kernel: [32690545.547846] fwbr260i0: port 1(fwln260i0) entered disabled state
Jul 20 12:48:40 proxprod4 kernel: [32690545.548048] vmbr1: port 14(fwpr260p0) entered disabled state
Jul 20 12:48:40 proxprod4 kernel: [32690545.548572] device fwln260i0 left promiscuous mode
Jul 20 12:48:40 proxprod4 kernel: [32690545.548576] fwbr260i0: port 1(fwln260i0) entered disabled state
Jul 20 12:48:40 proxprod4 kernel: [32690545.590250] device fwpr260p0 left promiscuous mode
Jul 20 12:48:40 proxprod4 kernel: [32690545.590254] vmbr1: port 14(fwpr260p0) entered disabled state
Jul 20 12:48:50 proxprod4 kernel: [32690555.266690] rbd11: p1
Jul 20 12:48:50 proxprod4 kernel: [32690555.267223] rbd: rbd11: capacity 34359738368 features 0x3d
Jul 20 12:48:50 proxprod4 kernel: [32690555.984398] device tap260i0 entered promiscuous mode
Jul 20 12:48:50 proxprod4 kernel: [32690556.063297] fwbr260i0: port 1(fwln260i0) entered blocking state
Jul 20 12:48:50 proxprod4 kernel: [32690556.063299] fwbr260i0: port 1(fwln260i0) entered disabled state
Jul 20 12:48:50 proxprod4 kernel: [32690556.063451] device fwln260i0 entered promiscuous mode
Jul 20 12:48:50 proxprod4 kernel: [32690556.063524] fwbr260i0: port 1(fwln260i0) entered blocking state
Jul 20 12:48:50 proxprod4 kernel: [32690556.063526] fwbr260i0: port 1(fwln260i0) entered forwarding state
Jul 20 12:48:50 proxprod4 kernel: [32690556.072974] vmbr1: port 14(fwpr260p0) entered blocking state
Jul 20 12:48:50 proxprod4 kernel: [32690556.072978] vmbr1: port 14(fwpr260p0) entered disabled state
Jul 20 12:48:50 proxprod4 kernel: [32690556.073126] device fwpr260p0 entered promiscuous mode
Jul 20 12:48:50 proxprod4 kernel: [32690556.073212] vmbr1: port 14(fwpr260p0) entered blocking state
Jul 20 12:48:50 proxprod4 kernel: [32690556.073213] vmbr1: port 14(fwpr260p0) entered forwarding state
Jul 20 12:48:50 proxprod4 kernel: [32690556.082407] fwbr260i0: port 2(tap260i0) entered blocking state
Jul 20 12:48:50 proxprod4 kernel: [32690556.082410] fwbr260i0: port 2(tap260i0) entered disabled state
Jul 20 12:48:50 proxprod4 kernel: [32690556.082600] fwbr260i0: port 2(tap260i0) entered blocking state
Jul 20 12:48:50 proxprod4 kernel: [32690556.082602] fwbr260i0: port 2(tap260i0) entered forwarding state
Jul 20 20:28:55 proxprod4 kernel: [32718160.588318] fwbr139i0: port 2(tap139i0) entered disabled state
Jul 20 20:28:55 proxprod4 kernel: [32718160.588730] fwbr139i0: port 2(tap139i0) entered disabled state
Jul 20 20:29:54 proxprod4 kernel: [32718219.492605] rbd: rbd12: breaking header lock owned by client413913880
Jul 20 20:29:54 proxprod4 kernel: [32718219.744661] rbd: rbd12: breaking object map lock owned by client413913880
Jul 20 20:29:54 proxprod4 kernel: [32718219.792411] rbd12: p1 p2
Jul 20 20:29:54 proxprod4 kernel: [32718219.793001] rbd: rbd12: capacity 42949672960 features 0x3d
Jul 20 20:29:54 proxprod4 kernel: [32718220.438667] device tap139i0 entered promiscuous mode
Jul 20 20:29:54 proxprod4 kernel: [32718220.450640] fwbr139i0: port 1(fwln139i0) entered disabled state
Jul 20 20:29:54 proxprod4 kernel: [32718220.450813] vmbr1: port 8(fwpr139p0) entered disabled state
Jul 20 20:29:54 proxprod4 kernel: [32718220.451244] device fwln139i0 left promiscuous mode
Jul 20 20:29:54 proxprod4 kernel: [32718220.451249] fwbr139i0: port 1(fwln139i0) entered disabled state

 

[Stefan_R]

What is the error exactly? The log you posted contains only normal messages, there's nothing wrong there...

Please describe in more detail what doesn't work, i.e. what do you expect to happen and what happens instead.