# After using pipeline to pipeline comunication in pipelines.yml, the other pipelines are not working

**URL:** https://discuss.elastic.co/t/after-using-pipeline-to-pipeline-comunication-in-pipelines-yml-the-other-pipelines-are-not-working/287455
**Category:** Logstash
**Created:** [October 22, 2021, 6:27pm UTC](https://discuss.elastic.co/t/after-using-pipeline-to-pipeline-comunication-in-pipelines-yml-the-other-pipelines-are-not-working/287455 "2021-10-22T18:27:53Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![ElasticLiver](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/elasticliver/32/64869_2.png) [@ElasticLiver](https://discuss.elastic.co/u/ElasticLiver)
#### Post date: [October 22, 2021, 6:27pm UTC](https://discuss.elastic.co/t/after-using-pipeline-to-pipeline-comunication-in-pipelines-yml-the-other-pipelines-are-not-working/287455/1 "2021-10-22T18:27:53Z")

</div>

Hi, when I use pipeline to pipeline comunication in pipelines.yml the other pipelines in the file stop working.

if I comment those lines the other pipelines start to work.  
this is my pipelines.yml, the first pipeline sends data to following four. the other are JDBC pipelines.

```auto
- pipeline.id: fork-filebeat
  path.config: "/etc/logstash/conf.d/filebeat/fork-logs.conf"

- pipeline.id: diskfs-filebeat
  path.config: "/etc/logstash/conf.d/filebeat/discos-fs.conf"

- pipeline.id: sap-filebeat
  path.config: "/etc/logstash/conf.d/filebeat/sap.conf"

- pipeline.id: diskfs-filebeat-quebec
  path.config: "/etc/logstash/conf.d/filebeat/discos-fs-quebec.conf"

- pipeline.id: diskfs-filebeat-alpha
  path.config: "/etc/logstash/conf.d/filebeat/discos-fs-alpha.conf"

- pipeline.id: component
  path.config: "/etc/logstash/conf.d/component.conf"

- pipeline.id: interface
  path.config: "/etc/logstash/conf.d/interface.conf"

- pipeline.id: eventos
  path.config: "/etc/logstash/conf.d/logstash-jdbc-eventos.conf"

- pipeline.id: cpu
  path.config: "/etc/logstash/conf.d/logstash-jdbc-cpu.conf"

- pipeline.id: memory
  path.config: "/etc/logstash/conf.d/logstash-jdbc-memory.conf"

- pipeline.id: ping
  path.config: "/etc/logstash/conf.d/logstash-jdbc-ping.conf"

```

This is the fork-filebeat pipeline

```auto
input {
  beats {
    port => 5044
    include_codec_tag => false
  }
}

output {
  if [tags][0] == "disktag"{
       pipeline { send_to => "fs-pipe" }
  }
  if [tags][0] == "saptag"{
       pipeline { send_to => "sap-pipe" }
  }
  if [tags][0] == "disktag-quebec"{
       pipeline { send_to => "fs-pipe-quebec" }
  }
  if [tags][0] == "disktag-alpha"{
       pipeline { send_to => "fs-pipe-alpha" }
  }
}

```

What is wrong with my conf?

---

<div class="post-metadata">

### Author: ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)
#### Post date: [October 22, 2021, 8:44pm UTC](https://discuss.elastic.co/t/after-using-pipeline-to-pipeline-comunication-in-pipelines-yml-the-other-pipelines-are-not-working/287455/2 "2021-10-22T20:44:29Z")

</div>

What are the configs for those pipelines?

If you have a pipeline with this output:

```auto
pipeline { send_to => "fs-pipe" }

```

You will need another pipeline with this output:

```auto
pipeline { address => "fs-pipe" }

```

So, share the files of those pipelines.

Also, does your documents have the field `tags`? Can you share an example of one source document? Use a `stdout` output to capture that message.

---

<div class="post-metadata">

### Author: ![ElasticLiver](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/elasticliver/32/64869_2.png) [@ElasticLiver](https://discuss.elastic.co/u/ElasticLiver)
#### Post date: [October 22, 2021, 10:20pm UTC](https://discuss.elastic.co/t/after-using-pipeline-to-pipeline-comunication-in-pipelines-yml-the-other-pipelines-are-not-working/287455/3 "2021-10-22T22:20:37Z")

</div>

Hi @leandrojmp, yes I have those inputs:

```auto
input { pipeline { address => "fs-pipe" } }

```

and the tags also work to direct the data to an specific pipeline and index  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/5/d/5d0c03daf7b572bc4928d181a421aa8dcf8fa87d.png)

the problem is that when I put the those (pipeline to pipeline) configurations in pipelines.yml the other ones (JDBC pipelines) stop working.

---

<div class="post-metadata">

### Author: ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)
#### Post date: [October 22, 2021, 11:34pm UTC](https://discuss.elastic.co/t/after-using-pipeline-to-pipeline-comunication-in-pipelines-yml-the-other-pipelines-are-not-working/287455/4 "2021-10-22T23:34:08Z")

</div>

The logstash logs will list the pipelines that are running and the pipelines that are not running after it loads the configuration. What does that message say?

---

<div class="post-metadata">

### Author: ![ElasticLiver](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/elasticliver/32/64869_2.png) [@ElasticLiver](https://discuss.elastic.co/u/ElasticLiver)
#### Post date: [October 23, 2021, 8:57pm UTC](https://discuss.elastic.co/t/after-using-pipeline-to-pipeline-comunication-in-pipelines-yml-the-other-pipelines-are-not-working/287455/5 "2021-10-23T20:57:16Z")

</div>

Hi, @Badger

```auto
 :non_running_pipelines=>[]}

```

the strange thing is that if I run logstash with the command

```auto
/usr/share/logstash/bin/logstash --path.settings /etc/logstash

```

all pipelines in pipelines.yml work....any ideas why they dont work when running logstash as service?

---

<div class="post-metadata">

### Author: ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)
#### Post date: [October 23, 2021, 9:54pm UTC](https://discuss.elastic.co/t/after-using-pipeline-to-pipeline-comunication-in-pipelines-yml-the-other-pipelines-are-not-working/287455/6 "2021-10-23T21:54:25Z")

</div>

Maybe an issue with the user that the service runs as....

---

<div class="post-metadata">

### Author: ![ElasticLiver](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/elasticliver/32/64869_2.png) [@ElasticLiver](https://discuss.elastic.co/u/ElasticLiver)
#### Post date: [October 23, 2021, 10:02pm UTC](https://discuss.elastic.co/t/after-using-pipeline-to-pipeline-comunication-in-pipelines-yml-the-other-pipelines-are-not-working/287455/7 "2021-10-23T22:02:56Z")

</div>

Mmmm maybe,

if I run the service as root logstash will run as root or logstash?

if I run the command `/usr/share/logstash/bin/logstash --path.settings /etc/logstash` it will run as root right?

the last\_run files for JDBC input has onwnership logstash:logstash and are udpated when I run the command `/usr/share/logstash/bin/logstash --path.settings /etc/logstash` as root.

---

<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 20, 2021, 10:03pm UTC](https://discuss.elastic.co/t/after-using-pipeline-to-pipeline-comunication-in-pipelines-yml-the-other-pipelines-are-not-working/287455/8 "2021-11-20T22:03:43Z")

</div>

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