# Issue with pipelines stopping to work

**URL:** <https://discuss.elastic.co/t/issue-with-pipelines-stopping-to-work/109763>\
**Category:** Logstash\
**Created:** [November 30, 2017, 1:57pm UTC](https://discuss.elastic.co/t/issue-with-pipelines-stopping-to-work/109763 "2017-11-30T13:57:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Enrico\_Maria\_Fusi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/enrico_maria_fusi/32/19258_2.png) [@Enrico\_Maria\_Fusi](https://discuss.elastic.co/u/Enrico_Maria_Fusi)\
**Post date:** [November 30, 2017, 1:57pm UTC](https://discuss.elastic.co/t/issue-with-pipelines-stopping-to-work/109763/1 "2017-11-30T13:57:39Z")

</div>

Hello All.

I am experiencing an issue on logstash , but I cannot find a solution.

Basically I have a TCP listener in input, which sends me line like:

> [some garbage] Info:[json message]

So what I do is:

> dissect {  
> mapping =\> {  
> "message" =\> "%{garbage}Info: %{msg}"  
> }  
> }

It usually works, but when some content with no "Info:" in the line reaches the port, then I see an exception, and the pipeline "main" stops.

Is there a safer/robust way to do this, in order to prevent the pipeline to stop?

thanks in advance

---

<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:** [December 28, 2017, 1:57pm UTC](https://discuss.elastic.co/t/issue-with-pipelines-stopping-to-work/109763/2 "2017-12-28T13:57:58Z")

</div>

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