# Elasticsearch 1.0.0	 Service Unavailable

**URL:** https://discuss.elastic.co/t/elasticsearch-1-0-0-service-unavailable/87361
**Category:** Elasticsearch
**Created:** [May 28, 2017, 12:29pm UTC](https://discuss.elastic.co/t/elasticsearch-1-0-0-service-unavailable/87361 "2017-05-28T12:29:56Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![rsthakur83](https://avatars.discourse-cdn.com/v4/letter/r/ce7236/32.png) [@rsthakur83](https://discuss.elastic.co/u/rsthakur83)
#### Post date: [May 28, 2017, 12:29pm UTC](https://discuss.elastic.co/t/elasticsearch-1-0-0-service-unavailable/87361/1 "2017-05-28T12:29:56Z")

</div>

Hi ,

I am running elastic search kibana on kubernetes platform and able to access the kibana dashboard  
but only error is appearing saying "elasticsearch 1.0.0 Service Unavailable" so can you please suggest the cause for this problem .

I have run the query from kibana pod/container to elastic search container and it is working fine. Below is the output.

root@kibana-logging-3636129189-swz70:/# curl -X GET [http://elasticsearch-logging:9200](http://elasticsearch-logging:9200)  
{  
"name" : "Caregiver",  
"cluster\_name" : "kubernetes-logging",  
"cluster\_uuid" : "_na_",  
"version" : {  
"number" : "2.4.1",  
"build\_hash" : "c67dc32e24162035d18d6fe1e952c4cbcbe79d16",  
"build\_timestamp" : "2016-09-27T18:57:55Z",  
"build\_snapshot" : false,  
"lucene\_version" : "5.5.2"  
},  
"tagline" : "You Know, for Search"  
}  
root@kibana-logging-3636129189-swz70:/#

Elasticsearch configuration:

root@kibana-logging-3636129189-swz70:/# cat /opt/kibana/config/kibana.yml.org

# Kibana is served by a back end server. This controls which port to use.

# server.port: 5601

# The host to bind the server to.

# server.host: "0.0.0.0"

# If you are running kibana behind a proxy, and want to mount it at a path,

# specify that path here. The basePath can't end in a slash.

# server.basePath: ""

# The maximum payload size in bytes on incoming server requests.

# server.maxPayloadBytes: 1048576

# The Elasticsearch instance to use for all your queries.

elasticsearch.url: '[http://elasticsearch-logging:9200](http://elasticsearch-logging:9200)'

# preserve\_elasticsearch\_host true will send the hostname specified in `elasticsearch`. If you set it to false,

# then the host you use to connect to _this_ Kibana instance will be sent.

# elasticsearch.preserveHost: true

# Kibana uses an index in Elasticsearch to store saved searches, visualizations

# and dashboards. It will create a new index if it doesn't already exist.

# kibana.index: ".kibana"

# The default application to load.

# kibana.defaultAppId: "discover"

# If your Elasticsearch is protected with basic auth, these are the user credentials

# used by the Kibana server to perform maintenance on the kibana\_index at startup. Your Kibana

# users will still need to authenticate with Elasticsearch (which is proxied through

# the Kibana server)

# elasticsearch.username: "user"

# elasticsearch.password: "pass"

# SSL for outgoing requests from the Kibana Server to the browser (PEM formatted)

# server.ssl.cert: /path/to/your/server.crt

# server.ssl.key: /path/to/your/server.key

# Optional setting to validate that your Elasticsearch backend uses the same key files (PEM formatted)

# elasticsearch.ssl.cert: /path/to/your/client.crt

# elasticsearch.ssl.key: /path/to/your/client.key

# If you need to provide a CA certificate for your Elasticsearch instance, put

# the path of the pem file here.

# [elasticsearch.ssl.ca](http://elasticsearch.ssl.ca): /path/to/your/CA.pem

# Set to false to have a complete disregard for the validity of the SSL

# certificate.

# elasticsearch.ssl.verify: true

# Time in milliseconds to wait for elasticsearch to respond to pings, defaults to

# request\_timeout setting

# elasticsearch.pingTimeout: 1500

# Time in milliseconds to wait for responses from the back end or elasticsearch.

# This must be \> 0

# elasticsearch.requestTimeout: 30000

# Header names and values that are sent to Elasticsearch. Any custom headers cannot be overwritten

# by client-side headers.

# elasticsearch.customHeaders: {}

# Time in milliseconds for Elasticsearch to wait for responses from shards.

# Set to 0 to disable.

# elasticsearch.shardTimeout: 0

# Time in milliseconds to wait for Elasticsearch at Kibana startup before retrying

# elasticsearch.startupTimeout: 5000

# Set the path to where you would like the process id file to be created.

# pid.file: /var/run/kibana.pid

# If you would like to send the log output to a file you can set the path below.

# logging.dest: stdout

# Set this to true to suppress all logging output.

# logging.silent: false

# Set this to true to suppress all logging output except for error messages.

# logging.quiet: false

# Set this to true to log all events, including system usage information and all requests.

# logging.verbose: false

root@kibana-logging-3636129189-swz70:/#

elasticsearch configuration;

root@elasticsearch-logging-d6rf7:/# cat /elasticsearch/config/elasticsearch.yml  
[cluster.name](http://cluster.name): kubernetes-logging

node.master: ${NODE\_MASTER}  
node.data: ${NODE\_DATA}

transport.tcp.port: ${TRANSPORT\_PORT}  
http.port: ${HTTP\_PORT}

path.data: /data

network.host: 0.0.0.0

discovery.zen.minimum\_master\_nodes: ${MINIMUM\_MASTER\_NODES}  
discovery.zen.ping.multicast.enabled: false  
root@elasticsearch-logging-d6rf7:/#

---

<div class="post-metadata">

### Author: ![rsthakur83](https://avatars.discourse-cdn.com/v4/letter/r/ce7236/32.png) [@rsthakur83](https://discuss.elastic.co/u/rsthakur83)
#### Post date: [May 28, 2017, 12:39pm UTC](https://discuss.elastic.co/t/elasticsearch-1-0-0-service-unavailable/87361/2 "2017-05-28T12:39:30Z")

</div>

For your information initially it is saying " elasticsearch 1.0.0 Unable to connect to Elasticsearch at [http://elasticsearch-logging:9200](http://elasticsearch-logging:9200)." and then showing "service unavailable" but curl is working fine from kibana to the elastic search as i have in above comment .

---

<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: [May 29, 2017, 3:53am UTC](https://discuss.elastic.co/t/elasticsearch-1-0-0-service-unavailable/87361/3 "2017-05-29T03:53:11Z")

</div>

You really need to upgrade. 1.0.0 is EOL

---

<div class="post-metadata">

### Author: ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [May 29, 2017, 5:07am UTC](https://discuss.elastic.co/t/elasticsearch-1-0-0-service-unavailable/87361/4 "2017-05-29T05:07:17Z")

</div>

> [@warkolm](#):
>
> You really need to upgrade. 1.0.0 is EOL

Well. In a trace it's written 2.4.1

Not sure what to think 🙂

Please format your code using `</>` icon as explained in [this guide](https://discuss.elastic.co/t/about-the-elasticsearch-category/21). It will make your post more readable.

Or use markdown style like:

````
```
CODE
```

````

---

<div class="post-metadata">

### Author: ![rsthakur83](https://avatars.discourse-cdn.com/v4/letter/r/ce7236/32.png) [@rsthakur83](https://discuss.elastic.co/u/rsthakur83)
#### Post date: [May 29, 2017, 12:50pm UTC](https://discuss.elastic.co/t/elasticsearch-1-0-0-service-unavailable/87361/5 "2017-05-29T12:50:23Z")

</div>

Thanks Warkolm Yes with the latest version it start working .

Thanks once again.

Cheers!!!!

---

<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: [June 26, 2017, 12:50pm UTC](https://discuss.elastic.co/t/elasticsearch-1-0-0-service-unavailable/87361/6 "2017-06-26T12:50:29Z")

</div>

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