You took it wrong. :) Even killing the pid with monitoring process running
also doesn't bring it up. Yes, to of-course humans do mistake so we better
can handle it via respawn which is what I am trying to convey. So was
thinking, can we add that feature in current code base too as an additional
You killed the monitor process, of course it couldn't revive the
monitored process.
If you have people going around killing processes without thinking,
that's your problem.
On Sat, Apr 29, 2017 at 12:59:50PM -0700, Aliasgar Mikail Ginwala wrote:
> Same is reproducible using SIGABRT (kill -6)
>
Same is reproducible using SIGABRT (kill -6)
ps aux | grep ovn-controller
root 927884 0.0 0.0 26792 956 ?S wrote:
> Please read the ovs-vswitchd manpage. It says:
>
>--monitor
> Creates an additional process to monitor the ovs-vswitchd
> dae‐
>
Please read the ovs-vswitchd manpage. It says:
--monitor
Creates an additional process to monitor the ovs-vswitchd dae‐
mon. If the daemon dies due to a signal that indicates a pro‐
gramming error (SIGABRT, SIGALRM, SIGBUS, SIGFPE, SIGILL,
When you say that ovn-controller crashed, what do you mean? Do you mean
that you killed it? Which process, and how did you kill it?
On Fri, Apr 28, 2017 at 10:51:04PM -0700, Aliasgar Mikail Ginwala wrote:
> Yes:
>
> ps aux | grep controller
> root 3639845 0.0 0.0 26792 952 ?S
Is it running with the --monitor option? If not, either --monitor
should be added or the upstart features should be used.
On Fri, Apr 28, 2017 at 05:16:09PM -0700, Aliasgar Mikail Ginwala wrote:
> I did double verify:
>
> This is what is happening after crashing the ovn pid:
>
> service
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
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
Hello Devs:
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.
Looking forward for your
