# The client site is going down due to after integrating Elastic search

**URL:** <https://discuss.elastic.co/t/the-client-site-is-going-down-due-to-after-integrating-elastic-search/152511>\
**Category:** Elasticsearch\
**Created:** [October 15, 2018, 2:29pm UTC](https://discuss.elastic.co/t/the-client-site-is-going-down-due-to-after-integrating-elastic-search/152511 "2018-10-15T14:29:45Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ali\_Nouman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ali_nouman/32/45644_2.png) [@Ali\_Nouman](https://discuss.elastic.co/u/Ali_Nouman)\
**Post date:** [October 15, 2018, 2:29pm UTC](https://discuss.elastic.co/t/the-client-site-is-going-down-due-to-after-integrating-elastic-search/152511/1 "2018-10-15T14:29:46Z")

</div>

The cpu goes high the drupal site code is one Aws ec2 server and elastic search on another ec2 server. Can some one point me where i can check the logs what can be the issue?

---

<div class="post-metadata">

**Author:** ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)\
**Post date:** [October 16, 2018, 3:13am UTC](https://discuss.elastic.co/t/the-client-site-is-going-down-due-to-after-integrating-elastic-search/152511/2 "2018-10-16T03:13:27Z")

</div>

The location of the log files depends on how you installed and configured elasticsearch.

The _likely_ places are:

- A `logs/` directory inside your Elasticsearch installation directory (if you installed from .zip or .tgz)
- The `/var/log/elasticsearch` directory (if you installed from .deb or .rpm)
- `docker logs` if you are running in docker (with the official docker image)

But it's possible to override any of those with configuration options.

---

<div class="post-metadata">

**Author:** ![Ali\_Nouman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ali_nouman/32/45644_2.png) [@Ali\_Nouman](https://discuss.elastic.co/u/Ali_Nouman)\
**Post date:** [October 18, 2018, 6:07am UTC](https://discuss.elastic.co/t/the-client-site-is-going-down-due-to-after-integrating-elastic-search/152511/3 "2018-10-18T06:07:30Z")

</div>

I'm getting this log in entry as crash

[2018-10-18T04:42:21,518][WARN][o.e.m.j.JvmGcMonitorService] [beppyc\_] [gc][young][241875][1751] duration [1.4m], collections [1]/[1.7m], total [1.4m]/[1.7m], memory [509.7mb]-\>[445.2mb]/[1015.6mb], all\_pools {[young] [64.3mb]-\>[3.2mb]/[66.5mb]}{[survivor] [8mb]-\>[5.1mb]/[8.3mb]}{[old] [439.2mb]-\>[439.3mb]/[940.8mb]}  
[2018-10-18T04:42:21,524][WARN][o.e.m.j.JvmGcMonitorService] [beppyc\_] [gc][241875] overhead, spent [1.4m] collecting in the last [1.7m]

Do you have any idea what the error could be?

---

<div class="post-metadata">

**Author:** ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)\
**Post date:** [October 18, 2018, 6:45am UTC](https://discuss.elastic.co/t/the-client-site-is-going-down-due-to-after-integrating-elastic-search/152511/4 "2018-10-18T06:45:43Z")

</div>

That is just a warning - it is not the cause of your crash.

You need to find the main elasticsearch logs.

---

<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:** [November 15, 2018, 6:45am UTC](https://discuss.elastic.co/t/the-client-site-is-going-down-due-to-after-integrating-elastic-search/152511/5 "2018-11-15T06:45:44Z")

</div>

Closed on November 15, 2018, 6:45am UTC

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