# Packetbeat can send to elasticsearch but not logstash?

**URL:** <https://discuss.elastic.co/t/packetbeat-can-send-to-elasticsearch-but-not-logstash/125997>\
**Category:** Beats\
**Tags:** packetbeat\
**Created:** [March 28, 2018, 9:50pm UTC](https://discuss.elastic.co/t/packetbeat-can-send-to-elasticsearch-but-not-logstash/125997 "2018-03-28T21:50:36Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jameswatson3](https://avatars.discourse-cdn.com/v4/letter/j/a6a055/32.png) [@jameswatson3](https://discuss.elastic.co/u/jameswatson3)\
**Post date:** [March 28, 2018, 9:50pm UTC](https://discuss.elastic.co/t/packetbeat-can-send-to-elasticsearch-but-not-logstash/125997/1 "2018-03-28T21:50:36Z")

</div>

I have an existing 6.2 stack with 2 logstash pipelines sending to elasticsearch - Winlogbeat and Syslog.

I'm trying to add a third pipeline for packetbeat and I can successfully index the output when sent to elasticsearch but not when sent to logstash. When I send to logstash, it crashes with the following logstash errors:

[2018-03-28T16:18:43,553][INFO][org.logstash.beats.BeatsHandler] [local: 10.192.2.126:5045, remote: 10.192.10.181:52624] Handling exception: org.logstash.b  
eats.BeatsParser$InvalidFrameProtocolException: Invalid Frame Type, received: 69  
[2018-03-28T16:18:43,554][WARN][io.netty.channel.DefaultChannelPipeline] An exceptionCaught() event was fired, and it reached at the tail of the pipeline.  
It usually means the last handler in the pipeline did not handle the exception.  
io.netty.handler.codec.DecoderException: org.logstash.beats.BeatsParser$InvalidFrameProtocolException: Invalid Frame Type, received: 69

The packetbeat log shows packetbeat connecting and starting, then after a short time shows loss of the connection.

Any suggestion how to further troubleshoot? Or better idea of how to accomplish my goal? I already tried sending the packetbeat outbeat to the existing logstash beats input for Winlogbeat but the crashing was the same.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [March 28, 2018, 9:59pm UTC](https://discuss.elastic.co/t/packetbeat-can-send-to-elasticsearch-but-not-logstash/125997/2 "2018-03-28T21:59:03Z")

</div>

Please show your relevant beat and Logstash configs 🙂

---

<div class="post-metadata">

**Author:** ![jameswatson3](https://avatars.discourse-cdn.com/v4/letter/j/a6a055/32.png) [@jameswatson3](https://discuss.elastic.co/u/jameswatson3)\
**Post date:** [March 29, 2018, 12:14am UTC](https://discuss.elastic.co/t/packetbeat-can-send-to-elasticsearch-but-not-logstash/125997/3 "2018-03-29T00:14:37Z")

</div>

I'm glad I didn't do that or you would have seen the embarrassing user error in my config files. Once corrected, elastic working like magic as always.

---

<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:** [April 26, 2018, 12:28am UTC](https://discuss.elastic.co/t/packetbeat-can-send-to-elasticsearch-but-not-logstash/125997/4 "2018-04-26T00:28:32Z")

</div>

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