# Kibana Issues with 6.4.1 **URL:** \ **Category:** Kibana\ **Created:** [September 20, 2018, 2:21pm UTC](https://discuss.elastic.co/t/kibana-issues-with-6-4-1/149312 "2018-09-20T14:21:44Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![bn8595](https://avatars.discourse-cdn.com/v4/letter/b/46a35a/32.png) [@bn8595](https://discuss.elastic.co/u/bn8595)\ **Post date:** [September 20, 2018, 2:21pm UTC](https://discuss.elastic.co/t/kibana-issues-with-6-4-1/149312/1 "2018-09-20T14:21:44Z")
Hi I am running below version of the kibana and facing issues. Ubuntu 16.04 elasticsearch/stable,stable,now 6.4.1 all [installed] filebeat/stable,now 6.4.1 amd64 [installed] kibana/stable,now 6.4.1 amd64 [installed] logstash/stable,stable,now 1:6.4.1-1 all [installed] cat jvm.options -Xms1g -Xmx1g -XX:+AlwaysPreTouch -server -Xss1m -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djna.nosys=true -XX:-OmitStackTraceInFastThrow -Dio.netty.noUnsafe=true -Dio.netty.noKeySetOptimization=true -Dio.netty.recycler.maxCapacityPerThread=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Djava.io.tmpdir=${ES\_TMPDIR} -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/lib/elasticsearch -XX:ErrorFile=/var/log/elasticsearch/hs\_err\_pid%p.log 8:-XX:+PrintGCDetails 8:-XX:+PrintGCDateStamps 8:-XX:+PrintTenuringDistribution 8:-XX:+PrintGCApplicationStoppedTime 8:-Xloggc:/var/log/elasticsearch/gc.log 8:-XX:+UseGCLogFileRotation 8:-XX:NumberOfGCLogFiles=32 8:-XX:GCLogFileSize=64m 9-:-Xlog:gc\*,gc+age=trace,safepoint:file=/var/log/elasticsearch/gc.log:utctime,pid,tags:filecount=32,filesize=64m 9-:-Djava.locale.providers=COMPAT 10-:-XX:UseAVX=2 LOGS Kibana.stdout {"type":"response","@timestamp":"2018-09-20T10:13:08Z","tags":[],"pid":9795,"method":"get","statusCode":404,"req":{"url":"/app/kibana","method":"get","headers":{"host":"localhost:5601","cache-control":"max-age=0","upgrade-insecure-requests":"1","user-agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36","accept":"text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,_/_;q=0.8","accept-encoding":"gzip, deflate, br","accept-language":"nl-NL,nl;q=0.9,en-NL;q=0.8,en;q=0.7,en-US;q=0.6","x-forwarded-for":"172.18.4.121","x-forwarded-host":"[test.example.com](http://test.example.com)","x-forwarded-server":"[test.example.com](http://test.example.com)","connection":"Keep-Alive"},"remoteAddress":"127.0.0.1","userAgent":"127.0.0.1"},"res":{"statusCode":404,"responseTime":26,"contentLength":9},"message":"GET /app/kibana 404 26ms - 9.0B"} {"type":"log","@timestamp":"2018-09-20T10:13:16Z","tags":["info","authentication"],"pid":9795,"message":"Authentication attempt failed: [index\_not\_found\_exception] no such index, with { resource.type="index\_expression" & resource.id="\_xpack" & index\_uuid="_na_" & index="\_xpack" }"} {"type":"log","@timestamp":"2018-09-20T10:13:16Z","tags":["license","warning","xpack"],"pid":9795,"message":"License information from the X-Pack plugin could not be obtained from Elasticsearch for the [data] cluster. [invalid\_index\_name\_exception] Invalid index name [_xpack], must not start with '_'., with { index\_uuid="_na_" & index="\_xpack" } :: {"path":"/\_xpack","statusCode":400,"response":"{\"error\":{\"root\_cause\":[{\"type\":\"invalid\_index\_name\_exception\",\"reason\":\"Invalid index name [_xpack], must not start with '_'.\",\"index\_uuid\":\"_na_\",\"index\":\"\_xpack\"}],\"type\":\"invalid\_index\_name\_exception\",\"reason\":\"Invalid index name [_xpack], must not start with '_'.\",\"index\_uuid\":\"_na_\",\"index\":\"\_xpack\"},\"status\":400}"}"} {"type":"response","@timestamp":"2018-09-20T10:13:16Z","tags":[],"pid":9795,"method":"get","statusCode":404,"req":{"url":"/","method":"get","headers":{"host":"localhost:5601","upgrade-insecure-requests":"1","user-agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36","accept":"text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,_/_;q=0.8","accept-encoding":"gzip, deflate, br","accept-language":"nl-NL,nl;q=0.9,en-NL;q=0.8,en;q=0.7,en-US;q=0.6","x-forwarded-for":"172.18.4.121","x-forwarded-host":"[test.example.com](http://test.example.com)","x-forwarded-server":"[test.example.com](http://test.example.com)","connection":"Keep-Alive"},"remoteAddress":"127.0.0.1","userAgent":"127.0.0.1"},"res":{"statusCode":404,"responseTime":12,"contentLength":9},"message":"GET / 404 12ms - 9.0B"} {"type":"log","@timestamp":"2018-09-20T10:13:29Z","tags":["license","warning","xpack"],"pid":9795,"message":"License information from the X-Pack plugin could not be obtained from Elasticsearch for the [data] cluster. [invalid\_index\_name\_exception] Invalid index name [_xpack], must not start with '_'., with { index\_uuid="_na_" & index="\_xpack" } :: {"path":"/\_xpack","statusCode":400,"response":"{\"error\":{\"root\_cause\":[{\"type\":\"invalid\_index\_name\_exception\",\"reason\":\"Invalid index name [_xpack], must not start with '_'.\",\"index\_uuid\":\"_na_\",\"index\":\"\_xpack\"}],\"type\":\"invalid\_index\_name\_exception\",\"reason\":\"Invalid index name [_xpack], must not start with '_'.\",\"index\_uuid\":\"_na_\",\"index\":\"\_xpack\"},\"status\":400}"}"} logstash logs [2018-09-20T16:21:00,378][ERROR][logstash.outputs.elasticsearch] Attempted to send a bulk request to elasticsearch, but no there are no living connections in the connection pool. Perhaps Elasticsearch is unreachable or down? {:error\_message=\>"No Available connections", :class=\>"LogStash::Outputs::ElasticSearch::HttpClient::Pool::NoConnectionAvailableError", :will\_retry\_in\_seconds=\>64} elasticsearch logs [2018-09-20T13:48:25,911][ERROR][o.e.b.ElasticsearchUncaughtExceptionHandler] [] fatal error in thread [elasticsearch[CSCo8TA][write][T#4]], exiting [2018-09-20T13:48:25,912][ERROR][o.e.b.ElasticsearchUncaughtExceptionHandler] [] fatal error in thread [elasticsearch[CSCo8TA][write][T#3]], exiting [2018-09-20T13:55:48,065][WARN][o.e.b.JNANatives] Unable to lock JVM Memory: error=12, reason=Cannot allocate memory [2018-09-20T14:04:36,683][ERROR][o.e.b.ElasticsearchUncaughtExceptionHandler] [] fatal error in thread [elasticsearch[CSCo8TA][refresh][T#2]], exiting [2018-09-20T14:55:11,840][WARN][o.e.b.JNANatives] Unable to lock JVM Memory: error=12, reason=Cannot allocate memory [2018-09-20T15:03:45,266][ERROR][o.e.b.ElasticsearchUncaughtExceptionHandler] [] fatal error in thread [elasticsearch[CSCo8TA][write][T#1]], exiting [2018-09-20T15:03:51,288][ERROR][o.e.b.ElasticsearchUncaughtExceptionHandler] [] fatal error in thread [elasticsearch[CSCo8TA][write][T#2]], exiting [2018-09-20T15:42:56,540][WARN][o.e.b.JNANatives] Unable to lock JVM Memory: error=12, reason=Cannot allocate memory [2018-09-20T15:56:47,719][ERROR][o.e.b.ElasticsearchUncaughtExceptionHandler] [] fatal error in thread [elasticsearch[CSCo8TA][management][T#1]], exiting Ans when I try to access the kibana URL I get below error. Ready plugin:elasticsearch@6.4.1 [cluster\_block\_exception] blocked by: [FORBIDDEN/12/index read-only / allow delete (api)]; Please help to solve. ---
**Author:** ![LeeDr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leedr/32/9289_2.png) [@LeeDr](https://discuss.elastic.co/u/LeeDr)\ **Post date:** [September 28, 2018, 6:18pm UTC](https://discuss.elastic.co/t/kibana-issues-with-6-4-1/149312/2 "2018-09-28T18:18:35Z")
When your Elasticsearch logs show fatal errors, you don't need to bother looking at your Kibana or Logstash logs. They can't work if Elasticsearch isn't working properly. > Unable to lock JVM Memory: error=12, reason=Cannot allocate memory It looks like Elasticsearch can't allocate memory for some reason. What's the hardware specs? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 26, 2018, 6:18pm UTC](https://discuss.elastic.co/t/kibana-issues-with-6-4-1/149312/3 "2018-10-26T18:18:41Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.