# Starting Kibana as a RHEL service failing

**URL:** <https://discuss.elastic.co/t/starting-kibana-as-a-rhel-service-failing/557>\
**Category:** Kibana\
**Created:** [May 12, 2015, 1:47pm UTC](https://discuss.elastic.co/t/starting-kibana-as-a-rhel-service-failing/557 "2015-05-12T13:47:08Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pedalair](https://avatars.discourse-cdn.com/v4/letter/p/9e8a1a/32.png) [@Pedalair](https://discuss.elastic.co/u/Pedalair)\
**Post date:** [May 12, 2015, 1:47pm UTC](https://discuss.elastic.co/t/starting-kibana-as-a-rhel-service-failing/557/1 "2015-05-12T13:47:08Z")

</div>

Hi

I have Kibana installed and running on RHEL6 and am connecting to an ES client node on the same machine. I have created an entry in /etc/init.d/ to start Kibana as a service (including a check to ensure ES is communicating before starting) and when i am logged in and use 'sudo service kibana start' it works fine.

When the box is rebooted then the Kibana start up fails (ES succeeds) with the following error.  
{"@timestamp":"2015-05-12T13:03:24.463Z","level":"fatal","message":"Service Unavailable","node\_env":"production","error":{"message":"Service Unavailable","name":"Error","stack":"Error: Service Unavailable\n at respond (/opt/kibana/src/node\_modules/elasticsearch/src/lib/transport.js:235:15)\n at checkRespForFailure (/opt/kibana/src/node\_modules/elasticsearch/src/lib/transport.js:203:7)\n at HttpConnector. (/opt/kibana/src/node\_modules/elasticsearch/src/lib/connectors/http.js:156:7)\n at IncomingMessage.bound (/opt/kibana/src/node\_modules/elasticsearch/node\_modules/lodash-node/modern/internals/baseBind.js:56:17)\n at IncomingMessage.emit (events.js:117:20)\n at \_stream\_readable.js:944:16\n at process.\_tickCallback (node.js:442:13)\n"}}

---

<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 12, 2015, 9:47pm UTC](https://discuss.elastic.co/t/starting-kibana-as-a-rhel-service-failing/557/2 "2015-05-12T21:47:36Z")

</div>

That looks like it cannot connect to ES for some reason.  
Are you sure ES starts up?

---

<div class="post-metadata">

**Author:** ![Pedalair](https://avatars.discourse-cdn.com/v4/letter/p/9e8a1a/32.png) [@Pedalair](https://discuss.elastic.co/u/Pedalair)\
**Post date:** [May 13, 2015, 10:42am UTC](https://discuss.elastic.co/t/starting-kibana-as-a-rhel-service-failing/557/3 "2015-05-13T10:42:51Z")

</div>

ES was starting up ok - a colleague helped debug and it seems like the script i had to detect when it had come up was not being executed properly. This must have interfered with the Kibana start during the boot initiation, although i think the logon was also relevant as it ran ok when being manually started.

---

<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:19pm UTC](https://discuss.elastic.co/t/starting-kibana-as-a-rhel-service-failing/557/4 "2017-07-06T14:19:37Z")

</div>