# Terminal blocked on \[2020-01-24T15:37:25,971\]\[INFO \]\[o.e.c.r.a.AllocationService\] \[LAPTOP-TRA6NOPS\] Cluster health status changed from \[RED\] to \[GREEN\] (reason: \[shards started \[\[.kibana\_task\_manager\_1\]\[0\], \[.kibana\_1\]\[0\]\]\]) **URL:** \ **Category:** Elasticsearch\ **Created:** [January 24, 2020, 2:51pm UTC](https://discuss.elastic.co/t/terminal-blocked-on-2020-01-24t1525-971-info-o-e-c-r-a-allocationservice-laptop-tra6nops-cluster-health-status-changed-from-red-to-green-reason-shards-started-kibana-task-manager-1-0-kibana-1-0/216446 "2020-01-24T14:51:12Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![pierrejutard](https://avatars.discourse-cdn.com/v4/letter/p/c5a1d2/32.png) [@pierrejutard](https://discuss.elastic.co/u/pierrejutard)\ **Post date:** [January 24, 2020, 2:51pm UTC](https://discuss.elastic.co/t/terminal-blocked-on-2020-01-24t1525-971-info-o-e-c-r-a-allocationservice-laptop-tra6nops-cluster-health-status-changed-from-red-to-green-reason-shards-started-kibana-task-manager-1-0-kibana-1-0/216446/1 "2020-01-24T14:51:12Z")
Hello, i just set up elastic search 7.5.2 on my computer and when runnning on the terminal comand elastic search on windows the terminal stops at this sentence: [2020-01-24T15:37:25,971][INFO][o.e.c.r.a.AllocationService] [LAPTOP-TRA6NOPS] Cluster health status changed from [RED] to [GREEN] (reason: [shards started [[.kibana\_task\_manager\_1][0], [.kibana\_1][0]]]). In the meantime, i checked on a web page if ES was running and this is what i get: with { "name" : "LAPTOP-TRA6NOPS", "cluster\_name" : "elasticsearch", "cluster\_uuid" : "z7EChdjwQD2-j9s73mtUBA", "version" : { "number" : "7.5.2", "build\_flavor" : "default", "build\_type" : "zip", "build\_hash" : "8bec50e1e0ad29dad5653712cf3bb580cd1afcdf", "build\_date" : "2020-01-15T12:11:52.313576Z", "build\_snapshot" : false, "lucene\_version" : "8.3.0", "minimum\_wire\_compatibility\_version" : "6.8.0", "minimum\_index\_compatibility\_version" : "6.0.0-beta1" }, "tagline" : "You Know, for Search" } When checking the indices with curl "localhost:9200/\_cat/indices?v": health status index uuid pri rep docs.count docs.deleted store.size pri.store.size green open .kibana\_task\_manager\_1 rfLqgEEWTQuWpFcxYr4xLg 1 0 0 0 283b 283b green open .kibana\_1 zDVSq4pGTjGKvtPEPXh9Bg 1 0 0 0 283b 283b Can anyone can help me please? Best regards Pierre Jutard ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [January 24, 2020, 2:53pm UTC](https://discuss.elastic.co/t/terminal-blocked-on-2020-01-24t1525-971-info-o-e-c-r-a-allocationservice-laptop-tra6nops-cluster-health-status-changed-from-red-to-green-reason-shards-started-kibana-task-manager-1-0-kibana-1-0/216446/2 "2020-01-24T14:53:37Z")
Everything you describe is normal behaviour for a healthy, happy cluster. Can you explain what help you need? ---
**Author:** ![pierrejutard](https://avatars.discourse-cdn.com/v4/letter/p/c5a1d2/32.png) [@pierrejutard](https://discuss.elastic.co/u/pierrejutard)\ **Post date:** [January 24, 2020, 3:19pm UTC](https://discuss.elastic.co/t/terminal-blocked-on-2020-01-24t1525-971-info-o-e-c-r-a-allocationservice-laptop-tra6nops-cluster-health-status-changed-from-red-to-green-reason-shards-started-kibana-task-manager-1-0-kibana-1-0/216446/3 "2020-01-24T15:19:09Z")
Is it normal that when running ES, the terminal stays in the line i mentionned? BR PJ ---
**Author:** ![pierrejutard](https://avatars.discourse-cdn.com/v4/letter/p/c5a1d2/32.png) [@pierrejutard](https://discuss.elastic.co/u/pierrejutard)\ **Post date:** [January 24, 2020, 3:21pm UTC](https://discuss.elastic.co/t/terminal-blocked-on-2020-01-24t1525-971-info-o-e-c-r-a-allocationservice-laptop-tra6nops-cluster-health-status-changed-from-red-to-green-reason-shards-started-kibana-task-manager-1-0-kibana-1-0/216446/4 "2020-01-24T15:21:10Z")
Because when runnning kibana in the meantime, it stays on this line: log [15:19:49.007] [warning][migrations] Another Kibana instance appears to be migrating the index. Waiting for that migration to complete. If no other Kibana instance is attempting migrations, you can get past this message by deleting index .kibana\_task\_manager\_1 and restarting Kibana. BR PJ ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [January 24, 2020, 4:19pm UTC](https://discuss.elastic.co/t/terminal-blocked-on-2020-01-24t1525-971-info-o-e-c-r-a-allocationservice-laptop-tra6nops-cluster-health-status-changed-from-red-to-green-reason-shards-started-kibana-task-manager-1-0-kibana-1-0/216446/5 "2020-01-24T16:19:25Z")
The Kibana question looks like [https://github.com/elastic/kibana/issues/25464](https://github.com/elastic/kibana/issues/25464) but it might be best to take that question to the Kibana forum instead. Everything looks good from the Elasticsearch side. ---
**Author:** ![pierrejutard](https://avatars.discourse-cdn.com/v4/letter/p/c5a1d2/32.png) [@pierrejutard](https://discuss.elastic.co/u/pierrejutard)\ **Post date:** [January 24, 2020, 7:12pm UTC](https://discuss.elastic.co/t/terminal-blocked-on-2020-01-24t1525-971-info-o-e-c-r-a-allocationservice-laptop-tra6nops-cluster-health-status-changed-from-red-to-green-reason-shards-started-kibana-task-manager-1-0-kibana-1-0/216446/6 "2020-01-24T19:12:48Z")
Alright thanks for your quick help david! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 21, 2020, 7:12pm UTC](https://discuss.elastic.co/t/terminal-blocked-on-2020-01-24t1525-971-info-o-e-c-r-a-allocationservice-laptop-tra6nops-cluster-health-status-changed-from-red-to-green-reason-shards-started-kibana-task-manager-1-0-kibana-1-0/216446/7 "2020-02-21T19:12:49Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.