# Temporal PODS not coming up with "index\_not\_found\_exception" error

**URL:** <https://community.temporal.io/t/temporal-pods-not-coming-up-with-index-not-found-exception-error/9010>\
**Category:** Server Deployment\
**Tags:** elasticsearch, mysql, helm\
**Created:** [July 30, 2023, 11:01am UTC](https://community.temporal.io/t/temporal-pods-not-coming-up-with-index-not-found-exception-error/9010 "2023-07-30T11:01:39Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![nkkrishna](https://avatars.discourse-cdn.com/v4/letter/n/7bcc69/32.png) [@nkkrishna](https://community.temporal.io/u/nkkrishna)\
**Post date:** [July 30, 2023, 11:01am UTC](https://community.temporal.io/t/temporal-pods-not-coming-up-with-index-not-found-exception-error/9010/1 "2023-07-30T11:01:39Z")

</div>

I am trying to deploy temporal using latest helm charts in GCP with **mysql8** instance. Elasticsearch, admin-tools and web pods are up and running. All the other pods like _history, frontend, matching and history pods_ are in **Init: 0/1** for very longtime. I could see, **check-elasticsearch-index** is in Running state with logs "_waiting for elasticsearch index to become ready_ ". i tried a curl from admin-tools pod, i could see following error

```auto
temporaldev-admintools-7f49894494-2pb58:/etc/temporal$ curl http://temporaldev-elasticsearch-master-headless:9200/temporal_visibility_v1_dev
{"error":{"root_cause":[{"type":"index_not_found_exception","reason":"no such index [temporal_visibility_v1_dev]","resource.type":"index_or_alias","resource.id":"temporal_visibility_v1_dev","index_uuid":"_na_","index":"temporal_visibility_v1_dev"}],"type":"index_not_found_exception","reason":"no such index [temporal_visibility_v1_dev]","resource.type":"index_or_alias","resource.id":"temporal_visibility_v1_dev","index_uuid":"_na_","index":"temporal_visibility_v1_dev"},"status":404}temporaldev-admintools-7f49894494-2pb58:/etc/temporal$

```

---

<div class="post-metadata">

**Author:** ![Raul-Ronald](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/raul-ronald/32/4548_2.png) [@Raul-Ronald](https://community.temporal.io/u/Raul-Ronald)\
**Post date:** [November 22, 2023, 9:45am UTC](https://community.temporal.io/t/temporal-pods-not-coming-up-with-index-not-found-exception-error/9010/2 "2023-11-22T09:45:22Z")

</div>

Having the same issue, did you manage to solve it?

I believe the problem might be a bug in the helm chart, see this [issue](https://github.com/temporalio/helm-charts/issues/445)

---

<div class="post-metadata">

**Author:** ![kaleby](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/kaleby/32/5198_2.png) [@kaleby](https://community.temporal.io/u/kaleby)\
**Post date:** [April 9, 2024, 5:48pm UTC](https://community.temporal.io/t/temporal-pods-not-coming-up-with-index-not-found-exception-error/9010/3 "2024-04-09T17:48:39Z")

</div>

Same issue here any solution?

---

<div class="post-metadata">

**Author:** ![Rashmi\_Sahu](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/rashmi_sahu/32/5443_2.png) [@Rashmi\_Sahu](https://community.temporal.io/u/Rashmi_Sahu)\
**Post date:** [July 29, 2024, 9:48am UTC](https://community.temporal.io/t/temporal-pods-not-coming-up-with-index-not-found-exception-error/9010/4 "2024-07-29T09:48:25Z")

</div>

You can easily deploy temporal on ECS with 5 separate services for temporal server, temporal ui, temporal admin tools, elasticsearch and postgresql.  
There will be 5 separate ecs services for all above in a same cluster.  
Feel free to contact me if need any help there as i have recently deployed it on ECS and everything is working fine for me.