# Kibana is not running **URL:** \ **Category:** Kibana\ **Created:** [February 26, 2016, 10:17am UTC](https://discuss.elastic.co/t/kibana-is-not-running/42842 "2016-02-26T10:17:38Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![babeesh](https://avatars.discourse-cdn.com/v4/letter/b/e47c2d/32.png) [@babeesh](https://discuss.elastic.co/u/babeesh)\ **Post date:** [February 26, 2016, 10:17am UTC](https://discuss.elastic.co/t/kibana-is-not-running/42842/1 "2016-02-26T10:17:38Z")
Installed ELK on AWS ubuntu 14.04. ELK versions : Elasticsearch 2.2.x, Logstash 2.2.x, and Kibana 4.4.x. While checking the status elasticsearch and logstash are running, but kibana is not running. I will share the result while running kibana... Last lines of `sudo /opt/kibana/bin/kibana` log [09:51:21.184] [info][**listening**] **Server running at [http://localhost:5601](http://localhost:5601)** log [09:51:51.119] **[error][status][plugin:elasticsearch**] **Status changed from yellow to red** - **Request Timeout after 30000ms** `./bin/kibana` **fs.js:565** **fs.write = function(fd, buffer, offset, length, position, callback) {** ^ **Error: EACCES, permission denied '/opt/kibana/optimize/.babelcache.json**' **at Error (native)** **at Object.fs.openSync (fs.js:500:18)** **at Object.fs.writeFileSync (fs.js:1099:15)** **at save (/opt/kibana/node\_modules/babel-core/lib/api/register/cache.js:35:19)** **at process.\_tickDomainCallback (node.js:381:11)** **at Function.Module.runMain (module.js:503:11)** **at startup (node.js:129:16)** **at node.js:814:3** _Log information_ `tail kibana.stdout` gives the information **{"type":"response","@timestamp":"2016-02-24T11:07:14+00:00","tags":[],"pid":1123,"method":"post","statusCode":200,"req":{"url":"/elasticsearch/logstash-_/\_field\_stats?level=indices","method":"post","headers":{"connection":"upgrade","host":"52.72.247.248","content-length":"178","accept":"application/json, text/plain, /","origin":"[http://52.72.247.248](http://52.72.247.248)","kbn-version":"4.4.1","user-agent":"Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36","content-type":"application/json;charset=UTF-8","referer":"[http://52.72.247.248/app/kibana?","accept-encoding":"gzip](http://52.72.247.248/app/kibana?%22,%22accept-encoding%22:%22gzip), deflate","accept-language":"en-US,en;q=0.8"},"remoteAddress":"172.30.0.28","userAgent":"172.30.0.28","referer":"[http://52.72.247.248/app/kibana?"](http://52.72.247.248/app/kibana?%22)},"res":{"statusCode":200,"responseTime":109,"contentLength":9},"message":"POST /elasticsearch/logstash-_/\_field\_stats?level=indices 200 109ms - 9.0B"}** **{"type":"response","@timestamp":"2016-02-24T11:07:15+00:00","tags":[],"pid":1123,"method":"post","statusCode":200,"req":{"url":"/elasticsearch/\_msearch?timeout=0&ignore\_unavailable=true&preference=1456301293544","method":"post","headers":{"connection":** When I start kibana, it will be running for sometime. But within seconds status will change to not running. I don't understand what is happening behind. Previously logserver was working perfectly, but once I stop and start the aws instance this issue came. Please help me to solve. Thanks ---
**Author:** ![pysysops](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pysysops/32/8106_2.png) [@pysysops](https://discuss.elastic.co/u/pysysops)\ **Post date:** [February 26, 2016, 10:26am UTC](https://discuss.elastic.co/t/kibana-is-not-running/42842/2 "2016-02-26T10:26:22Z")
What are the permissions on the file /opt/kibana/optimize/.babelcache.json? run: ```auto ls -l /opt/kibana/optimize/.babelcache.json ``` and paste the output. Also, why are you running kibana with sudo? Running it with root privileges is probably not ideal. ---
**Author:** ![babeesh](https://avatars.discourse-cdn.com/v4/letter/b/e47c2d/32.png) [@babeesh](https://discuss.elastic.co/u/babeesh)\ **Post date:** [February 26, 2016, 10:34am UTC](https://discuss.elastic.co/t/kibana-is-not-running/42842/3 "2016-02-26T10:34:38Z")
`-rwxr-xr-x 1 kibana kibana 2 Feb 26 10:21 /opt/kibana/optimize/.babelcache.json` Without sudo I got the message I put under `./bin/kibana` So I tried with sudo. Also with sudo , the server status page will load, and it will show as **waiting for plugin elasticsearch** , and after few seconds " **Request Timout**" message will come. ---
**Author:** ![babeesh](https://avatars.discourse-cdn.com/v4/letter/b/e47c2d/32.png) [@babeesh](https://discuss.elastic.co/u/babeesh)\ **Post date:** [February 26, 2016, 10:43am UTC](https://discuss.elastic.co/t/kibana-is-not-running/42842/4 "2016-02-26T10:43:43Z")
I am here sharing elasticsearch log also,,, **at** **org.elasticsearch.index.shard.StoreRecoveryService.recoverFromStore(StoreRecoveryService.java:245)** **at** **org.elasticsearch.index.shard.StoreRecoveryService.access$100(StoreRecoveryService.java:56)** **at** **org.elasticsearch.index.shard.StoreRecoveryService$1.run(StoreRecoveryService.java:129)** **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)** **[2016-02-25 11:19:32,106][WARN][index.engine] [ontash\_prod] [logstash-2016.02.24][2] failed engine [create]** **java.io.IOException: No space left on device** **at sun.nio.ch.FileDispatcherImpl.write0(Native Method)** **at sun.nio.ch.FileDispatcherImubuntu** ---
**Author:** ![pysysops](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pysysops/32/8106_2.png) [@pysysops](https://discuss.elastic.co/u/pysysops)\ **Post date:** [February 26, 2016, 10:46am UTC](https://discuss.elastic.co/t/kibana-is-not-running/42842/5 "2016-02-26T10:46:21Z")
That probably explains it... java.io.IOException: No space left on device Do you have a full disk? ---
**Author:** ![pysysops](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pysysops/32/8106_2.png) [@pysysops](https://discuss.elastic.co/u/pysysops)\ **Post date:** [February 26, 2016, 10:54am UTC](https://discuss.elastic.co/t/kibana-is-not-running/42842/6 "2016-02-26T10:54:46Z")
If you can access the Elasticsearch HTTP API you can delete old indexes with a curl command. Something like: ```auto curl -XDELETE http://localhost:9200/logstash-2016.01.* ``` will remove all logs from January (2016.01). Take a look at [Curator](https://www.elastic.co/guide/en/elasticsearch/client/curator/current/index.html) for managing indexes (deleting or moving old data). ---
**Author:** ![babeesh](https://avatars.discourse-cdn.com/v4/letter/b/e47c2d/32.png) [@babeesh](https://discuss.elastic.co/u/babeesh)\ **Post date:** [February 26, 2016, 11:01am UTC](https://discuss.elastic.co/t/kibana-is-not-running/42842/7 "2016-02-26T11:01:26Z")
I think space issue is the problem, I chkecked instance system information, it gives **System load: 0.0 Memory usage: 2% Processes: 80** **Usage of /:**** 96.2% of 29.39GB Swap usage: 0% Users logged in: 0** So I will try deleting logs as you said. And will let you know the result. ---
**Author:** ![babeesh](https://avatars.discourse-cdn.com/v4/letter/b/e47c2d/32.png) [@babeesh](https://discuss.elastic.co/u/babeesh)\ **Post date:** [February 27, 2016, 5:35am UTC](https://discuss.elastic.co/t/kibana-is-not-running/42842/8 "2016-02-27T05:35:35Z")
I uninstalled elasticsearch. will start from begining. But still system is using 76% of memory. Is there any hidden folders or something which keep old logs?? ---
**Author:** ![pysysops](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pysysops/32/8106_2.png) [@pysysops](https://discuss.elastic.co/u/pysysops)\ **Post date:** [March 1, 2016, 5:30pm UTC](https://discuss.elastic.co/t/kibana-is-not-running/42842/9 "2016-03-01T17:30:49Z")
DId you manage to get to the bottom of this? I'm not sure of your configuration (volumes / data storage configuration). ---
**Author:** ![babeesh](https://avatars.discourse-cdn.com/v4/letter/b/e47c2d/32.png) [@babeesh](https://discuss.elastic.co/u/babeesh)\ **Post date:** [March 2, 2016, 4:09am UTC](https://discuss.elastic.co/t/kibana-is-not-running/42842/10 "2016-03-02T04:09:53Z")
Hi, I removed elasticsearch completely and reinstalled it. Configured elasticsearch and kibana correctly. It works . I am trying to move logs to aws s3 to save disk space in ec2. Thanks ---
**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:00pm UTC](https://discuss.elastic.co/t/kibana-is-not-running/42842/11 "2017-07-06T14:00:37Z")