# Distributed Services With Go: Unable to pass readiness/liveness checks. (page 210, 215)

**URL:** <https://forum.devtalk.com/t/distributed-services-with-go-unable-to-pass-readiness-liveness-checks-page-210-215/22354>\
**Category:** PragProg Customers\
**Tags:** book-distributed-services-with-go\
**Created:** [22 September 2021 20:03 UTC](https://forum.devtalk.com/t/distributed-services-with-go-unable-to-pass-readiness-liveness-checks-page-210-215/22354 "2021-09-22T20:03:02Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![micuffaro](https://forum.devtalk.com/user_avatar/forum.devtalk.com/micuffaro/32/3438_2.png) [@micuffaro](https://forum.devtalk.com/u/micuffaro)\
**Post date:** [30 September 2021 14:28 UTC](https://forum.devtalk.com/t/distributed-services-with-go-unable-to-pass-readiness-liveness-checks-page-210-215/22354/2 "2021-09-30T14:28:05Z")

</div>

Hey [adamwoolhether](https://forum.devtalk.com/u/adamwoolhether)

Were you able to fix this?

I have the same problem, where the first instance becomes a candidate and is promoted as a leader, but then fails with `[ERROR] raft: failed to commit logs: error=EOF`, and becomes a follower again.

The application eventually times out and the pod errors out.

---

_[View the full topic](https://forum.devtalk.com/t/distributed-services-with-go-unable-to-pass-readiness-liveness-checks-page-210-215/22354)._
