Hello all,
I have built a test cluster using 4 machines and OVS
I have used the example config from https://pve.proxmox.com/wiki/Open_vSwitch with bonding .
What i am seeing is when I add or remove a port/vlan (i.e start a container) the OVS Seg faults
i have debugged it down to the
/usr/bin/ovs-vsctl del-port veth101.0
/usr/bin/ovs-vsctl add-port vmbr0 veth101.0 tag=10
015-04-23T03:27:53.790Z|05941|netdev_linux|WARN|veth101.2: obtaining netdev stats via vport failed (No such device)
2015-04-23T03:27:53.790Z|05942|netdev_linux|WARN|veth101.1: obtaining netdev stats via vport failed (No such device)
2015-04-23T03:27:53.791Z|05943|netdev_linux|WARN|veth101.0: obtaining netdev stats via vport failed (No such device)
2015-04-23T03:28:07.851Z|05944|bridge|WARN|could not open network device veth101.2 (No such device)
2015-04-23T03:28:07.853Z|05945|bridge|WARN|could not open network device veth101.0 (No such device)
2015-04-23T03:28:07.854Z|05946|bridge|INFO|bridge vmbr0: using datapath ID 00003440b58020c4
2015-04-23T03:28:07.879Z|05947|bond|INFO|interface eth1: link state down
2015-04-23T03:28:07.879Z|05948|bond|INFO|interface eth1: disabled
2015-04-23T03:28:08.798Z|05949|bond|INFO|interface eth0: link state down
2015-04-23T03:28:08.798Z|05950|bond|INFO|interface eth0: disabled
2015-04-23T03:28:08.798Z|05951|bond|INFO|bond bond0: all interfaces disabled
2015-04-23T03:28:08.964Z|00002|daemon_unix(monitor)|ERR|1 crashes: pid 1966 died, killed (Segmentation fault), core dumped, restarting
2015-04-23T03:28:08.966Z|00003|memory|INFO|6688 kB peak resident set size after 7588.4 seconds
2015-04-23T03:28:08.966Z|00004|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connecting...
2015-04-23T03:28:08.966Z|00005|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connected
2015-04-23T03:28:09.064Z|00006|ofproto_dpif|INFO|system@ovs-system: Datapath supports recirculation
2015-04-23T03:28:09.064Z|00007|dpif|WARN|system@ovs-system: execute userspace(pid=0,userdata(00000000)) failed (Invalid argument) on packet metadata=0,in_port=0,vlan_tci=0x0000,dl_src=00:00:00:00:00:00,dl_dst=00:00:00:00:00:00,dl_type=0x1234
2015-04-23T03:28:09.064Z|00008|ofproto_dpif|WARN|system@ovs-system: variable-length userdata feature probe failed (Invalid argument)
2015-04-23T03:28:09.064Z|00009|dpif|WARN|system@ovs-system: failed to put[create] (Invalid argument) skb_priority(0),skb_mark(0),in_port(0),eth(src=00:00:00:00:00:00,dst=00:00:00:00:00:00),eth_type(0x8847),mpls(label=0,tc=0,ttl=0,bos=1)
2015-04-23T03:28:09.064Z|00010|ofproto_dpif|INFO|system@ovs-system: MPLS label stack length probed as 0
it takes 30-70 seconds for this to come back up.
Any ideas on how i can resolve this ,
I have tried downgrading from 2.3.1-1 to 2.0.90-4 with no luck
ATM I have had to switch LACP off
Cheers
I have built a test cluster using 4 machines and OVS
I have used the example config from https://pve.proxmox.com/wiki/Open_vSwitch with bonding .
What i am seeing is when I add or remove a port/vlan (i.e start a container) the OVS Seg faults
i have debugged it down to the
/usr/bin/ovs-vsctl del-port veth101.0
/usr/bin/ovs-vsctl add-port vmbr0 veth101.0 tag=10
015-04-23T03:27:53.790Z|05941|netdev_linux|WARN|veth101.2: obtaining netdev stats via vport failed (No such device)
2015-04-23T03:27:53.790Z|05942|netdev_linux|WARN|veth101.1: obtaining netdev stats via vport failed (No such device)
2015-04-23T03:27:53.791Z|05943|netdev_linux|WARN|veth101.0: obtaining netdev stats via vport failed (No such device)
2015-04-23T03:28:07.851Z|05944|bridge|WARN|could not open network device veth101.2 (No such device)
2015-04-23T03:28:07.853Z|05945|bridge|WARN|could not open network device veth101.0 (No such device)
2015-04-23T03:28:07.854Z|05946|bridge|INFO|bridge vmbr0: using datapath ID 00003440b58020c4
2015-04-23T03:28:07.879Z|05947|bond|INFO|interface eth1: link state down
2015-04-23T03:28:07.879Z|05948|bond|INFO|interface eth1: disabled
2015-04-23T03:28:08.798Z|05949|bond|INFO|interface eth0: link state down
2015-04-23T03:28:08.798Z|05950|bond|INFO|interface eth0: disabled
2015-04-23T03:28:08.798Z|05951|bond|INFO|bond bond0: all interfaces disabled
2015-04-23T03:28:08.964Z|00002|daemon_unix(monitor)|ERR|1 crashes: pid 1966 died, killed (Segmentation fault), core dumped, restarting
2015-04-23T03:28:08.966Z|00003|memory|INFO|6688 kB peak resident set size after 7588.4 seconds
2015-04-23T03:28:08.966Z|00004|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connecting...
2015-04-23T03:28:08.966Z|00005|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connected
2015-04-23T03:28:09.064Z|00006|ofproto_dpif|INFO|system@ovs-system: Datapath supports recirculation
2015-04-23T03:28:09.064Z|00007|dpif|WARN|system@ovs-system: execute userspace(pid=0,userdata(00000000)) failed (Invalid argument) on packet metadata=0,in_port=0,vlan_tci=0x0000,dl_src=00:00:00:00:00:00,dl_dst=00:00:00:00:00:00,dl_type=0x1234
2015-04-23T03:28:09.064Z|00008|ofproto_dpif|WARN|system@ovs-system: variable-length userdata feature probe failed (Invalid argument)
2015-04-23T03:28:09.064Z|00009|dpif|WARN|system@ovs-system: failed to put[create] (Invalid argument) skb_priority(0),skb_mark(0),in_port(0),eth(src=00:00:00:00:00:00,dst=00:00:00:00:00:00),eth_type(0x8847),mpls(label=0,tc=0,ttl=0,bos=1)
2015-04-23T03:28:09.064Z|00010|ofproto_dpif|INFO|system@ovs-system: MPLS label stack length probed as 0
it takes 30-70 seconds for this to come back up.
Any ideas on how i can resolve this ,
I have tried downgrading from 2.3.1-1 to 2.0.90-4 with no luck
ATM I have had to switch LACP off
Cheers
Last edited: