# Apiserver liveness and readiness probes fail randomly with code 500

**URL:** <https://discuss.kubernetes.io/t/apiserver-liveness-and-readiness-probes-fail-randomly-with-code-500/20719>\
**Category:** General Discussions\
**Created:** [July 22, 2022, 9:33am UTC](https://discuss.kubernetes.io/t/apiserver-liveness-and-readiness-probes-fail-randomly-with-code-500/20719 "2022-07-22T09:33:11Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nicola\_Urbinati](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/nicola_urbinati/32/10028_2.png) [@Nicola\_Urbinati](https://discuss.kubernetes.io/u/Nicola_Urbinati)\
**Post date:** [July 22, 2022, 9:33am UTC](https://discuss.kubernetes.io/t/apiserver-liveness-and-readiness-probes-fail-randomly-with-code-500/20719/1 "2022-07-22T09:33:11Z")

</div>

### Cluster information:

Kubernetes version:  
Cloud being used: bare-metal  
Installation method: kubeadm  
Host OS: Ubuntu 22.04  
CNI and version: Calico 3.23.3  
CRI and version: [containerd.io](http://containerd.io) 1.6.6

Hi,

I’m having quite a lot of warning events, like:

```auto
kube-apiserver-k8cp1.170418e7b72f9344
kube-system
Unhealthy
Readiness probe failed: HTTP probe failed with statuscode: 500

```

or

```auto
kube-apiserver-k8cp3.17041b3d302fd052
kube-system
Unhealthy
Liveness probe failed: HTTP probe failed with statuscode: 500

```

They do not trigger pod restarts, but make me feel uneasy about my cluster health.

Is there a way to properly debug them?

Here is my apiserver manifest (already set readinessProbe periodSeconds from 1 to 5 without any benefit)

```auto
    livenessProbe:
      failureThreshold: 8
      httpGet:
        host: 10.0.50.31
        path: /livez
        port: 6443
        scheme: HTTPS
      initialDelaySeconds: 10
      periodSeconds: 10
      timeoutSeconds: 15
    name: kube-apiserver
    readinessProbe:
      failureThreshold: 3
      httpGet:
        host: 10.0.50.31
        path: /readyz
        port: 6443
        scheme: HTTPS
      periodSeconds: 5
      timeoutSeconds: 15
    resources:
      requests:
        cpu: 250m
    startupProbe:
      failureThreshold: 24
      httpGet:
        host: 10.0.50.31
        path: /livez
        port: 6443
        scheme: HTTPS
      initialDelaySeconds: 10
      periodSeconds: 10
      timeoutSeconds: 15

```

Also, curl to the probe api gives proper result, even if repeated:

```auto
ubuntu@k8cp1:~$ curl -k https://10.0.50.31:6443/readyz
ok

```

Anything else to try or set?

---

<div class="post-metadata">

**Author:** ![shorif2000](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/shorif2000/32/11590_2.png) [@shorif2000](https://discuss.kubernetes.io/u/shorif2000)\
**Post date:** [January 11, 2023, 3:10pm UTC](https://discuss.kubernetes.io/t/apiserver-liveness-and-readiness-probes-fail-randomly-with-code-500/20719/2 "2023-01-11T15:10:46Z")

</div>

did you fix this. i have same problem. i believe its trying to access via https but would work insecurly but not sure where to set this so it works insecurly

---

<div class="post-metadata">

**Author:** ![Nicola\_Urbinati](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/nicola_urbinati/32/10028_2.png) [@Nicola\_Urbinati](https://discuss.kubernetes.io/u/Nicola_Urbinati)\
**Post date:** [January 18, 2023, 3:09pm UTC](https://discuss.kubernetes.io/t/apiserver-liveness-and-readiness-probes-fail-randomly-with-code-500/20719/3 "2023-01-18T15:09:31Z")

</div>

Not yet, don’t know if there was a network or a protocol problem or anything else.

---

<div class="post-metadata">

**Author:** ![Vitalii\_Shevchuk](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/vitalii_shevchuk/32/12592_2.png) [@Vitalii\_Shevchuk](https://discuss.kubernetes.io/u/Vitalii_Shevchuk)\
**Post date:** [May 23, 2023, 7:06pm UTC](https://discuss.kubernetes.io/t/apiserver-liveness-and-readiness-probes-fail-randomly-with-code-500/20719/4 "2023-05-23T19:06:15Z")

</div>

Hi.

I’ve had the same issue and fixed it with the commands

```auto
mkdir -p /etc/containerd
containerd config default | tee /etc/containerd/config.toml
sed -i 's/SystemdCgroup = false/SystemdCgroup = true/g' /etc/containerd/config.toml
systemctl restart containerd

```

Hope this will help to you too