# Kibana 3 – Not Displaying Historical Logs **URL:** \ **Category:** Kibana\ **Created:** [August 5, 2015, 11:36am UTC](https://discuss.elastic.co/t/kibana-3-not-displaying-historical-logs/26883 "2015-08-05T11:36:36Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Ben19](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ben19/32/3745_2.png) [@Ben19](https://discuss.elastic.co/u/Ben19)\ **Post date:** [August 5, 2015, 11:36am UTC](https://discuss.elastic.co/t/kibana-3-not-displaying-historical-logs/26883/1 "2015-08-05T11:36:36Z")
Hello, I have an ELK server with the below stack versions: K: 3.1.2 E: 1.4.3 L: 1.4.2 I have an issue where I cannot view historical logs in Kibana, this seems to be random as I was able to view the data on that date in the past. I have indices at /var/lib/elasticsearch/elasticsearch/nodes/0/indices right back to 01/09/2015 (logstash-2015.01.09) and all the way down to todays date, where I can only see the last weeks’ worth of logs. Where am I best starting looking to resolve this problem? I can see all my index names via curl [http://localhost:9200/\_aliases?pretty=1](http://localhost:9200/_aliases?pretty=1) Many thanks EDIT: I had two nodes that did this and I was able to resolve it on one. It was receiving the below in the /var/log/elasticsearch/elasticsearch.log: [Black Tarantula] Caught exception while handling client http traffic, closing connection [id: 0xdc2765c4, /127.0.0.1:57760 =\> /127.0.0.1:9200] org.elasticsearch.common.netty.handler.codec.frame.TooLongFrameException: An HTTP line is larger than 4096 bytes. I was able to edit the required line in the elasticsearch.yml but it didn’t resolve it for the other node, this one no longer receives the above URL issue but receives the below now: [DEBUG][action.search.type] [Feron] All shards failed for phase: [query] ---
**Author:** ![Ben19](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ben19/32/3745_2.png) [@Ben19](https://discuss.elastic.co/u/Ben19)\ **Post date:** [August 6, 2015, 2:54pm UTC](https://discuss.elastic.co/t/kibana-3-not-displaying-historical-logs/26883/2 "2015-08-06T14:54:30Z")
Can anyone recomend a solution? ---
**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:** [August 7, 2015, 7:56am UTC](https://discuss.elastic.co/t/kibana-3-not-displaying-historical-logs/26883/3 "2015-08-07T07:56:54Z")
There should be something in the logs to help you figure this out. Also, you should really upgrade, you've lagging behind current releases 🙂 ---
**Author:** ![Ben19](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ben19/32/3745_2.png) [@Ben19](https://discuss.elastic.co/u/Ben19)\ **Post date:** [August 7, 2015, 8:31am UTC](https://discuss.elastic.co/t/kibana-3-not-displaying-historical-logs/26883/4 "2015-08-07T08:31:30Z")
Yeah I have a build that runs the latest versions of all stack apps, just this one is production right now though. I’m looking through google trying to find some knowledge so just posting here too to see if an answer can be given quicker. ---
**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:** [August 7, 2015, 8:33am UTC](https://discuss.elastic.co/t/kibana-3-not-displaying-historical-logs/26883/5 "2015-08-07T08:33:13Z")
There should be more in your logs. Maybe if you can gist/pastebin/etc them we can have a look? ---
**Author:** ![Ben19](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ben19/32/3745_2.png) [@Ben19](https://discuss.elastic.co/u/Ben19)\ **Post date:** [August 10, 2015, 2:02pm UTC](https://discuss.elastic.co/t/kibana-3-not-displaying-historical-logs/26883/6 "2015-08-10T14:02:28Z")
My issues relates to a large number of shards not being allocated, for example: logstash-2015.06.13 4 p UNASSIGNED logstash-2015.06.13 4 r UNASSIGNED logstash-2015.06.14 2 p UNASSIGNED logstash-2015.06.14 2 r UNASSIGNED logstash-2015.06.14 0 p UNASSIGNED logstash-2015.06.14 0 r UNASSIGNED logstash-2015.06.14 3 p UNASSIGNED logstash-2015.06.14 3 r UNASSIGNED not sure exactly why but I’ve been trying to re-allocate them but I’m running into this issue below: [NO(shard cannot be allocated on same node [gMnx09\_-TMqDfLJe5NkJWQ] it already exists on). So I can’t re-assign onto the same node obviously but how do I change the node? ---
**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:** [August 10, 2015, 10:51pm UTC](https://discuss.elastic.co/t/kibana-3-not-displaying-historical-logs/26883/7 "2015-08-10T22:51:43Z")
You mentioned you had two nodes, do you only have one now? ---
**Author:** ![Ben19](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ben19/32/3745_2.png) [@Ben19](https://discuss.elastic.co/u/Ben19)\ **Post date:** [August 11, 2015, 8:22am UTC](https://discuss.elastic.co/t/kibana-3-not-displaying-historical-logs/26883/8 "2015-08-11T08:22:50Z")
I have only one cluster with the issue, the other one was fixed as the issue was something else. ---
**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:15pm UTC](https://discuss.elastic.co/t/kibana-3-not-displaying-historical-logs/26883/9 "2017-07-06T14:15:04Z")
Closed on July 6, 2017, 2:15pm UTC