# Failed to detect running cluster - instance was not detected as running in time

**URL:** <https://discuss.elastic.co/t/failed-to-detect-running-cluster-instance-was-not-detected-as-running-in-time/254257>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [November 4, 2020, 11:14am UTC](https://discuss.elastic.co/t/failed-to-detect-running-cluster-instance-was-not-detected-as-running-in-time/254257 "2020-11-04T11:14:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mesiasc](https://avatars.discourse-cdn.com/v4/letter/m/b38774/32.png) [@mesiasc](https://discuss.elastic.co/u/mesiasc)\
**Post date:** [November 4, 2020, 11:14am UTC](https://discuss.elastic.co/t/failed-to-detect-running-cluster-instance-was-not-detected-as-running-in-time/254257/1 "2020-11-04T11:14:33Z")

</div>

I have ECE 2.5.1 with over 30GB capacity spare over 3 zones. I am unable to create new clusters, the full message is:

```auto
Plan change failed: [ClusterFailure:InstanceDidNotStartWhileWaitingForRunning]: Failed to detect running cluster - instance was not detected as running in time. Check the health of the cluster, and look at the instance and/or allocator logs to determine if there were any issues starting. Details: [{"details":"The state did not become the desired one before [600000 milliseconds] elapsed. Last error was: [Instance is not running [instance-0000000001]. Please check allocator/docker logs.]"}]

```

I have tried to find more logs and wasn't sure if this was relevant:

```auto
allocator/logs/allocator.log:[2020-11-03 17:11:18,345][ERROR][no.found.runner.allocation.elasticsearch.ElasticsearchDockerContainerManager] Unexpected error during allocation {"ec_container_name":"instance-0000000000","cluster_type":"elasticsearch","ec_container_group":"3b011a14a88d4e919525dc8a974e43e2","cluster_id":"3b011a14a88d4e919525dc8a974e43e2","instance_id":"instance-0000000000","ec_container_kind":"elasticsearch"}

```

Checking the disk usage on the hosts, root volume was 95% full and seems to contain Docker related content. So I initially tried to reduce disk requirement by choosing a version of elasticsearch for my cluster that was already in use instead of the newest version. I seemed to get further (the logs above) with this approach that when I was trying the new version of Elasticsearch. With the new version, I got errors in the Elasticsearch and Kibana activities of ECE.

How can I diagnose this and fix ECE so I can create more clusters? Is the 95% root volume a problem even though the /mnt/data is only 1% full?

-Camilo

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 18, 2020, 11:14am UTC](https://discuss.elastic.co/t/failed-to-detect-running-cluster-instance-was-not-detected-as-running-in-time/254257/2 "2020-11-18T11:14:33Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.