# Permanent truncate detection

**URL:** <https://discuss.elastic.co/t/permanent-truncate-detection/348254>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [November 29, 2023, 4:17pm UTC](https://discuss.elastic.co/t/permanent-truncate-detection/348254 "2023-11-29T16:17:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![terrainc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/terrainc/32/81564_2.png) [@terrainc](https://discuss.elastic.co/u/terrainc)\
**Post date:** [November 29, 2023, 4:17pm UTC](https://discuss.elastic.co/t/permanent-truncate-detection/348254/1 "2023-11-29T16:17:15Z")

</div>

Each 10min filebeat resending file to ELK. In logs we can find "File was truncated. Reading file from offset 0....". File wasn't rotated (state-id the same) or truncated. This file rotated daily only by logrotate (daily, delaycompress). Is any known opened bugs? I am using 8.11.1  
Config

```auto
- ignore_older: 1h
  paths:
  - /log/*.json*
  prospector.scanner.exclude_files:
  - \.gz$
  - \.xz$
  type: filestream

```

---

<div class="post-metadata">

**Author:** ![terrainc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/terrainc/32/81564_2.png) [@terrainc](https://discuss.elastic.co/u/terrainc)\
**Post date:** [December 1, 2023, 2:33pm UTC](https://discuss.elastic.co/t/permanent-truncate-detection/348254/2 "2023-12-01T14:33:45Z")

</div>

Any ideas? Or maybe you need additional information? This is starting to get very annoying. But still can't reproduce this in a test environment.

---

<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 29, 2023, 4:34pm UTC](https://discuss.elastic.co/t/permanent-truncate-detection/348254/3 "2023-12-29T16:34:27Z")

</div>

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