# Kibana 4.5.1 stop
**URL:** https://discuss.elastic.co/t/kibana-4-5-1-stop/55818
**Category:** Kibana
**Created:** [July 19, 2016, 2:33am UTC](https://discuss.elastic.co/t/kibana-4-5-1-stop/55818 "2016-07-19T02:33:16Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@gabriel\_tessier](https://discuss.elastic.co/u/gabriel_tessier)
#### Post date: [July 19, 2016, 2:33am UTC](https://discuss.elastic.co/t/kibana-4-5-1-stop/55818/1 "2016-07-19T02:33:16Z")
Hi,
We setup a fresh new log server for our Apache logs, everything is fine and we love it 😍
But each morning I need to start by hand kibana i.e `sudo /etc/init.d/kibana start` After start it run correctly during all the day and the day after I need to start it again... Is there some well known problem or something was messed during installation/configuration??
I checked the logs kibana.stderr is empty and the kibana.stdout :
> {"type":"log","@timestamp":"2016-07-14T21:44:06+00:00","tags":["status","plugin:elasticsearch","error"],"pid":23959,"name":"plugin:elasticsearch","state":"red","message":"Status changed from green to red - Request Timeout after 3000ms","prevState":"green","prevMsg":"Kibana index ready"}
> {"type":"log","@timestamp":"2016-07-14T21:44:16+00:00","tags":["status","plugin:elasticsearch","info"],"pid":23959,"name":"plugin:elasticsearch","state":"green","message":"Status changed from red to green - Kibana index ready","prevState":"red","prevMsg":"Request Timeout after 3000ms"}
> {"type":"log","@timestamp":"2016-07-14T21:45:21+00:00","tags":["status","plugin:elasticsearch","error"],"pid":23959,"name":"plugin:elasticsearch","state":"red","message":"Status changed from green to red - Request Timeout after 3000ms","prevState":"green","prevMsg":"Kibana index ready"}
> {"type":"log","@timestamp":"2016-07-14T21:45:47+00:00","tags":["status","plugin:elasticsearch","info"],"pid":23959,"name":"plugin:elasticsearch","state":"green","message":"Status changed from red to green - Kibana index ready","prevState":"red","prevMsg":"Request Timeout after 3000ms"}
> {"type":"log","@timestamp":"2016-07-14T21:46:35+00:00","tags":["status","plugin:elasticsearch","error"],"pid":23959,"name":"plugin:elasticsearch","state":"red","message":"Status changed from green to red - Request Timeout after 3000ms","prevState":"green","prevMsg":"Kibana index ready"}
> {"type":"log","@timestamp":"2016-07-14T21:46:43+00:00","tags":["status","plugin:elasticsearch","info"],"pid":23959,"name":"plugin:elasticsearch","state":"green","message":"Status changed from red to green - Kibana index ready","prevState":"red","prevMsg":"Request Timeout after 3000ms"}
> {"type":"log","@timestamp":"2016-07-19T02:05:07+00:00","tags":["status","plugin:kibana","info"],"pid":12654,"name":"plugin:kibana","state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
Last time I checked I didn't have the timeout, but is it related? Maybe today I'm lucky! 🙂
Thanks for any tips.
---
### Author:  [@gabriel\_tessier](https://discuss.elastic.co/u/gabriel_tessier)
#### Post date: [July 19, 2016, 2:49am UTC](https://discuss.elastic.co/t/kibana-4-5-1-stop/55818/2 "2016-07-19T02:49:59Z")
I reply to myself,
Always find the answer after posting a message... 😭
The problem look similar to the bottom post: Kibana is installed on a CentOs and access a remote Elastic, and not using docker.
>
I'll try their solution and post a re-reply if it's solved.
Sorry for the noise and hope that it can help if somebody don't find the issue or come to discuss first.
---
### Author:  [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)
#### Post date: [July 21, 2016, 5:02pm UTC](https://discuss.elastic.co/t/kibana-4-5-1-stop/55818/3 "2016-07-21T17:02:35Z")
You can also try specifying Node's max-old-space-size when running Kibana
`NODE_OPTIONS="--max-old-space-size=256" ./bin/kibana`
This should lower the memory overhead.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 1:45pm UTC](https://discuss.elastic.co/t/kibana-4-5-1-stop/55818/4 "2017-07-06T13:45:09Z")