Hi, SIGTERM/INT/HUP/ALRM are intercepted in vswitchd. When they are caught some cleaning up is performed e.g. all vhost-user-XXX socket files are removed as well as socket files for communication between vswitchd and the database etc.
However, there are more signals generating a process termination but they are not handled and as a consequence there will be socket files left. When restarting, they will sometimes stop re-creation of vhostuser sockets with still existing names, resulting in log entries like these: |dpdk|ERR|vhost-user socket device setup failure for socket /var/run/openvswitch/vhostuser-e184f013-72d|bridge|WARN|could not open network device vhostuser-e184f013-72d (Unknown error -1) |dpdk|ERR|vhost-user socket device setup failure for socket /var/run/openvswitch/vhostuser-06802a37-a09|bridge|WARN|could not open network device vhostuser-06802a37-a09 (Unknown error -1) They need to be removed manually and vswitchd restarted again. Is it a "design decision" to handle only the signals as defined in fatal_signals.c? Also, why are the vhost-user sockets not abstract? Wouldn't that simplify the socket handling? Comments please, anyone? BR /Jan _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
