# Single Event Not Parsed Correctly

**URL:** <https://discuss.elastic.co/t/single-event-not-parsed-correctly/117505>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [January 29, 2018, 5:41pm UTC](https://discuss.elastic.co/t/single-event-not-parsed-correctly/117505 "2018-01-29T17:41:04Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![cappy](https://avatars.discourse-cdn.com/v4/letter/c/22d042/32.png) [@cappy](https://discuss.elastic.co/u/cappy)\
**Post date:** [January 30, 2018, 3:20pm UTC](https://discuss.elastic.co/t/single-event-not-parsed-correctly/117505/8 "2018-01-30T15:20:01Z")

</div>

I just checked the inode, and it seems to be changing with each pull (tested manually), with the exception of a couple recent pulls, where it appears to keep going back and forth between two different inodes (2895/3098)

However, even if I explicitly delete the file, then run the script to replace the file, I still get the same old inode of 2895.

I'm wondering if `clean_inactive` could help here.

Thanks,  
Cappy

---

_[View the full topic](https://discuss.elastic.co/t/single-event-not-parsed-correctly/117505)._