Re: [atomic-devel] Systemd Flanneld Exit 0

2018-01-18 Thread Dusty Mabe
On 01/16/2018 03:01 PM, hskarlupka wrote: > All, Hey Heath, > > I'm running a 4 node CentOS 7 Atomic Kubernetes Cluster.  I ran into an > issue over the weekend where two of my nodes stopped running flanneld.  > "Systemctl status flanneld" showed that the processes had an exit status > of 0

Re: [atomic-devel] Systemd Flanneld Exit 0

2018-01-18 Thread Ben Breard
I'm not sure why Restart=on-failure is the default. On my systems, I always default to Restart=always. I don't see value in shying away from a hammer approach when you need something to always be running. $0.02, On Tue, Jan 16, 2018 at 2:01 PM, hskarlupka < heath.skarlu...@icecube.wisc.edu> wrote

[atomic-devel] Systemd Flanneld Exit 0

2018-01-16 Thread hskarlupka
All, I'm running a 4 node CentOS 7 Atomic Kubernetes Cluster.  I ran into an issue over the weekend where two of my nodes stopped running flanneld.  "Systemctl status flanneld" showed that the processes had an exit status of 0 and were not running.  The Unit file sets "Restart=on-failure" ins