# Attempted to send event to pipeline

**URL:** <https://discuss.elastic.co/t/attempted-to-send-event-to-pipeline/262124>\
**Category:** Logstash\
**Created:** [January 25, 2021, 3:13pm UTC](https://discuss.elastic.co/t/attempted-to-send-event-to-pipeline/262124 "2021-01-25T15:13:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![gose](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gose/32/37875_2.png) [@gose](https://discuss.elastic.co/u/gose)\
**Post date:** [January 25, 2021, 3:13pm UTC](https://discuss.elastic.co/t/attempted-to-send-event-to-pipeline/262124/1 "2021-01-25T15:13:08Z")

</div>

I'm using Centralized Pipeline Management. I updated a pipeline (pipeline-1) that started sending events to another pipeline (pipeline-2). I didn't have pipeline-2 in my logstash.yml file, so Logstash didn't know about it, resulting in lots of these log messages:

`[2021-01-25T09:02:10,084][WARN][org.logstash.plugins.pipeline.PipelineBus][pipeline-1][eea5877602780] Attempted to send event to 'pipeline-2' but that address was unavailable. Maybe the destination pipeline is down or stopping? Will Retry.`

I then updated pipeline-1 to send events to a working pipeline (pipeline-3), but these log messages persist. Wouldn't Logstash be able to redirect the messages from pipeline-2 over to pipeline-3? Thus flushing this problem scenario?

Or what's an alternative to get out of this scenario?

---

<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:** [February 22, 2021, 3:13pm UTC](https://discuss.elastic.co/t/attempted-to-send-event-to-pipeline/262124/2 "2021-02-22T15:13:34Z")

</div>

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