# Unable to create index pattern in Kibana after installing X-Pack on Elastic Search Nodes

**URL:** <https://discuss.elastic.co/t/unable-to-create-index-pattern-in-kibana-after-installing-x-pack-on-elastic-search-nodes/140371>\
**Category:** Elasticsearch\
**Created:** [July 17, 2018, 5:05pm UTC](https://discuss.elastic.co/t/unable-to-create-index-pattern-in-kibana-after-installing-x-pack-on-elastic-search-nodes/140371 "2018-07-17T17:05:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ashishmehtta1984](https://avatars.discourse-cdn.com/v4/letter/a/e95f7d/32.png) [@ashishmehtta1984](https://discuss.elastic.co/u/ashishmehtta1984)\
**Post date:** [July 17, 2018, 5:05pm UTC](https://discuss.elastic.co/t/unable-to-create-index-pattern-in-kibana-after-installing-x-pack-on-elastic-search-nodes/140371/1 "2018-07-17T17:05:24Z")

</div>

Hi, I have a 3 Node Elastic Search production cluster on AWS. I installed X-Pack basic on cluster nodes, and after that when I am trying to create index pattern in Kibana, it is erroring out.  
Below are the logs from the Elastic Search node:

[2018-07-17T15:26:49,888][DEBUG][o.e.a.a.c.n.s.TransportNodesStatsAction] [esnode-01] failed to execute on node [HdNCE8niR1m1V2pEMyuBuw]  
org.elasticsearch.transport.ReceiveTimeoutTransportException: [esnode-01][10.0.46.169:9300][cluster:monitor/nodes/stats[n]] request\_id [18367] timed out after [15000ms]  
at org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:934) [elasticsearch-5.4.1.jar:5.4.1]  
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:569) [elasticsearch-5.4.1.jar:5.4.1]  
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0\_161]  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0\_161]  
at java.lang.Thread.run(Thread.java:748) [?:1.8.0\_161]  
[2018-07-17T15:26:49,892][WARN][o.e.a.a.c.n.s.TransportNodesStatsAction] [esnode-01] not accumulating exceptions, excluding exception from response  
org.elasticsearch.action.FailedNodeException: Failed node [HdNCE8niR1m1V2pEMyuBuw]  
at org.elasticsearch.action.support.nodes.TransportNodesAction$AsyncAction.onFailure(TransportNodesAction.java:246) [elasticsearch-5.4.1.jar:5.4.1]  
at org.elasticsearch.action.support.nodes.TransportNodesAction$AsyncAction.access$200(TransportNodesAction.java:160) [elasticsearch-5.4.1.jar:5.4.1]  
at org.elasticsearch.action.support.nodes.TransportNodesAction$AsyncAction$1.handleException(TransportNodesAction.java:218) [elasticsearch-5.4.1.jar:5.4.1]  
at org.elasticsearch.transport.TransportService$ContextRestoreResponseHandler.handleException(TransportService.java:1050) [elasticsearch-5.4.1.jar:5.4.1]  
at org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:933) [elasticsearch-5.4.1.jar:5.4.1]  
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:569) [elasticsearch-5.4.1.jar:5.4.1]  
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0\_161]  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0\_161]  
at java.lang.Thread.run(Thread.java:748) [?:1.8.0\_161]  
Caused by: org.elasticsearch.transport.ReceiveTimeoutTransportException: [esnode-01][10.0.46.169:9300][cluster:monitor/nodes/stats[n]] request\_id [18367] timed out after [15000ms]  
at org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:934) ~[elasticsearch-5.4.1.jar:5.4.1]  
... 4 more

---

<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:** [August 14, 2018, 5:05pm UTC](https://discuss.elastic.co/t/unable-to-create-index-pattern-in-kibana-after-installing-x-pack-on-elastic-search-nodes/140371/2 "2018-08-14T17:05:35Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
