[ovs-discuss] Openvswitch bridge is not created properly sometimes

mageshgv mageshgv at gmail.com
Thu Jul 24 03:45:35 UTC 2014

Previous message: [ovs-discuss] Openvswitch bridge is not created properly sometimes
Next message: [ovs-discuss] Openvswitch bridge is not created properly sometimes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I has missed this earlier because the timestamps on OVS logs are not
matching the system time.

Here is the logs from OVS. The last few lines about non existent port 65534
and the netlink errors may be the relevant ones I hope:

2014-07-22T05:08:54.085Z|00001|vlog|INFO|opened log file
/var/log/openvswitch/ovs-vswitchd.log
2014-07-22T05:08:54.085Z|00002|reconnect|INFO|tcp:127.0.0.1:6622:
connecting...
2014-07-22T05:08:54.097Z|00003|reconnect|INFO|tcp:127.0.0.1:6622: connected
2014-07-22T05:08:54.104Z|00004|bridge|INFO|ovs-vswitchd (Open vSwitch) 2.0.0
2014-07-22T05:08:54.221Z|00005|bridge|INFO|bridge br-int: added interface
br-int on port 65534
2014-07-22T05:08:54.222Z|00006|bridge|INFO|bridge br-int: using datapath ID
0000b6b357bc7e4b
2014-07-22T05:08:54.222Z|00007|connmgr|INFO|br-int: added service
controller "punix:/var/run/openvswitch/br-int.mgmt"
2014-07-22T05:08:54.345Z|00008|bridge|INFO|bridge br-tun: added interface
br-tun on port 65534
2014-07-22T05:08:54.345Z|00009|bridge|INFO|bridge br-tun: using datapath ID
0000e6a6828f724d
2014-07-22T05:08:54.345Z|00010|connmgr|INFO|br-tun: added service
controller "punix:/var/run/openvswitch/br-tun.mgmt"
2014-07-22T05:08:54.439Z|00011|bridge|WARN|could not open network device
patch_br-int (No such device)
2014-07-22T05:08:54.481Z|00012|bridge|WARN|could not open network device
patch_br-int (No such device)
2014-07-22T05:08:54.502Z|00013|bridge|WARN|could not open network device
patch_br-tun (No such device)
2014-07-22T05:08:54.524Z|00014|netdev_vport|ERR|patch_br-int: patch type
requires valid 'peer' argument
2014-07-22T05:08:54.524Z|00015|bridge|WARN|could not configure network
device patch_br-int (Invalid argument)
2014-07-22T05:08:54.545Z|00016|bridge|WARN|could not open network device
patch_br-tun (No such device)
2014-07-22T05:08:54.568Z|00017|netdev_vport|ERR|patch_br-int: patch type
requires valid 'peer' argument
2014-07-22T05:08:54.568Z|00018|bridge|WARN|could not configure network
device patch_br-int (Invalid argument)
2014-07-22T05:08:54.568Z|00019|netdev_vport|ERR|patch_br-tun: patch type
requires valid 'peer' argument
2014-07-22T05:08:54.568Z|00020|bridge|WARN|could not configure network
device patch_br-tun (Invalid argument)
2014-07-22T05:08:54.592Z|00021|bridge|INFO|bridge br-int: added interface
patch_br-int on port 1
2014-07-22T05:08:54.592Z|00022|netdev_vport|ERR|patch_br-tun: patch type
requires valid 'peer' argument
2014-07-22T05:08:54.592Z|00023|bridge|WARN|could not configure network
device patch_br-tun (Invalid argument)
2014-07-22T05:08:54.618Z|00024|bridge|INFO|bridge br-tun: added interface
patch_br-tun on port 1
2014-07-22T05:08:54.671Z|00025|bridge|INFO|bridge br-tun: added interface
tun-192.168.101.159 on port 2
2014-07-22T05:08:54.721Z|00026|bridge|INFO|bridge br-ex: added interface
br-ex on port 65534
2014-07-22T05:08:54.721Z|00027|bridge|INFO|bridge br-ex: using datapath ID
0000eeeaac697b40
2014-07-22T05:08:54.721Z|00028|connmgr|INFO|br-ex: added service controller
"punix:/var/run/openvswitch/br-ex.mgmt"
2014-07-22T05:08:54.772Z|00029|bridge|INFO|bridge br-ex: added interface
eth1 on port 1
2014-07-22T05:08:54.819Z|00030|connmgr|INFO|br-int: added primary
controller "tcp:192.168.101.166:6633"
2014-07-22T05:08:54.819Z|00031|rconn|INFO|br-int<->tcp:192.168.101.166:6633:
connecting...
2014-07-22T05:08:54.859Z|00036|rconn|INFO|br-tun<->tcp:192.168.101.166:6633:
connection failed (Connection refused)
2014-07-22T05:09:01.601Z|00053|rconn|INFO|br-tun<->tcp:192.168.101.166:6633:
connection failed (Connection refused)
2014-07-22T05:09:01.601Z|00054|rconn|INFO|br-tun<->tcp:192.168.101.166:6633:
continuing to retry connections in the background but suppressing further
logging
2014-07-22T05:09:04.098Z|00055|memory|INFO|24088 kB peak resident set size
after 10.0 seconds
2014-07-22T05:09:04.098Z|00056|memory|INFO|facets:14 ofconns:2 ports:7
rules:28 subfacets:14
2014-07-22T05:10:13.766Z|00057|rconn|INFO|br-tun<->tcp:192.168.101.166:6633:
connected
2014-07-22T05:10:13.772Z|00058|rconn|INFO|br-int<->tcp:192.168.101.166:6633:
connected
2014-07-22T05:10:27.600Z|00059|ofproto|INFO|br-tun: 1 flow_mods 10 s ago (1
deletes)
2014-07-22T05:10:29.600Z|00060|ofproto|INFO|br-int: 5 flow_mods in the 1 s
starting 10 s ago (4 adds, 1 deletes)
2014-07-22T10:35:47.969Z|00061|bridge|INFO|bridge br-int: added interface
tap84b00f70-5e on port 2
2014-07-22T10:35:47.978Z|00001|ofproto_dpif_upcall(miss_handler)|INFO|received
packet on unassociated datapath port 6
2014-07-22T10:35:49.200Z|00062|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on
tap84b00f70-5e device failed: No such device
2014-07-22T10:35:49.394Z|00063|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on
tap84b00f70-5e device failed: No such device
2014-07-22T10:35:52.315Z|00064|bridge|INFO|bridge br-int: added interface
tap029dc49f-0e on port 3
2014-07-22T10:35:52.315Z|00065|netdev_linux|WARN|tap84b00f70-5e: removing
policing failed: No such device
2014-07-22T10:35:52.323Z|00002|ofproto_dpif_upcall(miss_handler)|INFO|received
packet on unassociated datapath port 7
2014-07-22T10:35:53.471Z|00066|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on
tap029dc49f-0e device failed: No such device
2014-07-22T10:35:54.429Z|00067|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on
tap029dc49f-0e device failed: No such device
2014-07-22T10:35:57.643Z|00068|bridge|INFO|bridge br-int: added interface
tap08c98744-8e on port 4
2014-07-22T10:35:57.643Z|00069|netdev_linux|WARN|tap029dc49f-0e: removing
policing failed: No such device
2014-07-22T10:35:58.899Z|00070|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on
tap08c98744-8e device failed: No such device
2014-07-22T10:35:59.471Z|00071|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on
tap08c98744-8e device failed: No such device
2014-07-22T10:36:03.776Z|00072|bridge|INFO|bridge br-int: added interface
tap19136701-67 on port 5
2014-07-22T10:36:03.777Z|00073|netdev_linux|WARN|tap08c98744-8e: removing
policing failed: No such device
2014-07-22T10:36:03.784Z|00003|ofproto_dpif_upcall(miss_handler)|INFO|received
packet on unassociated datapath port 9
2014-07-22T10:36:04.800Z|00074|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on
tap19136701-67 device failed: No such device
2014-07-22T10:36:09.513Z|00075|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on
tap19136701-67 device failed: No such device
2014-07-22T12:22:50.628Z|00076|dpif|WARN|system at ovs-system: failed to
flow_del (No such file or directory)
skb_priority(0),in_port(5),skb_mark(0),eth(src=80:71:1f:27:d5:4b,dst=ff:ff:ff:ff:ff:ff),eth_type(0x0806),arp(sip=192.168.102.254,tip=192.168.102.125,op=1,sha=80:71:1f:27:d5:4b,tha=00:00:00:00:00:00)
2014-07-22T12:22:50.628Z|00077|dpif|WARN|system at ovs-system: failed to
flow_del (No such file or directory)
skb_priority(0),in_port(5),skb_mark(0),eth(src=52:54:00:20:f3:3b,dst=ff:ff:ff:ff:ff:ff),eth_type(0x0806),arp(sip=192.168.100.18,tip=192.168.100.254,op=1,sha=52:54:00:20:f3:3b,tha=00:00:00:00:00:00)
2014-07-22T12:22:50.628Z|00078|dpif|WARN|system at ovs-system: failed to
flow_del (No such file or directory)
skb_priority(0),in_port(5),skb_mark(0),eth(src=52:54:00:da:f5:c1,dst=ff:ff:ff:ff:ff:ff),eth_type(0x0806),arp(sip=192.168.100.188,tip=192.168.100.254,op=1,sha=52:54:00:da:f5:c1,tha=00:00:00:00:00:00)
2014-07-22T12:22:50.628Z|00079|dpif|WARN|system at ovs-system: failed to
flow_del (No such file or directory)
skb_priority(0),in_port(5),skb_mark(0),eth(src=52:54:00:ff:96:90,dst=ff:ff:ff:ff:ff:ff),eth_type(0x0806),arp(sip=192.168.100.26,tip=192.168.100.254,op=1,sha=52:54:00:ff:96:90,tha=00:00:00:00:00:00)
2014-07-22T12:22:50.628Z|00080|dpif|WARN|system at ovs-system: failed to
flow_del (No such file or directory)
skb_priority(0),in_port(5),skb_mark(0),eth(src=80:71:1f:27:d5:4b,dst=ff:ff:ff:ff:ff:ff),eth_type(0x0806),arp(sip=192.168.102.254,tip=192.168.102.145,op=1,sha=80:71:1f:27:d5:4b,tha=00:00:00:00:00:00)
2014-07-22T12:22:50.700Z|00081|ofproto|WARN|br-ex: cannot get STP status on
nonexistent port 65534
2014-07-22T12:22:50.700Z|00082|ofproto|WARN|br-int: cannot get STP status
on nonexistent port 65534
2014-07-22T12:22:50.700Z|00083|ofproto|WARN|br-tun: cannot get STP status
on nonexistent port 65534
2014-07-22T12:22:50.800Z|00084|ofproto|WARN|br-ex: cannot get STP status on
nonexistent port 65534
2014-07-22T12:22:50.800Z|00085|ofproto|WARN|br-int: cannot get STP status
on nonexistent port 65534
2014-07-22T12:22:50.895Z|00086|netlink_socket|INFO|netlink dump request
error (No such file or directory)
2014-07-22T12:22:51.608Z|00087|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on
br-int device failed: No such device
2014-07-22T12:22:51.608Z|00088|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on
br-tun device failed: No such device
2014-07-22T12:22:51.895Z|00089|netlink_socket|INFO|netlink dump request
error (No such file or directory)
2014-07-22T12:22:51.608Z|00087|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on
br-int device failed: No such device
2014-07-22T12:22:51.608Z|00088|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on
br-tun device failed: No such device
2014-07-22T12:22:51.895Z|00089|netlink_socket|INFO|netlink dump request
error (No such file or directory)
2014-07-22T12:22:51.895Z|00090|dpif|WARN|Dropped 9 log messages in last 1
seconds (most recently, 1 seconds ago) due to excessive rate
2014-07-22T12:22:54.641Z|00097|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on
br-ex device failed: No such device
2014-07-22T12:22:54.649Z|00098|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on
br-ex device failed: No such device
2014-07-22T12:22:54.649Z|00099|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on
br-int device failed: No such device
2014-07-22T12:22:54.680Z|00100|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on
br-tun device failed: No such device
2014-07-22T12:22:54.896Z|00101|netlink_socket|INFO|netlink dump request
error (No such file or directory)
2014-07-22T12:22:55.896Z|00102|netlink_socket|INFO|netlink dump request
error (No such file or directory)
2014-07-22T12:22:56.896Z|00103|netlink_socket|INFO|netlink dump request
error (No such file or directory)
2014-07-22T12:22:57.896Z|00104|netlink_socket|INFO|netlink dump request
error (No such file or directory)
2014-07-22T12:22:58.897Z|00105|netlink_socket|INFO|netlink dump request
error (No such file or directory)
2014-07-22T12:22:59.896Z|00106|netlink_socket|INFO|netlink dump request
error (No such file or directory)
2014-07-22T12:23:00.896Z|00107|netlink_socket|INFO|netlink dump request
error (No such file or directory)

On Wed, Jul 23, 2014 at 11:55 PM, Ben Pfaff <blp at nicira.com> wrote:

> On Wed, Jul 23, 2014 at 04:10:49PM +0530, mageshgv wrote:
> > We are facing an issue with Openvswitch 2.0.0 package built from source
> > code for Ubuntu 13.04.
> >
> > We have patched the openvswitch init script to invoke another script,
> that
> > creates two OVS bridges during openvswitch start.
> >
> > The problem is that out of some 1000 runs, the following issue is hit in
> > around 5 runs.
> >
> > The bridges are getting created in the OVSDB. But the physical bridge is
> > not created.
> >
> > root at compute-node2:~# ovs-ofctl show br-int
> > ovs-ofctl: br-int is not a bridge or a socket
> >
> > root at compute-node2:~# ovs-ofctl show br-tun
> > ovs-ofctl: br-tun is not a bridge or a socket
>
> What's in the OVS log?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/discuss/attachments/20140724/3508e85d/attachment.html>

Previous message: [ovs-discuss] Openvswitch bridge is not created properly sometimes
Next message: [ovs-discuss] Openvswitch bridge is not created properly sometimes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the discuss mailing list