Public bug reported:
crashing / killing ovs-vswitchd doesn't clean up vhost_user sockets
If a crash occurs the subsequent automated restart of openvswitch by its
monitor runs into collisions with the existing sockets.
Messages are like:
Apr 07 11:36:43 horsea ovs-vswitchd[21481]: VHOST_CONFIG: socket created, fd:346
Apr 07 11:36:43 horsea ovs-vswitchd[21481]: VHOST_CONFIG: fail to bind fd:346,
remove file:/var/run/openvswitch/vhost-user-979 and try again.
Note: this was discussed on the mailing list a while ago, we need to
check if/what the supposed handling should be.
The DPDK code gets a path to the socket from openvswitch - it is
debatable if ovs or dpdk should remove that file if a collision occurs.
** Affects: dpdk (Ubuntu)
Importance: Medium
Status: Triaged
** Affects: openvswitch-dpdk (Ubuntu)
Importance: Undecided
Status: New
** Changed in: dpdk (Ubuntu)
Status: New => Triaged
** Changed in: dpdk (Ubuntu)
Importance: Undecided => Medium
** Also affects: openvswitch-dpdk (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567383
Title:
crashing / killing ovs-vswitchd doesn't clean up vhost_user sockets
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1567383/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
