I did double verify: This is what is happening after crashing the ovn pid:
service ovn-host status Pidfile for ovn-controller (/var/run/openvswitch/ovn-controller.pid) is stale Works only after manual restart and didn't respawn service ovn-host restart 2017-04-29T00:14:37Z|00001|unixctl|WARN|failed to connect to /var/run/openvswitch/ovn-controller.3623709.ctl ovs-appctl: cannot connect to "/var/run/openvswitch/ovn-controller.3623709.ctl" (Connection refused) * Starting ovn-controller Regards, Aliasgar On Fri, Apr 28, 2017 at 4:50 PM, Ben Pfaff <b...@ovn.org> wrote: > On Fri, Apr 28, 2017 at 04:02:26PM -0700, Aliasgar Mikail Ginwala wrote: > > Recently when I was adding monitoring and alerting for ovs and ovn > version > > 2.7.0, I found both of the upstart services are missing *respawn* . Is it > > on purpose? If it's not then lets handle it as an improvement to add it > in > > the upstart. Suggestions welcome. > > OVS and OVN already restarts itself, so probably nothing is needed. > _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
