Ask Your Question

ovs-vswitchd crashing continuously on reboot of network node

asked 2015-04-24 18:01:49 -0500

Nate_McKay gravatar image


I recently finished the first phase of a 4 node OpenStack (Juno) lab on CentOS 7 using the guide found here: (

On the whole this went pretty smoothly and I was able to launch instances and ping the l3 agent router IPs etc. I'm running into an external issue that necessitates that I reboot my network node and am finding that after it comes back up, my instances are no longer able to leverage any network node services any longer (dhcp and l3 are now inaccessible).

I noticed that ovs-vswitchd seems to be crashing and respawning constantly after the reboot with messages to this effect:

2015-04-22T03:07:31.535Z|00023|bridge|INFO|ovs-vswitchd (Open vSwitch) 2.1.3
2015-04-24T21:47:21.457Z|00024|memory|INFO|43132 kB peak resident set size after 10.0 seconds
2015-04-24T21:47:21.457Z|00025|memory|INFO|dispatchers:1 flow_dumpers:1 handlers:1 ports:13 revalidator keys:1 revalidators:1 rules:11
2015-04-24T21:47:26.187Z|00026|bridge|INFO|bridge br-int: added interface tap9dc19b59-70 on port 1
2015-04-24T21:47:26.855Z|00027|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on tap9dc19b59-70 device failed: No such device
2015-04-24T21:47:26.874Z|00028|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on tap9dc19b59-70 device failed: No such device
2015-04-24T21:47:26.875Z|00029|netdev_linux|WARN|tap9dc19b59-70: removing policing failed: No such device
2015-04-24T21:47:27.013Z|00030|bridge|INFO|bridge br-int: added interface int-br-ex on port 2
2015-04-24T21:47:27.160Z|00031|bridge|INFO|bridge br-ex: added interface phy-br-ex on port 2
2015-04-24T21:47:27.652Z|00002|daemon(monitor)|ERR|1 crashes: pid 666 died, killed (Segmentation fault), restarting
2015-04-24T21:47:27.655Z|00003|memory|INFO|9520 kB peak resident set size after 16.2 seconds
2015-04-24T21:47:27.655Z|00004|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connecting...
2015-04-24T21:47:27.655Z|00005|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connected
2015-04-24T21:47:27.706Z|00006|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on tap9dc19b59-70 device failed: No such device
2015-04-24T21:47:27.709Z|00007|bridge|INFO|bridge br-ex: added interface br-ex on port 65534
2015-04-24T21:47:27.709Z|00008|bridge|INFO|bridge br-ex: added interface eno50338560 on port 1
2015-04-24T21:47:27.709Z|00009|bridge|INFO|bridge br-ex: added interface phy-br-ex on port 2
2015-04-24T21:47:27.709Z|00010|bridge|INFO|bridge br-int: added interface br-int on port 65534
2015-04-24T21:47:27.709Z|00011|bridge|INFO|bridge br-int: added interface tap9dc19b59-70 on port 1
2015-04-24T21:47:27.712Z|00012|netdev_linux|WARN|ioctl(SIOCGIFINDEX) on tap9dc19b59-70 device failed: No such device
2015-04-24T21:47:27.712Z|00013|bridge|INFO|bridge br-int: added interface int-br-ex on port 2
2015-04-24T21:47:27.712Z|00014|bridge|INFO|bridge br-ex: using datapath ID 0000005056996d07
2015-04-24T21:47:27.712Z|00015|connmgr|INFO|br-ex: added service controller "punix:/var/run/openvswitch/br-ex.mgmt"
2015-04-24T21:47:27.712Z|00016|bridge|INFO|bridge br-int: using datapath ID 00003a25509d8841
2015-04-24T21:47:27.712Z|00017|netdev_linux ...
edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2015-04-25 23:58:09 -0500

dbaxps gravatar image

updated 2015-04-26 00:06:41 -0500

You are running OVS 2.1.3 on CentOS 7. Please,view
If this a case, it might be fixed now just via yum update to OVS 2.3.1 . It is 100% bug on CentOS 7.1
Kernel 3.10.0-229.1.2.el7.x86_64 doesn't work with OVS 2.1.3.

edit flag offensive delete link more


Yeah that's sorted it. Too easy, thanks!

Nate_McKay gravatar imageNate_McKay ( 2015-04-26 02:44:13 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2015-04-24 18:01:49 -0500

Seen: 744 times

Last updated: Apr 26 '15