[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: livenessProbe

We were using it for the registry and it was working fine (https://github.com/openshift/origin/blob/master/pkg/cmd/admin/registry/registry.go#L253-L265), although it's been disabled for a long time because we had issues when users were toggling back and forth between the v1 and v2 registry implementations. Which reminds me, we need to reenable it :-)


On Tue, Oct 13, 2015 at 11:37 PM, Philippe Lafoucrière <philippe lafoucriere tech-angels com> wrote:

Is anyone here using livenessProbe on pods?
I have added this to my dc:

# defines the health checking
  # an http probe
    path: /
    port: 8080
  # length of time to wait for a pod to initialize
  # after pod startup, before applying health checking
  initialDelaySeconds: 30
  timeoutSeconds: 3

While the app is up in 10s, it seems to restart it every time, even if the service is responding.
I have in the events:

Liveness probe failed: Get read tcp use of closed network connection (4 times in the last 2 minutes, 31 seconds)

No error reported in the logs, just the container being killed.


users mailing list
users lists openshift redhat com

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]