# Elasticsearch: Service Unavailable in Kibana 4.3

**URL:** <https://discuss.elastic.co/t/elasticsearch-service-unavailable-in-kibana-4-3/36589>\
**Category:** Kibana\
**Created:** [December 8, 2015, 12:03am UTC](https://discuss.elastic.co/t/elasticsearch-service-unavailable-in-kibana-4-3/36589 "2015-12-08T00:03:35Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sdsunjay](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sdsunjay/32/6469_2.png) [@sdsunjay](https://discuss.elastic.co/u/sdsunjay)\
**Post date:** [December 8, 2015, 12:03am UTC](https://discuss.elastic.co/t/elasticsearch-service-unavailable-in-kibana-4-3/36589/1 "2015-12-08T00:03:35Z")

</div>

I'm running 4 instances of Elasticsearch 2.1. 1 of the instances, named "superman\_172\_31\_5\_65", runs with Kibana 4.3 (Apache is the proxy) and has node.data and node.master set to false. Whenever I start Kibana I get the "Service Unavailble" for Elasticsearch. Digging into /var/log/elasticsearch we see

[2015-12-07 23:59:34,242][WARN][discovery.zen] [superman\_172\_31\_5\_65] master left (reason = transport disconnected), current nodes: {{spiderman\_172\_31\_56\_21}{c0XXmfsrQYqXbgsZ705h4g}{172.31.56.21}{172.31.56.21:9300}{max\_local\_storage\_nodes=1, master=true},{ironman\_172\_31\_56\_19}{q1B4AXEsTJie2vPcQCPh-g}{172.31.56.19}{172.31.56.19:9300}{max\_local\_storage\_nodes=1, master=true},{superman\_172\_31\_5\_65}{2UIAOma\_SQO8AN2cUXP-fQ}{172.31.5.65}{172.31.5.65:9300}{max\_local\_storage\_nodes=1, data=false, master=false},}  
[2015-12-07 23:59:34,242][INFO][cluster.service] [superman\_172\_31\_5\_65] removed {{hulk\_172\_31\_56\_20}{5JI2m1n8S1CDok\_6yBwv0w}{172.31.56.20}{172.31.56.20:9300}{max\_local\_storage\_nodes=1, master=true},}, reason: zen-disco-master\_failed ({hulk\_172\_31\_56\_20}{5JI2m1n8S1CDok\_6yBwv0w}{172.31.56.20}{172.31.56.20:9300}{max\_local\_storage\_nodes=1, master=true})  
[2015-12-07 23:59:34,242][WARN][cluster.service] [superman\_172\_31\_5\_65] failed to notify ClusterStateListener  
java.lang.IllegalStateException: master not available when registering auto-generated license  
at org.elasticsearch.license.plugin.core.LicensesService.requestTrialLicense(LicensesService.java:750)  
at org.elasticsearch.license.plugin.core.LicensesService.clusterChanged(LicensesService.java:484)  
at org.elasticsearch.cluster.service.InternalClusterService$UpdateTask.run(InternalClusterService.java:494)  
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:231)  
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:194)  
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)  
at java.lang.Thread.run(Thread.java:745)  
(END)

Essentially it can't contact the master. Any suggestions? Should I set node.master in the other elasticsearch.yml?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [December 8, 2015, 3:18am UTC](https://discuss.elastic.co/t/elasticsearch-service-unavailable-in-kibana-4-3/36589/2 "2015-12-08T03:18:59Z")

</div>

> [@sdsunjay](#):
>
> Should I set node.master in the other elasticsearch.yml?

The other nodes? Yes as someone needs to be the master

---

<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:** [July 6, 2017, 2:07pm UTC](https://discuss.elastic.co/t/elasticsearch-service-unavailable-in-kibana-4-3/36589/3 "2017-07-06T14:07:22Z")

</div>