# Zero: error logs about broken pipe

**URL:** <https://discuss.dgraph.io/t/zero-error-logs-about-broken-pipe/19674>\
**Category:** Dgraph\
**Tags:** kind:question\
**Created:** [December 23, 2024, 12:58pm UTC](https://discuss.dgraph.io/t/zero-error-logs-about-broken-pipe/19674 "2024-12-23T12:58:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mike42](https://avatars.discourse-cdn.com/v4/letter/m/e79b87/32.png) [@mike42](https://discuss.dgraph.io/u/mike42)\
**Post date:** [December 23, 2024, 12:58pm UTC](https://discuss.dgraph.io/t/zero-error-logs-about-broken-pipe/19674/1 "2024-12-23T12:58:07Z")

</div>

Hey,

I have deployed a simple Dgraph cluster via helm chart v24.0.5 on a three node self hosted Kubernetes cluster.

On a totally new installation every zero pod logs every 10 seconds an error message like this:

```auto
E1223 12:11:23.512475 1 x.go:352] Could not send error msg=write tcp 10.111.54.190:6080->89.XXX.XXX.115:49574: write: broken pipe code=ErrorNoData due to http error write tcp 10.111.54.190:6080->89.XXX.XXX.115:49574: write: broken pipe

```

Has anybody an idea what does this mean? (probably any liveness probe)  
I am wondering about the message content, because the “-\>” implies to me that the connection goes from the private IP of the zero pod (outgoing on port 6080) to the public IP (incoming on a random port) of the host the zero pod is running. Well this should be the other way around, right?

Could this be caused because I don’t use any ingress (disabled in the values for the helm chart)?

Thanks for any hint to get rid of it.

---

<div class="post-metadata">

**Author:** ![mike42](https://avatars.discourse-cdn.com/v4/letter/m/e79b87/32.png) [@mike42](https://discuss.dgraph.io/u/mike42)\
**Post date:** [February 8, 2025, 6:40pm UTC](https://discuss.dgraph.io/t/zero-error-logs-about-broken-pipe/19674/2 "2025-02-08T18:40:26Z")

</div>

Just to provide you with some information we figured out during the last weeks.

The mentioned error is triggered by the readiness probe on the path: /state  
When we changed it to /health like for liveness probe all zero pods work like expected without this error message.

We have also found a [pull request](https://github.com/hypermodeinc/dgraph/pull/5580) from year 2020 where the issue is already mentioned. However the path: /state is still set in the [value.yaml](https://github.com/dgraph-io/charts/blob/master/charts/dgraph/values.yaml) file for helm charts provided on GitHub (which caused the mentioned issue in my original post).

Are there any reasons to do the readiness probe for zeros on the path: /state ?