# Trouble parsing msgpack input, falling back to plain text

**URL:** <https://discuss.elastic.co/t/trouble-parsing-msgpack-input-falling-back-to-plain-text/173733>\
**Category:** Logstash\
**Created:** [March 25, 2019, 11:01am UTC](https://discuss.elastic.co/t/trouble-parsing-msgpack-input-falling-back-to-plain-text/173733 "2019-03-25T11:01:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bjk](https://avatars.discourse-cdn.com/v4/letter/b/90db22/32.png) [@bjk](https://discuss.elastic.co/u/bjk)\
**Post date:** [March 25, 2019, 11:01am UTC](https://discuss.elastic.co/t/trouble-parsing-msgpack-input-falling-back-to-plain-text/173733/1 "2019-03-25T11:01:49Z")

</div>

The data coming in through kafka is encoded in msgpack so I try to unpack it using codec.  
However, the following error occurs.

- config

input {  
kafka {  
zk\_connect =\> "localhost:2181"  
topic\_id =\> "topic"  
group\_id =\> "test"  
codec =\> "msgpack"  
}  
}

output {  
stdout { }  
}

- error  
[WARN][logstash.codecs.msgpack] Trouble parsing msgpack input, falling back to plain text....  
[FATAL][logstash.runner] An unexpected error occurred! {:error=\>#\<NoMethodError: undefined method `set' for nil:NilClass....

Did you mean? send\>, :backtrace=\>["/home/logstash/logstash-6.5.4/vendor/bundle/jruby/2.3.0/gems/logstash-codec-msgpack-3.0.7-java/lib/logstash/codecs/msgpack.rb:36:in `decode'", "/home/logstash/logstash-6.5.4/vendor/bundle/jruby/2.3.0/gems/logstash-input-kafka-8.2.1/lib/logstash/inputs/kafka.rb:256:in`block in thread\_runner'", "/home1/logstash/logstash-6.5.4/vendor/bundle/jruby/2.3.0/gems/logstash-input-kafka-8.2.1/lib/logstash/inputs/kafka.rb:255:in `block in thread\_runner'"]}

---

<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 22, 2019, 11:01am UTC](https://discuss.elastic.co/t/trouble-parsing-msgpack-input-falling-back-to-plain-text/173733/2 "2019-04-22T11:01:59Z")

</div>

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