# Kibana Service will not start

**URL:** <https://discuss.elastic.co/t/kibana-service-will-not-start/37375>\
**Category:** Kibana\
**Created:** [December 16, 2015, 4:16pm UTC](https://discuss.elastic.co/t/kibana-service-will-not-start/37375 "2015-12-16T16:16:06Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![simroo](https://avatars.discourse-cdn.com/v4/letter/s/f475e1/32.png) [@simroo](https://discuss.elastic.co/u/simroo)\
**Post date:** [December 16, 2015, 4:16pm UTC](https://discuss.elastic.co/t/kibana-service-will-not-start/37375/1 "2015-12-16T16:16:06Z")

</div>

Hello  
I have some problem when trying to connect to my Kibana via localhost on the host.  
I get the error Bad Gateway 502. And the services Kibana will not start at all.  
The logs in /var/log/kibana/kibana.stderr show :

/opt/kibana/bin/../node/bin/node: 1: /opt/kibana/bin/../node/bin/node: cannot create @▒j@@@@: Permission denied  
/opt/kibana/bin/../node/bin/node: 1: /opt/kibana/bin/../node/bin/node:ELF: not found

and im not sure why, i get that it does not have rights but i have dubbelcheck it, and even after running this command :sudo chmod +x /etc/init.d/kibana  
sudo update-rc.d kibana defaults 96 9  
sudo service kibana start  
but still  
ls -la kibana  
-rwxrwxrwx 1 root root 3271 dec 16 17:13 kibana

What iam i missing or doing wrong ?

---

<div class="post-metadata">

**Author:** ![vtst2412](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vtst2412/32/6228_2.png) [@vtst2412](https://discuss.elastic.co/u/vtst2412)\
**Post date:** [December 16, 2015, 5:04pm UTC](https://discuss.elastic.co/t/kibana-service-will-not-start/37375/2 "2015-12-16T17:04:40Z")

</div>

> [@simroo](#):
>
> /opt/kibana/bin/../node/bin/node: 1: /opt/kibana/bin/../node/bin/node: cannot create @▒j@@@@

Is that how the message display in your stderr?  
Run these and report back with the output:

`file /opt/kibana/node/bin/node`  
`java -version`

---

<div class="post-metadata">

**Author:** ![BigFunger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bigfunger/32/7323_2.png) [@BigFunger](https://discuss.elastic.co/u/BigFunger)\
**Post date:** [December 16, 2015, 5:06pm UTC](https://discuss.elastic.co/t/kibana-service-will-not-start/37375/3 "2015-12-16T17:06:22Z")

</div>

What version of Kibana did you download and what OS are you on?

---

<div class="post-metadata">

**Author:** ![simroo](https://avatars.discourse-cdn.com/v4/letter/s/f475e1/32.png) [@simroo](https://discuss.elastic.co/u/simroo)\
**Post date:** [December 16, 2015, 7:23pm UTC](https://discuss.elastic.co/t/kibana-service-will-not-start/37375/4 "2015-12-16T19:23:43Z")

</div>

Hello

file /opt/kibana/node/bin/node  
/opt/kibana/node/bin/node: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.9, not stripped  
@netmanager:/etc/default$ java -version  
java version "1.8.0\_66"  
Java(TM) SE Runtime Environment (build 1.8.0\_66-b17)  
Java HotSpot(TM) Client VM (build 25.66-b17, mixed mode)  
@netmanager:/etc/default$

---

<div class="post-metadata">

**Author:** ![simroo](https://avatars.discourse-cdn.com/v4/letter/s/f475e1/32.png) [@simroo](https://discuss.elastic.co/u/simroo)\
**Post date:** [December 16, 2015, 7:24pm UTC](https://discuss.elastic.co/t/kibana-service-will-not-start/37375/5 "2015-12-16T19:24:33Z")

</div>

/opt/kibana/node/bin/node  
/opt/kibana/node/bin/node: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.9, not stripped

Running debian Linux

---

<div class="post-metadata">

**Author:** ![simroo](https://avatars.discourse-cdn.com/v4/letter/s/f475e1/32.png) [@simroo](https://discuss.elastic.co/u/simroo)\
**Post date:** [December 17, 2015, 7:47am UTC](https://discuss.elastic.co/t/kibana-service-will-not-start/37375/6 "2015-12-17T07:47:36Z")

</div>

Please find the config files if needed

exit $?  
@netmanager:/opt/kibana/config$ cat kibana.yml

# 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: "localhost"

# A value to use as a XSRF token. This token is sent back to the server on each request

# and required if you want to execute requests from other clients (like curl).

# server.xsrf.token: ""

# 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 Elasticsearch instance to use for all your queries.

# elasticsearch.url: "[http://localhost:9200](http://localhost: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: 300000

# 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

---

<div class="post-metadata">

**Author:** ![Joe\_Fleming](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joe_fleming/32/3561_2.png) [@Joe\_Fleming](https://discuss.elastic.co/u/Joe_Fleming)\
**Post date:** [December 17, 2015, 5:47pm UTC](https://discuss.elastic.co/t/kibana-service-will-not-start/37375/7 "2015-12-17T17:47:28Z")

</div>

Looks like you're using the 64-bit version of Kibana, is your system actually 64-bit? Sounds like maybe you need the 32-bit Linux build...

Running `uname -a` will probably give you some insight into which arch you're running on.

---

<div class="post-metadata">

**Author:** ![simroo](https://avatars.discourse-cdn.com/v4/letter/s/f475e1/32.png) [@simroo](https://discuss.elastic.co/u/simroo)\
**Post date:** [December 18, 2015, 7:14am UTC](https://discuss.elastic.co/t/kibana-service-will-not-start/37375/8 "2015-12-18T07:14:29Z")

</div>

Hello  
Here is the output  
$ uname -a  
Linux netmanager 3.2.0-4-686-pae #1 SMP Debian 3.2.68-1+deb7u6 i686 GNU/Linux

---

<div class="post-metadata">

**Author:** ![simroo](https://avatars.discourse-cdn.com/v4/letter/s/f475e1/32.png) [@simroo](https://discuss.elastic.co/u/simroo)\
**Post date:** [December 18, 2015, 9:14am UTC](https://discuss.elastic.co/t/kibana-service-will-not-start/37375/9 "2015-12-18T09:14:58Z")

</div>

So i get that iam running the 64 bit version of Kibana and iam trying to uninstall Kibana but i cant seem to do it.  
sudo apt-get purge kibana . E: Cant find the packge kibana. My debian box cant find the pkg Kibana.  
Where is it placed ?

---

<div class="post-metadata">

**Author:** ![Joe\_Fleming](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joe_fleming/32/3561_2.png) [@Joe\_Fleming](https://discuss.elastic.co/u/Joe_Fleming)\
**Post date:** [December 18, 2015, 4:33pm UTC](https://discuss.elastic.co/t/kibana-service-will-not-start/37375/10 "2015-12-18T16:33:02Z")

</div>

Yeah, so step one is running the 32 bit version instead, as you are on a 32 bit system.

How'd you install it in the first place? We don't have an apt install process as far as I know, so I'm not sure how Kibana ended up in /opt on your system. Perhaps you put it there by hand?

In any event, all you need to do to "uninstall" Kibana is simply remove the `/opt/kibana` path, it doesn't create files anywhere else.

---

<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:06pm UTC](https://discuss.elastic.co/t/kibana-service-will-not-start/37375/11 "2017-07-06T14:06:18Z")

</div>


