# After-reboot on a monolith consistently fails on start Zookeeper service

**URL:** <https://forum.dimagi.com/t/after-reboot-on-a-monolith-consistently-fails-on-start-zookeeper-service/9102>\
**Category:** Developers\
**Created:** [June 25, 2022, 8:37pm UTC](https://forum.dimagi.com/t/after-reboot-on-a-monolith-consistently-fails-on-start-zookeeper-service/9102 "2022-06-25T20:37:50Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![Sravan\_Reddy](https://dimagi.b-cdn.net/letter_avatar_proxy/v4/letter/s/da6949/32.png) [@Sravan\_Reddy](https://forum.dimagi.com/u/Sravan_Reddy)\
**Post date:** [July 7, 2022, 7:26am UTC](https://forum.dimagi.com/t/after-reboot-on-a-monolith-consistently-fails-on-start-zookeeper-service/9102/7 "2022-07-07T07:26:02Z")

</div>

This issue has just been [fixed](https://github.com/dimagi/commcare-cloud/pull/5359).

Can you please do update-code and then deploy zookeeper using `commcare-cloud $env_name deploy-stack --skip-check -tags=zookeeper`? That should create the missing config file and restart the zookeeper. You can verify that it's fixed by re-looking at the status of the zookeeper process.

---

_[View the full topic](https://forum.dimagi.com/t/after-reboot-on-a-monolith-consistently-fails-on-start-zookeeper-service/9102)._