# 2.1.3: Parse Error in Logs

**URL:** <https://discuss.elastic.co/t/2-1-3-parse-error-in-logs/48638>\
**Category:** Logstash\
**Created:** [April 28, 2016, 7:42am UTC](https://discuss.elastic.co/t/2-1-3-parse-error-in-logs/48638 "2016-04-28T07:42:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dawiro](https://avatars.discourse-cdn.com/v4/letter/d/71e660/32.png) [@dawiro](https://discuss.elastic.co/u/dawiro)\
**Post date:** [April 28, 2016, 7:42am UTC](https://discuss.elastic.co/t/2-1-3-parse-error-in-logs/48638/1 "2016-04-28T07:42:28Z")

</div>

Hi,  
After upgrading to 2.1.3 I'm seeing the following error reported in the logs on my test VM:

{:timestamp=\>"2016-04-28T08:09:37.070000+0100", :message=\>"JSON parse failure. Falling back to plain-text", :error=\>#\<LogStash::Json::ParserError: Unrecognized token 'INFO': was expecting 'null', 'true', 'false' or NaN  
at [Source: [B@5a181f9; line: 1, column: 6]\>, :data=\>"INFO [AntiEntropyStage:1] 2016-04-28 08:09:32,290 Validator.java:257 - [repair #27f934a0-0d10-11e6-9d09-4d1537ee238d] Sending completed merkle tree to /10.33.234.40 for keyspace/schemaversion", :level=\>:error}

These messages are coming in via the beats input. We have a mix of json formatted and unstructured logs, like this cassandra log line. We know this is the case and, for the time being, are ok with that. Can I disable the logging of these parsing errors as they're causing disk volumes to fill?

Regards,  
David

---

<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:** [July 6, 2017, 5:00am UTC](https://discuss.elastic.co/t/2-1-3-parse-error-in-logs/48638/2 "2017-07-06T05:00:12Z")

</div>