# Timeout on /\_cat/indices on a single node **URL:** \ **Category:** Elasticsearch\ **Created:** [October 20, 2016, 5:13pm UTC](https://discuss.elastic.co/t/timeout-on--cat-indices-on-a-single-node/63529 "2016-10-20T17:13:05Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![carrot](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carrot/32/44335_2.png) [@carrot](https://discuss.elastic.co/u/carrot)\ **Post date:** [October 20, 2016, 5:13pm UTC](https://discuss.elastic.co/t/timeout-on--cat-indices-on-a-single-node/63529/1 "2016-10-20T17:13:05Z")
I have a cluster of about 10 data nodes, 5 master nodes and a few client nodes. I've got a single client node that no matter what I do, I can get the cluster state via curl, but not getting any responses back from /\_cat/indices on that node. I re-installed elasticsearch and cleared a bunch of directory. I tried the same install on a different server and worked just fine. How do we debug these kind of issues? The only thing I can see in the logs for each masters is the following : > [2016-10-20 17:11:41,189][WARN][transport] [node0001-master] Transport response handler not found of id [956886] > [2016-10-20 17:11:41,281][WARN][transport] [node0001-master] Transport response handler not found of id [956919] > [2016-10-20 17:11:41,282][WARN][transport] [node0001-master] Transport response handler not found of id [956930] > [2016-10-20 17:11:41,283][WARN][transport] [node0001-master] Transport response handler not found of id [956933] > [2016-10-20 17:11:43,808][WARN][transport] [node0001-master] Transport response handler not found of id [957725] > [ Timeout out query : > [me@client ~]$ curl [http://localhost:9200/\_cat/indices](http://localhost:9200/_cat/indices) -v > > - About to connect() to localhost port 9200 (#0) > - Trying 127.0.0.1... connected > - Connected to localhost (127.0.0.1) port 9200 (#0) > > > GET /\_cat/indices HTTP/1.1 > > User-Agent: curl/7.19.7 (x86\_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.21 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2 > > Host: localhost:9200 > > Accept: _/_ > > ^C Cluster Health : > [me@client ~]$ curl [http://localhost:9200/\_cluster/health?pretty=true](http://localhost:9200/_cluster/health?pretty=true) > { > "cluster\_name" : "elasticsearch", > "status" : "green", > "timed\_out" : false, > "number\_of\_nodes" : 18, > "number\_of\_data\_nodes" : 10, > "active\_primary\_shards" : 156, > "active\_shards" : 312, > "relocating\_shards" : 0, > "initializing\_shards" : 0, > "unassigned\_shards" : 0, > "delayed\_unassigned\_shards" : 0, > "number\_of\_pending\_tasks" : 0, > "number\_of\_in\_flight\_fetch" : 0, > "task\_max\_waiting\_in\_queue\_millis" : 0, > "active\_shards\_percent\_as\_number" : 100.0 > } Thanks, ---
**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:** [October 21, 2016, 10:53pm UTC](https://discuss.elastic.co/t/timeout-on--cat-indices-on-a-single-node/63529/2 "2016-10-21T22:53:04Z")
What version? ---
**Author:** ![carrot](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carrot/32/44335_2.png) [@carrot](https://discuss.elastic.co/u/carrot)\ **Post date:** [October 21, 2016, 11:24pm UTC](https://discuss.elastic.co/t/timeout-on--cat-indices-on-a-single-node/63529/3 "2016-10-21T23:24:48Z")
2.4.0 ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [October 22, 2016, 7:31am UTC](https://discuss.elastic.co/t/timeout-on--cat-indices-on-a-single-node/63529/4 "2016-10-22T07:31:14Z")
Do you have some plugins? Also try to upgrade to 2.4.1 ---
**Author:** ![carrot](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carrot/32/44335_2.png) [@carrot](https://discuss.elastic.co/u/carrot)\ **Post date:** [October 22, 2016, 5:07pm UTC](https://discuss.elastic.co/t/timeout-on--cat-indices-on-a-single-node/63529/5 "2016-10-22T17:07:35Z")
I actually installed 2.4.1 first which had the issue. Then I decided to downgraded to same version as the cluster (2.4.0). Between the installed I cleared all data directories and temp directories. I just don't know why the specific query fails all the time. There is other queries such as /\_cat/count/index that works half the time. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [October 22, 2016, 6:42pm UTC](https://discuss.elastic.co/t/timeout-on--cat-indices-on-a-single-node/63529/6 "2016-10-22T18:42:59Z")
Do you have plugins ? ---
**Author:** ![carrot](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carrot/32/44335_2.png) [@carrot](https://discuss.elastic.co/u/carrot)\ **Post date:** [October 22, 2016, 6:59pm UTC](https://discuss.elastic.co/t/timeout-on--cat-indices-on-a-single-node/63529/7 "2016-10-22T18:59:19Z")
You made me thinking. But no, I only have kibana installed locally as well which kibana has the sense plugin to be able to control via API. For example with count... Works then doesn't... [smalenfa@cdn1cdstats0001 installedPlugins]$ curl [http://localhost:9200/\_cat/count/custom\_ats\_2-2016.10.16](http://localhost:9200/_cat/count/custom_ats_2-2016.10.16) 1477162602 18:56:42 1049713714 [smalenfa@cdn1cdstats0001 installedPlugins]$ curl [http://localhost:9200/\_cat/count/custom\_ats\_2-2016.10.18](http://localhost:9200/_cat/count/custom_ats_2-2016.10.18) ^C [smalenfa@cdn1cdstats0001 installedPlugins]$ curl [http://localhost:9200/\_cat/count/custom\_ats\_2-2016.10.18](http://localhost:9200/_cat/count/custom_ats_2-2016.10.18) ^C [smalenfa@cdn1cdstats0001 installedPlugins]$ curl [http://localhost:9200/\_cat/count/custom\_ats\_2-2016.10.18](http://localhost:9200/_cat/count/custom_ats_2-2016.10.18) ^C [smalenfa@cdn1cdstats0001 installedPlugins]$ curl [http://localhost:9200/\_cat/count/custom\_ats\_2-2016.10.18](http://localhost:9200/_cat/count/custom_ats_2-2016.10.18) 1477162607 18:56:47 779883228 [smalenfa@cdn1cdstats0001 instal How do we debug ES (data) incoming queries or routing? I thought my cluster was too busy, but then it works correctly with 3 other client nodes. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [October 23, 2016, 5:04am UTC](https://discuss.elastic.co/t/timeout-on--cat-indices-on-a-single-node/63529/8 "2016-10-23T05:04:18Z")
Anything in your logs? ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [October 23, 2016, 5:06am UTC](https://discuss.elastic.co/t/timeout-on--cat-indices-on-a-single-node/63529/9 "2016-10-23T05:06:06Z")
Oh and please reinstall 2.4.1. It will remove the error message you mentioned initially. ---
**Author:** ![carrot](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carrot/32/44335_2.png) [@carrot](https://discuss.elastic.co/u/carrot)\ **Post date:** [October 23, 2016, 1:03pm UTC](https://discuss.elastic.co/t/timeout-on--cat-indices-on-a-single-node/63529/10 "2016-10-23T13:03:26Z")
There is actually nothing in the logs at all except the updates from the clusters. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:10pm UTC](https://discuss.elastic.co/t/timeout-on--cat-indices-on-a-single-node/63529/11 "2017-07-05T22:10:20Z")