# X-Pack -"Monitoring: Error 400 Bad Request: Request Timeout after 60000ms"

**URL:** <https://discuss.elastic.co/t/x-pack-monitoring-error-400-bad-request-request-timeout-after-60000ms/84808>\
**Category:** Elasticsearch\
**Created:** [May 6, 2017, 7:00am UTC](https://discuss.elastic.co/t/x-pack-monitoring-error-400-bad-request-request-timeout-after-60000ms/84808 "2017-05-06T07:00:31Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jamesl](https://avatars.discourse-cdn.com/v4/letter/j/c0e974/32.png) [@jamesl](https://discuss.elastic.co/u/jamesl)\
**Post date:** [May 6, 2017, 7:00am UTC](https://discuss.elastic.co/t/x-pack-monitoring-error-400-bad-request-request-timeout-after-60000ms/84808/1 "2017-05-06T07:00:31Z")

</div>

Hi.  
Got a problem where when I click on the monitoring icon I get the dreaded red bar fatal error...

Fatal Error  
Monitoring: Error 400 Bad Request: Request Timeout after 60000ms  
Version: 5.3.1  
Build: 14844

Can anybody please suggest what I can possibly do to make this not happen.

I'm on 5.3.1 ES, LS, Kib, X-Pack.. running on Ubuntu 16.04.

---

<div class="post-metadata">

**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\
**Post date:** [May 7, 2017, 11:19pm UTC](https://discuss.elastic.co/t/x-pack-monitoring-error-400-bad-request-request-timeout-after-60000ms/84808/2 "2017-05-07T23:19:01Z")

</div>

HI James

I will try and reproduce your problem on 5.3.1 build, but in the mean time, can you make sure your ElasticSearch instance is not under heavy load or excessive garbage collection.

In that case , you probably need more resource for you ElasticSearch installation, you can turn up the timeout in the config file, but that will only help so much.

Thanks  
Rashmi

---

<div class="post-metadata">

**Author:** ![jamesl](https://avatars.discourse-cdn.com/v4/letter/j/c0e974/32.png) [@jamesl](https://discuss.elastic.co/u/jamesl)\
**Post date:** [May 11, 2017, 9:30pm UTC](https://discuss.elastic.co/t/x-pack-monitoring-error-400-bad-request-request-timeout-after-60000ms/84808/3 "2017-05-11T21:30:39Z")

</div>

Hi Thanks.

My 2 data nodes have 16GB physical memory.  
Looks like somebody had adjusted the JVM heap size to be 16GB as well!  
I have set this to 12GB and things are behaving much better now.... no crashes.

My ES nodes are are on a vm host that is very low on memory. Will be rectifying that shortly.

Thanks for your help.

---

<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:** [June 8, 2017, 9:37pm UTC](https://discuss.elastic.co/t/x-pack-monitoring-error-400-bad-request-request-timeout-after-60000ms/84808/4 "2017-06-08T21:37:00Z")

</div>

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