# Elasticsearch logs

**URL:** <https://discuss.elastic.co/t/elasticsearch-logs/84141>\
**Category:** Elasticsearch\
**Created:** [May 1, 2017, 10:32am UTC](https://discuss.elastic.co/t/elasticsearch-logs/84141 "2017-05-01T10:32:52Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Raj\_Kumar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raj_kumar/32/25420_2.png) [@Raj\_Kumar](https://discuss.elastic.co/u/Raj_Kumar)\
**Post date:** [May 1, 2017, 10:32am UTC](https://discuss.elastic.co/t/elasticsearch-logs/84141/1 "2017-05-01T10:32:52Z")

</div>

Hi All,

I was trying to see the elasticsearch logs and I was able to find these type of logs are loading the server very fastly.

[2017-05-01T12:26:23,993][DEBUG][o.e.a.b.TransportBulkAction] [casa\_1] failed to execute pipeline [xpack\_monitoring\_2] for document [.monitoring-data-2/logstash/37cd9d97-fcff-4042-925e-b2467af2b695]  
java.lang.IllegalArgumentException: pipeline with id [xpack\_monitoring\_2] does not exist  
at org.elasticsearch.ingest.PipelineExecutionService.getPipeline(PipelineExecutionService.java:193) ~[elasticsearch-5.3.1.jar:5.3.1]  
at org.elasticsearch.ingest.PipelineExecutionService.access$100(PipelineExecutionService.java:41) ~[elasticsearch-5.3.1.jar:5.3.1]  
at org.elasticsearch.ingest.PipelineExecutionService$2.doRun(PipelineExecutionService.java:88) [elasticsearch-5.3.1.jar:5.3.1]  
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:638) [elasticsearch-5.3.1.jar:5.3.1]  
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) [elasticsearch-5.3.1.jar:5.3.1]  
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0\_111]  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0\_111]  
at java.lang.Thread.run(Thread.java:745) [?:1.8.0\_111]

Am afraid this could kill the server,any help or suggestion how to fix this issue .  
Would be really helpful.

Thanks in advance,  
Raj

---

<div class="post-metadata">

**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\
**Post date:** [May 1, 2017, 4:20pm UTC](https://discuss.elastic.co/t/elasticsearch-logs/84141/2 "2017-05-01T16:20:40Z")

</div>

This usually happens when you've disable ingest on a cluster to which you are sending monitoring data. Monitoring prefers that that stay on. If you set `use_ingest` to `false` on the exporting system it _ought_ to work though.

---

<div class="post-metadata">

**Author:** ![Raj\_Kumar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raj_kumar/32/25420_2.png) [@Raj\_Kumar](https://discuss.elastic.co/u/Raj_Kumar)\
**Post date:** [May 1, 2017, 8:40pm UTC](https://discuss.elastic.co/t/elasticsearch-logs/84141/3 "2017-05-01T20:40:03Z")

</div>

Thank you Nik, very much for the info , it worked 🙂

---

<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:** [May 29, 2017, 8:47pm UTC](https://discuss.elastic.co/t/elasticsearch-logs/84141/4 "2017-05-29T20:47:41Z")

</div>

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